Where your keys live
Paddle does not hold your keys in Paddle Billing, so the first job is to find them. As of November 2026 Paddle’s migration pages say product delivery and license key generation “aren’t handled by Paddle in Paddle Billing” and recommend building them from webhooks. That leaves three cases:
| Where the keys are | What to do |
|---|---|
| Your own database or license server | Follow homegrown license server. |
| Another licensing service | Follow its page, for example Keygen. |
| Paddle Classic license codes | The report below. |
Moving payments does not force an app change. If your keys sit in your own system, your app can keep calling it. You can import the keys into Clavem when you want key management, downloads and Stripe fulfillment in one place, and then the app calls Clavem’s License API instead.
Paddle Classic: the License Activations Report
Classic sellers who sold one-time products through Paddle’s SDKs can use the License Activations Report. Paddle’s help page lists its columns: Activation ID, Paddle License ID, Product ID, Product Name, Email, License Code, Device ID and Date. Each row is one activation, so a key with two devices appears twice, and rows where the buyer never activated hold NULL in the activation, device and date cells.
That layout is close to Clavem’s file import, which accepts the same key on several rows, one device per row. Keep the columns you need and rename two headers:
| Paddle column | Clavem header | Note |
|---|---|---|
| License Code | key |
Kept exactly as written. |
email |
The help page says it can differ from the order email. | |
| Device ID | instance_id |
Clavem also reads device_id. |
| Date | instance_created_at |
Convert to ISO 8601, for example 2024-03-04T10:02:00Z. |
Clear every NULL cell first. In a test file built from those headers, a row with NULL in the date column was rejected with instanceCreatedAt must be an ISO 8601 date, and a NULL device id with a valid date would have been imported as a device called NULL. Two rows with the same key and different devices were read as one key with two devices. Run one file per Paddle product, because the import assigns a whole file to one Clavem product. The layout above comes from Paddle’s help page, not from a real export, so check the date format of your own file.
Paddle’s documentation does not describe a bulk export of Classic license codes beyond this report. A key that was never activated still has a row, with NULL in the device cells.
Subscribers
Paddle is the merchant of record, so it holds the payment methods. Its seller guide describes leaving Paddle as the reverse of joining: you ask Paddle to transfer payment details to the new provider’s PCI-compliant vault, which it says takes within two weeks after security checks, and you export subscriber data from the dashboard. A subscriptions report is one row per subscription, with subscription_id, customer_id, customer_email, subscription_started_at and subscription_next_billed_at among its columns. Generate it in the dashboard or through the API, and download it within 14 days.
On the Stripe side, its Data Migrations team executes the card import and returns a mapping file. Stripe’s page says new customers can pay on Stripe while existing ones stay with the old processor, and that you should cancel the old subscriptions as soon as the Stripe ones are active.
Clavem is not part of that transfer. It issues and extends keys from Stripe events on purchases that went through your mapped Stripe products, and imported keys have no Stripe subscription, so those events never change them. For subscribers you have two practical choices:
- Import their keys with
expires_atset fromsubscription_next_billed_at, then move the date forward withPATCH /v1/admin/licenses/:idas renewals arrive. - Ask them to subscribe again through a Stripe link, which issues a new Clavem key, and let the old key expire.
A key imported with an empty expires_at never expires, so do not leave subscribers’ dates blank.
The subscriptions report does not contain keys, so the dates have to be joined to your key list. Match on email: customer_email in the report against the email column of your key sheet or table, then copy subscription_next_billed_at into expires_at. The report’s subscription_status takes the values active, canceled, past_due, paused and trialing, and a subscription scheduled to cancel still shows as active, so decide before the join what each status means for access. Buyers who used a different email for the license than for the order will not match, and those rows need a manual look.
Webhooks and tax
Paddle’s guide tells Billing sellers to fulfil from transaction.completed. After the move, Stripe’s checkout.session.completed, invoice.paid and charge.refunded events do that work, and Connecting Stripe lists what each does. Turn the Paddle webhook off once Stripe is live so a buyer is not fulfilled twice.
Leaving a merchant of record also moves tax registration and filing onto you. This is general information, not advice. Ask an accountant before you switch.
Rollback
Importing is additive and Paddle is untouched. Keep your Paddle products live until subscribers have moved and the Stripe subscriptions are active. Keep your old fulfillment code behind a switch for a few weeks. If you need to go back, nothing in Clavem blocks it: the Licenses screen exports every key as CSV.
Questions
Does Paddle Billing issue license keys?
No. Paddle's own comparison says Paddle-led fulfillment, including license key generation and activation, has been deprecated in Paddle Billing, and its migration guide recommends building it yourself from transaction.completed webhooks.
Can Paddle move my subscribers' saved cards to Stripe?
Paddle's seller guide says it will transfer payment details to a new provider's PCI-compliant vault within two weeks of your request, after security checks. Stripe's Data Migrations team then runs the import. Confirm the details with both before you commit to a date.
What about double billing?
Stripe's migration page says to cancel the previous subscriptions as soon as the Stripe ones become active, or customers are billed twice.
Sources
- Paddle, subscription migration process and migrating away (checked November 2026)
- Paddle Billing and Classic feature comparison (checked November 2026)
- Paddle, migrate from Classic, update your fulfillment workflow (checked November 2026)
- Paddle, generate reports (checked November 2026)
- Paddle, subscriptions reports (checked November 2026)
- Paddle Classic, the License Activations Report (checked November 2026)
- Stripe, import payment data to Stripe (checked November 2026)