Move from Chargebee to yRecurring.
Chargebee exports everything a move needs as CSV, and for most gateways the saved cards already live in your own account. The whole move is an export, a dry run and one parallel billing cycle.
1. Export from Chargebee
Settings, then Import & Export Data, then Export Data for the product catalog; the Export button on the Subscriptions and Customers pages for those, each with a download import-friendly file option; invoices and transactions through the Exports API.
- Subscriptions (import-friendly file)
- Customers (import-friendly file)
- Product catalog: plans and addons
- Invoices, credit notes and transactions through the Exports API
As documented by Chargebee on 24 September 2026: their export guide.
2. Saved cards
Chargebee stores only the card's last four digits, its expiry and a vault token. If your gateway is Stripe or Braintree the cards sit in your own gateway account and come with you: connect the same account to yRecurring and import the saved payment methods as token references. For cards vaulted through Spreedly, check Chargebee's per-gateway data portability table first, and plan a card-update link before the first renewal for anything it does not carry over.
Source: Chargebee documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Chargebee | In yRecurring | Notes |
|---|---|---|
| Customers | Customers | Name, email, address, tax ids, your own customer id kept as the external id |
| Plans and addons | 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 |
| Credit notes | 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 Chargebee 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 Chargebee and compare the invoices line by line.
- 05Switch
Turn charging on at a renewal boundary and stop Chargebee charging the same day.
Questions teams ask
Which Chargebee export should I use?
The import-friendly subscription and customer files: they are the cleanest column set. The product catalog export rebuilds your plans and addons as products and 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 Chargebee 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.