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.
See how Lemon Squeezy and yRecurring compare →What is different about leaving Lemon Squeezy
Variants are where the prices live
A Lemon Squeezy product has variants, and each variant carries the price and the billing interval. Each variant becomes a price under its product; when your variants are really separate plans (Basic, Pro), make each its own product.
License keys stay with the store
yRecurring does not issue license keys. If your app validates Lemon Squeezy keys, move the access check to the subscription status, which your app can read from yRecurring's API or webhooks, before you close the store.
Move subscribers at their renewal
With no card transfer, each subscriber moves on their own renewal date once they have added a card. Point new signups at yRecurring on day one; the existing base follows over one billing cycle.
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 |
|---|---|---|
| Customer: name, email, country | Customer From the orders export or the API. | From the orders export or the API. |
| Product | Product Rebuilt in minutes, or imported from a short file. | Rebuilt in minutes, or imported from a short file. |
| Variant: price, interval, trial | Price One price per variant and currency. | One price per variant and currency. |
| Subscription: variant, status, renews at | Subscription renews at becomes the next billing date; on_trial becomes trialing. | renews at becomes the next billing date; on_trial becomes trialing. |
| Subscription invoice | Invoice Historical, one summary line with the total. | Historical, one summary line with the total. |
| Order for a one-time purchase | Invoice, marked paid Kept for the customer history. | Kept for the customer history. |
| Order total, as paid | Payment Recorded against the invoice it settled. | Recorded against the invoice it settled. |
| Refund on an order | Credit note Historical, against its invoice. | Historical, against its invoice. |
| Saved card, held by Lemon Squeezy | Saved payment method, added by the customer Collected through a card update link before the renewal. | Collected through a card update link before the renewal. |
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 Lemon Squeezy, and what to do instead
They stay with the merchant of record. Send each subscriber a card update link two or three weeks before their renewal, from your own address.
Recreate them as yRecurring coupons, with codes in a batch if you had many.
Lemon Squeezy filed as the seller; now you do. Configure your rates, or connect Avalara AvaTax from Grow.
Usage on a subscription item stays in Lemon Squeezy. Create a meter in yRecurring and report usage to it from each customer's first yRecurring period.
4. The cutover, in five steps
- 01Export
Export orders and subscriptions from the store, and pull customers through the API if you want their full records.
- 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
As each subscriber adds a card, cancel their Lemon Squeezy subscription so it ends at the period they paid for.
Questions about leaving Lemon Squeezy
See how Lemon Squeezy and yRecurring compare → What you pay today, next to a flat plan: the fee calculator →
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.
Should I wait for the path to Stripe Managed Payments?
If being on Stripe Managed Payments is where you want to end up, ask Lemon Squeezy for its timing. If you want your own payment account, invoices and net terms now, the card update route on this page works today.
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.