Move from Stripe Billing to yRecurring.
Leaving Stripe Billing does not mean leaving Stripe. yRecurring runs on your existing Stripe account, so the cards, the customers and the payouts stay exactly where they are; only the subscriptions move.
1. Export from Stripe Billing
The Export button on the Customers, Subscriptions and Invoices pages of the Dashboard (all columns, date range set to all); prices and charges through the API.
- Customers
- Subscriptions
- Invoices
- Prices and charges through the API
As documented by Stripe Billing on 24 September 2026: their export guide.
2. Saved cards
Nothing to move. Connect the same Stripe account to yRecurring and import the saved payment methods as Stripe token references; the customer keeps paying with the card already on file. If you also want to leave Stripe as the processor, that is a separate, later job: Stripe transfers card data to another PCI compliant processor on request.
Source: Stripe Billing documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Stripe Billing | In yRecurring | Notes |
|---|---|---|
| Customers | Customers | Name, email, address, tax ids, your own customer id kept as the external id |
| Products 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 |
| 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 |
| Payment methods | 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 Stripe Billing 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 Stripe Billing and compare the invoices line by line.
- 05Switch
Turn charging on at a renewal boundary and stop Stripe Billing charging the same day.
Questions teams ask
Do I need to cancel the Stripe subscriptions?
Yes, at the cutover: import them into yRecurring with their renewal dates first, run a cycle in test mode, then cancel them in Stripe on the day you switch charging on, so the same renewal is never billed by both.
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 Stripe Billing 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.