Move from Paddle to yRecurring.
Paddle is the merchant of record, so the move has one extra step the others do not: your customers' cards are in Paddle's vault, and Paddle transfers them to your new payment provider on request. Start that first; the data itself is a report away.
1. Export from Paddle
Reports, then Build reports, then Build report, per report type; download links expire after 72 hours.
- Subscriptions, with customer email and country
- Transactions and line items
- Adjustments
- Products and prices
- Discounts
As documented by Paddle on 24 September 2026: their export guide.
2. Saved cards
Paddle's own seller guide describes the path: tell Paddle you are migrating, pass their security checks, and they transfer payment details to your new provider's PCI compliant vault, within about two weeks. Once the cards are in your Stripe, Braintree or GoCardless account, yRecurring imports them as saved payment methods. Until then, run the trial in test mode.
Source: Paddle documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Paddle | In yRecurring | Notes |
|---|---|---|
| Customers, from the subscriptions report or the API | Customers | Name, email, address, tax ids, your own customer id kept as the external id |
| Plans and prices | Products and prices | One product, many prices: currency, billing period and pricing model per price |
| Subscriptions | Subscriptions | With their renewal dates, so nobody is charged early or twice |
| Transactions | Invoices | Historical, marked as imported; they never email your customers |
| Transactions | Payments | Recorded against the imported invoices |
| Adjustments | Credit notes | Historical, against the imported invoices |
| Saved cards | Saved payment methods | As token references from your payment gateway, never card numbers |
Records go in dependency order: customers and catalog, then subscriptions, then invoices and the payments that settle them. Each row keeps your old system's id, so a second run updates instead of duplicating. What you can import.
4. The cutover, in five steps
- 01Export
Run the Paddle exports above, on the day you are ready to import them.
- 02Connect
Start the free trial and connect the same payment account you charge through today.
- 03Dry run
Upload the files. The import maps the columns, cleans the values, and shows every row it would create before it writes one.
- 04Parallel cycle
Run one billing cycle in test mode beside Paddle and compare the invoices line by line.
- 05Switch
Turn charging on at a renewal boundary and stop Paddle charging the same day.
Questions teams ask
Who collects sales tax after I leave Paddle?
You do, as the seller: yRecurring applies the rates you configure at invoice time and can hand calculation to a tax provider, and you register and remit in the places you need to. Paddle did that as merchant of record; budget for it when comparing prices.
Will my customers get emails during the import?
No. Imported invoices, payments and subscriptions are historical records; the importer never sends a customer email for them. The first message a customer gets from yRecurring is the first invoice or receipt you choose to send.
Could someone be charged twice while both systems run?
Not if the renewal dates come across, which the import keeps. Run yRecurring in test mode beside the old platform for one cycle, compare the invoices, then switch charging on at a renewal boundary and turn the old platform's charging off the same day.
How long does a migration take?
A catalog of a few plans and a few hundred customers is an afternoon: export, dry run, import, one test invoice. The saved cards decide the rest, and that depends on whether your current platform holds them or your gateway does.
Can you do the migration for us?
Yes. Book a demo and bring your export; we import it live with you on the call, so you leave with a working environment on your own data.
Bring your Paddle export to a call.
We import it live with you, dry run first, so you leave with a working environment on your own data. Or start the trial and run the import yourself; it is built for that.