Move from Recurly to yRecurring.
Recurly has the most complete export in the category, thirty-odd CSVs, and a documented way to hand your saved cards to the next system. The one thing to do early is the card export request.
1. Export from Recurly
Analytics, then Exports (the Analytics user role is required); the billing information export is under Data Exports.
- Accounts
- Subscriptions
- Invoices
- Transactions and adjustments
- Plans and coupons
- Billing information: card type, last four, expiry
As documented by Recurly on 24 September 2026: their export guide.
2. Saved cards
Recurly exports card data only in tokenized form, to a PCI compliant destination, on request to Recurly Support; one export is free as part of off-boarding. Ask for it the day you decide to move: their data migrations team runs it, and the tokens land in your gateway account where yRecurring reads them as saved payment methods.
Source: Recurly documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Recurly | In yRecurring | Notes |
|---|---|---|
| Accounts | Customers | Name, email, address, tax ids, your own customer id kept as the external id |
| Plans and add-ons | 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 |
| Invoices | Invoices | Historical, marked as imported; they never email your customers |
| Payments | Payments | Recorded against the imported invoices |
| Adjustments and credit invoices | 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 Recurly 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 Recurly and compare the invoices line by line.
- 05Switch
Turn charging on at a renewal boundary and stop Recurly charging the same day.
Questions teams ask
How long do Recurly exports stay available?
Seven days after they are generated, so run the exports when you are ready to import them, not weeks ahead.
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 Recurly 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.