How to migrate Lemon Squeezy subscriptions without losing your subscribers
Updated November 2026 · Lemon Squeezy stops processing payments March 31, 2027
If you only sell one-time products, migrating off Lemon Squeezy is mostly admin. If you have active subscriptions, it's the part of the migration that decides how much revenue you still have in April 2027.
Lemon Squeezy is the merchant of record, so your subscribers' cards are stored under its account, not yours. You can't log in and download them, and you shouldn't want to: card numbers carry heavy PCI-compliance obligations. So the question isn't "how do I export cards". It's "can the cards be moved for me, or do my customers have to re-enter them?"
That one answer splits every subscription migration into two paths.
Path A: payment methods are transferred
Card details can sometimes move between PCI-compliant payment providers through a secure data transfer. The sending side (Lemon Squeezy, and behind it Stripe) has to agree, and the receiving provider has to accept the import. Each side usually wants to know who you are, how many records there are, and why.
If you get this approved, it's by far the best outcome:
- The transfer lands your customers' payment methods on the new provider, attached to new customer records.
- You recreate each subscription on the new provider with the same price and the same next billing date.
- On the cutover date you cancel the Lemon Squeezy subscription without refunding, so the customer is billed once per period by exactly one provider.
Customers don't do anything. Most never notice.
Ask early. These transfers involve two companies' security and compliance teams. A request sent in March will be too late.
Path B: customers re-subscribe
If the cards can't move, each subscriber has to enter payment details once on the new provider. This is where migrations lose money, and almost all of the loss is avoidable.
What separates a 60% retention rate from a 95% one:
Make it one click from the email
Don't send people to your pricing page. For each customer, generate a checkout link with their plan, email and currency already filled in. On most providers you can create a checkout session per customer through the API and put that link in the email.
Don't charge them early
If a customer paid you for a year in June, don't ask them to pay again in January. Set the new subscription to start billing on their current renewal date, using a trial period or a delayed start depending on the provider. Say it plainly in the email: "You won't be charged until 14 June, your normal renewal date."
Send from you, in your voice
An email from a payment company you've never heard of asking for card details looks exactly like phishing. Send it from your own domain and name. Explain in two sentences why it's happening (Lemon Squeezy is closing), and link to the official announcement so people can check it's real.
Time reminders to each customer's renewal
One email blast in February doesn't work. Send each customer reminders tied to their renewal date: a first notice, then 7 days, 3 days and 1 day before. Customers who renew in May don't need to act in February. Customers who renew on April 2 need to act in March.
Keep access during the grace window
If someone's Lemon Squeezy subscription ends and they haven't re-subscribed yet, don't cut them off instantly. Give a few days' grace with a clear in-app banner. You'll recover many of them.
We have customer email templates for every one of these messages.
The details that cause double charges or lost access
Billing anchors
Every subscription has an anchor date. Recreate each one with the next billing date taken from your Lemon Squeezy export (renews_at), not from today's date. Otherwise customers get charged twice in one month, or get a month free.
Grandfathered prices
Early customers on old prices must stay on old prices. Create a separate price on the new provider for each legacy price point, and map each subscription to the right one. This is the single most common mistake we see.
Trials
A customer halfway through a 14-day trial should keep the remaining days, not get a fresh 14. Use trial_ends_at from the export.
Paused and past-due subscriptions
Lemon Squeezy supports pausing. Decide on purpose what happens to paused subscriptions (recreate them paused, or contact the customer) and to past-due ones (often better left to fail on Lemon Squeezy than carried across).
Annual plans
Annual subscribers who renewed recently won't need to act for months. Don't spam them, but make sure their renewal still happens on the new provider long after you've stopped thinking about the migration.
Tax and currency
If customers paid in local currencies on Lemon Squeezy, check your new provider charges them in the same currency, or tell them clearly if it changes.
Cutover without access gaps
The safest order on cutover day:
- New checkout goes live for new customers.
- Old and new webhook handlers both run. Access is granted if either provider says the customer is active.
- Existing subscriptions are moved (Path A) or invited (Path B) in batches.
- Each Lemon Squeezy subscription is cancelled only after its replacement is confirmed active.
- Every day, compare active counts on both sides until they add up.
Make your app's idea of "this user is subscribed" provider-agnostic: a row in your own database keyed by your own user ID, updated by both providers' webhooks. That one design choice makes the rest of the migration much easier, and makes the next migration, if there ever is one, easy too.
Worked example
A SaaS with 400 monthly subscribers at $19 has about $7,600 MRR.
- Path B done badly (one blast email, pricing-page link, immediate charge): retention often ends up somewhere around 60–75%, a loss of roughly $1,900–3,000 in MRR, every month after.
- Path B done well (pre-filled links, billing deferred to renewal, per-customer reminders, grace period): the loss is usually a small fraction of that.
- Path A (cards transferred): close to zero loss.
Even a few percentage points of retention is worth more than the whole migration costs.
Don't want to do this yourself? We'll do the whole migration at a fixed price.
Questions
Can I export my customers' card details from Lemon Squeezy?+−
No. As merchant of record, Lemon Squeezy holds the payment methods. They can only move through a secure PCI-compliant data transfer between providers, which both sides have to approve.
Will my subscribers be charged twice during the migration?+−
Not if each new subscription keeps the Lemon Squeezy renewal date and the Lemon Squeezy subscription is cancelled at the right moment. Getting that sequence right is most of the work.
What if a subscriber never re-subscribes?+−
Their Lemon Squeezy subscription stops renewing after the shutdown. Per-customer reminders timed to their renewal date and a short in-app grace period recover most of them.
How early should I start migrating subscriptions?+−
Start asking about payment-method transfers now. Move subscriptions in January–February 2027 so customers renewing in March and April have time to act.
Keep reading
- Lemon Squeezy Shutdown
- Lemon Squeezy Alternatives
- Lemon Squeezy Migration Checklist
- Export Lemon Squeezy Data
- Migrate Lemon Squeezy License Keys
- Lemon Squeezy Webhook Migration
Migration guides by destination