How to migrate from Lemon Squeezy to Stripe
Stripe Managed Payments is the path Lemon Squeezy itself points sellers to. Stripe acts as merchant of record, so tax stays off your plate.
Updated November 2026 · Lemon Squeezy stops processing payments March 31, 2027
Stripe is a good fit if
- — You want the officially supported route
- — You may later want full Stripe Billing, Connect or Radar
- — Your team already knows the Stripe API
Check first
- — Check Managed Payments availability for your country and product type before you commit
- — License keys are not a Stripe primitive, so you need your own key service
- — Affiliates need a separate tool
Why most sellers will look at Stripe first
Lemon Squeezy's own announcement points sellers to Stripe Managed Payments. The team that built Lemon Squeezy built Managed Payments, and Stripe owns both. Lemon Squeezy is telling every seller about it, so for many SaaS businesses it's the path of least resistance.
Managed Payments makes Stripe your merchant of record, like Lemon Squeezy was. Stripe collects and pays sales tax and VAT, handles disputes, and sells to your customers on your behalf. You still get the Stripe API, the Stripe dashboard and Stripe's ecosystem.
Mapping your catalog
| Lemon Squeezy | Stripe |
|---|---|
| Store | Stripe account |
| Product | Product |
| Variant | Price (one per variant and interval) |
| Subscription | Subscription |
| Discount code | Coupon + Promotion code |
| Customer | Customer |
| License key | Not built in. Run your own key service |
| Affiliates | Not built in. Use a third-party tool |
Each Lemon Squeezy variant usually becomes one Stripe Price. If a variant has monthly and yearly options, that's two Prices on the same Product. Use Price metadata to store the old Lemon Squeezy variant ID. You'll want it for mapping subscriptions.
Swapping checkout
Replace Lemon Squeezy checkout links or the overlay with a Stripe Checkout Session created on your server:
const session = await stripe.checkout.sessions.create({
mode: "subscription",
line_items: [{ price: "price_...", quantity: 1 }],
client_reference_id: user.id, // replaces custom_data.user_id
customer_email: user.email,
success_url: "https://yourapp.com/welcome",
cancel_url: "https://yourapp.com/pricing",
});
// redirect the user to session.url
Check Stripe's Managed Payments docs for any extra parameters needed to sell under Managed Payments. They're the source of truth for the current setup.
Moving subscriptions to Stripe
This is the part to plan carefully. Since Stripe already processes Lemon Squeezy's payments behind the scenes, ask Lemon Squeezy support and Stripe directly what transfer path exists for your subscribers' payment methods. If the cards can be carried over, you recreate subscriptions in Stripe with the same price and a billing anchor matching each customer's renews_at date, then cancel the Lemon Squeezy side. If not, follow the re-subscribe playbook.
Stripe-specific tips:
- Use
billing_cycle_anchor(or a trial ending on the renewal date) so nobody is billed early. - Set
proration_behavior: "none"when recreating, so Stripe doesn't invent a partial charge. - Put the Lemon Squeezy subscription ID in subscription
metadata. Support will thank you.
License keys on Stripe
Stripe has no license key primitive. Run a small key service: a table of keys and activations, created from your checkout.session.completed / invoice.paid webhook, and a validation endpoint on your own domain. Make that endpoint answer in the same format as Lemon Squeezy's license API, and your app update is just a URL change. Full walkthrough: migrating license keys.
Customer portal
Stripe's hosted customer portal replaces Lemon Squeezy's "manage subscription" page. Create a portal session on your server and link to it from your account page. Configure which actions customers can take (cancel, switch plan, update card) in the Stripe dashboard.
Typical timeline
| Week | Work |
|---|---|
| 1 | Export, confirm Managed Payments eligibility, ask about payment-method transfer |
| 2 | Rebuild catalog, new checkout and webhooks in test mode |
| 3 | License key service and app update, affiliates |
| 4–5 | Move subscriptions, staged cutover, customer emails |
Webhook mapping: Lemon Squeezy → Stripe
Closest equivalents. Check payload shapes against Stripe's current docs before shipping. Signature code for every provider →
| Lemon Squeezy | Stripe |
|---|---|
| order_created | checkout.session.completed |
| subscription_created | customer.subscription.created |
| subscription_updated | customer.subscription.updated |
| subscription_payment_success | invoice.paid |
| subscription_cancelled | customer.subscription.deleted |
| license_key_created | none: issue keys from your own service |
Don't want to do this yourself? We'll do the whole migration at a fixed price.
Questions
How long does a Lemon Squeezy to Stripe migration take?+−
A store with only one-time products can move in a few days. With active subscriptions, license keys or affiliates, plan for two to five weeks including testing and a staged cutover.
Can I move my subscribers to Stripe without them re-entering their card?+−
Only if a secure payment data transfer between Lemon Squeezy/Stripe and Stripe is approved for your account. Ask both sides early. If it isn't possible, a well-run re-subscribe flow keeps most subscribers.
Is Stripe a merchant of record like Lemon Squeezy?+−
Yes. Stripe handles sales tax and VAT as merchant of record. Confirm it supports your seller country and product type.
Does Stripe support license keys?+−
Not natively. You'd run your own key service fed by Stripe webhooks and keep validation on your own domain.