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.
See how Recurly and yRecurring compare →What is different about leaving Recurly
Ask for the card export on day one
The tokenized billing information export is run by Recurly Support, so it is the one step with a queue. Request it when you decide to move, and generate the other exports close to your import date.
One plan, several currencies
A Recurly plan can carry a price in several currencies. yRecurring keeps currencies apart: import one price per currency under the same product, and point each subscription at the price in the currency it pays in.
Account codes are your join key
Recurly identifies accounts by an account code, often one you set yourself. Use it as the customer's external id and as the customer reference in the subscription, invoice and payment method files, so every file joins without a lookup.
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 |
|---|---|---|
| Account: account code, email, company, address, VAT number | Customer The account code is kept as the external id. | The account code is kept as the external id. |
| Plan: plan code, interval | Product, kind plan The plan code is kept as the product external id. | The plan code is kept as the product external id. |
| Plan price, one per currency | Price One price per currency and interval. | One price per currency and interval. |
| Add-on: add-on code | Product, kind add-on Fixed add-ons import with a flat or per unit price; usage add-ons get a meter and a metered price built in the app. | Fixed add-ons import with a flat or per unit price; usage add-ons get a meter and a metered price built in the app. |
| Subscription: uuid, plan, quantity, state, current period start and end | Subscription in_trial becomes trialing; canceled and expired arrive as canceled, kept for history. | in_trial becomes trialing; canceled and expired arrive as canceled, kept for history. |
| Charge invoice | Invoice Historical, one summary line with the total. | Historical, one summary line with the total. |
| Credit invoice and credit adjustments | Credit note Historical, against the invoice they credited. | Historical, against the invoice they credited. |
| Successful transaction | Payment Recorded against its invoice. | Recorded against its invoice. |
| Billing info, tokenized by Recurly Support | Saved payment method Tokens in your gateway account, read as saved payment methods. | Tokens in your gateway account, read as saved payment methods. |
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 running a file again skips what is already there instead of copying it; customers, products and prices can be set to update instead. What you can import.
What stays in Recurly, and what to do instead
Recreate the coupons in yRecurring and apply them to the subscriptions with an active redemption.
Usage recorded in Recurly stays there. Create the meter in yRecurring and report usage to it from the first yRecurring period.
Balances do not travel in the files. Honor them with a credit note on each customer's first yRecurring invoice.
Recreate your retry schedule in yRecurring (all plans); smart timing and card expiry warnings come with Grow.
4. The cutover, in five steps
- 01Export
Once Recurly Support confirms the card tokens, run the account, subscription, invoice and plan exports from Analytics.
- 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
Cancel the Recurly subscriptions so they expire at the end of the paid term, the day yRecurring's first renewal bills.
Questions about leaving Recurly
See how Recurly and yRecurring compare → What you pay today, next to a flat plan: the fee calculator →
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.
Should I cancel or terminate the Recurly subscriptions?
Cancel. A canceled Recurly subscription runs to the end of the term the customer already paid for and then expires without renewing, which is exactly where yRecurring picks up. Terminating ends it at once and can refund part of the term.
Our plans charge a setup fee. Does that come across?
The historical invoices that carried it do. For customers who sign up after the move, add the setup fee as a one-off charge alongside the plan.
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.