Move from Lemon Squeezy to yRecurring.
Lemon Squeezy exports orders and subscriptions, and rebuilding a store's products takes minutes. What it does not offer is a documented way to move saved cards to another provider, so the plan below treats the first renewal as a card update.
1. Export from Lemon Squeezy
Orders, then Export, for a CSV sent to the store owner; Store, then Subscriptions, then Export, for subscriptions and their invoices.
- Orders, with totals and tax
- Subscriptions and subscription invoices
- Customers through the API
As documented by Lemon Squeezy on 24 September 2026: their export guide.
2. Saved cards
As merchant of record Lemon Squeezy holds the cards, and its help center documents no self-serve transfer to another provider (ask their support; since Stripe's acquisition it has said it is building a path to Stripe Managed Payments). So: import subscriptions with their renewal dates, send each customer a link to add a card before the renewal, and let payment recovery follow up with the ones who do not. Customers who add a card pay their next renewal on yRecurring; the rest keep their access until the recovery run ends.
Source: Lemon Squeezy documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Lemon Squeezy | In yRecurring | Notes |
|---|---|---|
| Customers, from the orders export 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 |
| Orders and subscription invoices | Invoices | Historical, marked as imported; they never email your customers |
| Orders | Payments | Recorded against the imported invoices |
| Refunds | 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 Lemon Squeezy 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 Lemon Squeezy and compare the invoices line by line.
- 05Switch
Turn charging on at a renewal boundary and stop Lemon Squeezy charging the same day.
Questions teams ask
Will I lose customers over the card update?
Some will not act on the first email; that is what the recovery run is for, with its retry schedule and follow-ups, and you decide what happens when it is exhausted. Sending the link two or three weeks before the renewal, from your own address, is the single biggest lever.
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 Lemon Squeezy 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.