Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My business is on Paddle Classic and I need to move to Paddle Billing

Short answer

Paddle Billing is a different system, not an update. Checkout, webhooks, API keys and your subscription records all have to be rebuilt first. Then Paddle's dashboard migration moves existing subscriptions in batches, which Paddle says silently cancels the Classic ones. Do not switch anything off until a test renewal has worked.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Paddle told me to move to Paddle Billing and I do not know what that involves.
  • My developer says the checkout and the webhooks have to be rewritten.
  • I am worried subscribers will be cancelled or charged twice.
  • Customer data, plans and prices look different in the new dashboard.
  • Licence keys or downloads came from Paddle before and I do not know what replaces them.

Why does this happen?

  1. Billing is a new system with a new integration

    Paddle's reintegration checklist says Paddle.js v1 is replaced by Paddle.js v2 with client-side tokens, new notification destinations replace the single endpoint, and new API keys are needed. Paddle recommends new pages for the Billing checkout.

  2. Webhooks change shape and verification

    Paddle documents that Classic webhooks are form-encoded and Billing sends JSON. Billing verifies each event with the Paddle-Signature header and a secret per destination. Code that reads the old format silently fails.

  3. Your data model does not match one to one

    Classic separates products and plans, while Billing has one product with prices. Billing splits customer data into customer, address and business, and a customer can hold several subscriptions. Paddle also says currency override prices become separate non-catalogue prices.

  4. Fulfilment is now your job

    Paddle states that Classic handled licence keys and digital downloads, while in Billing you build this yourself, typically by listening for transaction.completed events.

  5. The subscription move has its own rules

    Paddle describes the dashboard migration as being in early access with enrolment required. Active, paused and past due subscriptions can move, subscriptions in dunning restart it, and those that finished dunning are imported as paused. If an import fails, the Classic subscription is not cancelled.

What can I do about it today?

  1. Change nothing in Classic yetKeep your current checkout and subscriptions running. Nothing in Classic needs to be switched off to start planning.
  2. Write down what Paddle does for you todayList emails, licence keys, downloads, invoices, cancel and upgrade flows. Each one has to be rebuilt or replaced.
  3. Export your numbersSave the count of active subscribers by plan and the current revenue reports. Historic data stays in Classic, according to Paddle, so keep your own copy.
  4. Read Paddle's reintegration checklist with your developerAsk who will do each step and when. The checklist is long, and ten minutes of reading together shows the real size of the job.
  5. Ask Paddle about enrolmentThe subscription migration needs enrolment in an early access programme, so ask Paddle early.

When should I bring someone in?

  • You sell licence keys, downloads or seat-based plans that depend on Paddle Classic behaviour.
  • Your app reads Classic webhooks to grant or remove access.
  • You have many subscribers with trials, discounts or custom prices.

How do I handle it?

  1. Map Classic to Billing on paperI take your plans, prices, webhooks and database fields and map each one to its Billing equivalent, using Paddle's published data mapping.
  2. Build the new integration beside the old oneNew customers go through Billing in the sandbox first, with the webhook simulator, while Classic keeps running.
  3. Prove a full cycleA real purchase, a renewal, a cancellation and a failed payment are tested end to end before any existing subscriber is moved.
  4. Move subscribers in small batchesI start with a small batch, as Paddle recommends, check each against your records, and keep a written rollback step.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will my subscribers notice the move?

Paddle states the Classic subscription is cancelled silently with no disruption to the customer. Check the current wording with Paddle before you promise customers anything.

What if an import fails?

Paddle says that if an import fails, the Classic subscription is not cancelled.

Can I do it all in one go?

Paddle says you can run as many migrations as you like in batches and recommends starting with a small batch.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.