The complete Lemon Squeezy migration checklist
Updated November 2026 · Lemon Squeezy stops processing payments March 31, 2027
This is the checklist we work from on real migrations, in the order we do things. It works whether you're moving to Stripe Managed Payments, Paddle, Polar, Dodo Payments or Creem. Skip the sections that don't apply to you. If you sell only one-time downloads, half of it won't.
Copy it into your task tracker and tick items off. The steps marked ⚠ are the ones that cost revenue when they're missed.
Phase 1: Decide (week 1)
- Read Lemon Squeezy's email about your store's next steps, and save it
- Write down your seller country, entity type and payout bank country
- List what you sell: subscriptions, one-time, license keys, downloads, usage-based
- Count active subscriptions and their MRR
- Count activated license keys
- Count affiliates with a sale in the last 90 days
- Shortlist two destinations (comparison)
- Confirm each shortlisted provider supports your country and product category
- ⚠ Ask both Lemon Squeezy and the new provider whether payment methods can be transferred
- Apply to the chosen provider (some take days to approve)
Phase 2: Export (week 1)
- Create a read-only Lemon Squeezy API key
- Export products and variants
- Export prices, intervals, trial lengths
- Export discount codes with remaining uses and expiry
- Export customers
- ⚠ Export subscriptions with status, variant, renewal date, trial end, pause state
- Export orders (needed for refunds and support after the switch)
- ⚠ Export license keys with status, activation limit, activation usage, expiry
- Export license key instances (activations)
- Export affiliates and unpaid commission balances
- Store the raw JSON somewhere safe. This is your backup and audit trail
Full code for every export: How to export all your Lemon Squeezy data.
Phase 3: Rebuild the catalog (week 2)
- Create each product on the new provider
- Create one price per Lemon Squeezy variant and billing interval
- ⚠ Create separate prices for grandfathered customers on old pricing
- Recreate trials with the same lengths
- Recreate discount codes you still honour
- Re-upload digital files for download products
- Set up tax category for each product correctly
- Build a mapping file: Lemon Squeezy variant ID → new price ID
Phase 4: Rewire your app (weeks 2–3)
- Replace checkout links and overlay scripts
- Pass your own user ID into checkout metadata
- Write new webhook handlers (event mapping)
- Verify webhook signatures for the new provider
- Make handlers idempotent (same event twice = no double access)
- Key access off your own user ID, not a provider customer ID
- Replace "manage subscription" / customer portal links
- Update receipts and invoice links in your emails
- Test the full purchase → access → cancel → lose access loop in test mode
Phase 5: Subscriptions (weeks 3–5)
- ⚠ Decide: payment-method transfer or re-subscribe flow
- If transferring: recreate each subscription with the same next billing date
- If re-subscribing: build links that open a checkout already filled in for each customer, with billing deferred to their renewal date
- Handle trials and paused subscriptions on purpose
- ⚠ Only cancel each Lemon Squeezy subscription after its replacement is confirmed
- Reconcile counts: active on Lemon Squeezy vs active on new provider, every day of cutover
Details: Migrating subscriptions without churn.
Phase 6: License keys (weeks 2–5)
- Choose where keys live: provider's built-in keys or your own service
- Import existing keys with activation counts
- Stand up a validation endpoint you control
- ⚠ Ship an app update that validates against your endpoint before the deadline
- Add an offline grace period so old builds degrade gently
Details: Migrating license keys.
Phase 7: Affiliates (week 4)
- Choose an affiliate tool with a native integration for your new provider
- Import affiliates and keep their referral codes where possible
- Settle unpaid Lemon Squeezy commissions
- Email affiliates their new dashboard link before cutover
Phase 8: Cut over (week 5–6)
- Pick a low-traffic day
- Switch checkout to the new provider
- Run old and new webhook handlers side by side
- Send customer emails (templates)
- Watch failed payments, support inbox and access errors daily for two weeks
- Keep Lemon Squeezy active until the last legacy subscription is handled
Phase 9: After
- Re-send reminders to customers who haven't re-subscribed (at 7 days, 3 days, 1 day before their renewal)
- Update help docs, FAQ and pricing page links
- Remove Lemon Squeezy scripts and environment variables
- Archive your Lemon Squeezy export somewhere you'll find it in a year
Don't want to do this yourself? We'll do the whole migration at a fixed price.
Questions
How long does a Lemon Squeezy migration take?+−
From a few days for a store selling only one-time products, to four to six weeks for a SaaS with hundreds of subscribers, license keys and affiliates. Most of the calendar time is approvals, testing and giving customers time to act.
What's the most commonly missed step?+−
Grandfathered prices and license key app updates. Both cause angry customers on day one.
Can I run Lemon Squeezy and the new provider at the same time?+−
Yes, and you should during cutover. Keep Lemon Squeezy active until every legacy subscription has been moved or has ended.