Lemon Squeezy migration
Leaving Lemon Squeezy, without rewriting your app.
Lemon Squeezy stops processing payments on 31 March 2027. The replacement it recommends, Stripe Managed Payments, has no license keys. Clavem takes over that part: your customers’ keys move across, and your app changes one hostname.
The situation
Three things to know.
- 1 · The deadline
Lemon Squeezy stops on 31 March 2027.
New sign-ups are already closed. Lemon Squeezy has said it cannot extend the date.
- 2 · Your keys
Your existing keys can move.
Clavem imports each key with its status, device limit, expiry and activated devices. Customers keep the key they have.
- 3 · Your app
Your app changes one hostname.
Clavem’s License API has the same paths, parameters and response shape. Ship one update before the deadline.
In their words
What Lemon Squeezy has said.
From Lemon Squeezy’s own migration documentation. Quotes are exact.
- 16 Nov 2026Shutdown announced. New sign-ups closed.
- 2 Dec 2026Lemon Squeezy’s migration tooling opens.
- Mid-Jan 2027Latest start Lemon Squeezy recommends.
- 31 Mar 2027Processing stops.
“We won’t be able to extend.”
“Managed Payments does not offer license-key management or file and link hosting.”
“Not included. Connect a fulfillment or licensing app, or build your own.”
“Customers may lose access to their license keys, files, and links after March 31, 2027”
Source: Lemon Squeezy’s migration documentation at docs.lemonsqueezy.com/migration, and its announcement of 16 November 2026, read on 18 November 2026. Their pages may change, so read them yourself. By the same documentation, Stripe Managed Payments is priced at 3.5% plus Stripe fees, with a promotional rate of 1.5% through 1 December 2027.
What moves
What moves by itself, and what does not.
Clavem replaces the license-key and download half of Lemon Squeezy. It does not take payments.
| What | Moves by itself? | What to do |
|---|---|---|
| Payments and checkout | Lemon Squeezy recommends Stripe Managed Payments. Its documentation lists what its tooling moves. | Set up Stripe, then connect it to Clavem. |
| License keys | No. Customers may lose access to them after 31 March 2027. | Import them into Clavem. |
| Files and links | No. Managed Payments does not host them. | Upload release files to Clavem. |
| Your app’s license calls | No. Shipped versions call api.lemonsqueezy.com. | Change the hostname and ship an update. |
| Lemon Squeezy’s License API after 31 March 2027 | Not documented. | Do not rely on it. |
The plan
Five steps, in this order.
Keys and your app come first, because they are what customers notice. Payments can move when you are ready.
- Step 1
Create a Clavem product
Create a free account and add a product for each app you sell. Clavem generates an Ed25519 key pair for it. Copy the product’s public key and id: your app will use them to verify keys offline. The product’s device limit is a default. Imported keys keep the limit they had.
- Step 2
Import your keys
Two ways. Both are safe to run again, because keys that already exist are skipped.
- With a Lemon Squeezy API key. Paste it into the import screen. Clavem reads your stores, products, license keys and their device activations, page by page. The key is used for the import and is not stored. The screen first shows what it found, and you map each Lemon Squeezy product to a Clavem product, or let Clavem create one with the same name.
- With a CSV. Needs no API key. A row requires a key and an email address. Name, device limit, status, expiry and creation date are optional. Each row is checked on its own: a bad row is reported and the rest import. The columns are listed in Import existing licenses.
Imports count against your plan, but expired and disabled keys do not. A batch that would pass the limit is refused whole, before anything is written. How limits work.
- Step 3
Change the hostname in your app, and ship an update
The License API has the same paths, parameters and response shape. The change is one line.
License check in your app1 line changed - https://api.lemonsqueezy.com/v1/licenses/validate+ https://clavem.io/v1/licenses/validate license_key=38b1460a-5104-4067-a91d-77b872934d51 instance_id=47596ad9-a811-4ebf-ac8a-03fc7b6d2a17Change
/activateand/deactivatethe same way. Bodies can be JSON or form-encoded. A device id your app stored last year still validates. The response also carries a signedtoken, which you can adopt later for offline checks. Details are in the API reference and the platform guides. - Step 4
Move payments to Stripe and connect it
Lemon Squeezy recommends Stripe Managed Payments. Whichever way you sell in Stripe, create a restricted key and connect it, then map each Stripe product to a Clavem product. New purchases then issue Clavem keys (25 characters in five groups) and an order page. Imported keys keep their old format. See Connecting Stripe, including the notes on Managed Payments.
- Step 5
Upload release files
Upload your current build to Clavem and publish it. New buyers download from their order page, and your app can check for updates with any license key, including imported ones. See Releases and downloads.
What is kept
To your app, an imported license looks the same as before.
Key strings
Stored exactly as they were, UUIDs included. Matching ignores case.
Statuses
inactive,active,expiredanddisabled. A key Lemon Squeezy had disabled stays disabled.Device limits
Each key keeps its own limit. Unlimited stays unlimited.
Expiry and dates
The expiry date and the creation date, and the buyer’s name and email.
Devices
Every activation, under the instance id and name your app stored. Each still validates and still uses a seat.
Original ids
Lemon Squeezy’s documentation tells apps to check store, product and variant ids, so imported licenses answer with the originals in
meta, along with the license, order, order item and customer ids. The full response is in the API reference.
Limits
What the import cannot do, and what is unproven.
Installed apps must be updated
App versions already in customers’ hands that hard-code
api.lemonsqueezy.commust be updated before 31 March 2027. Importing keys does not change where an installed app sends its requests.After the deadline is unknown
Whether Lemon Squeezy’s own License API keeps answering after 31 March 2027 is not documented. Plan as if it will stop, and decide what your app does when it cannot get an answer.
Untested on a live store
The importer was built from Lemon Squeezy’s published API documentation and covered by automated tests. It has not yet been run against a live store, because new Lemon Squeezy accounts cannot be opened. The first sellers to import get hands-on help, and the CSV route is always available.
No order page for imports
The import creates licenses and device activations, not orders. Those buyers get downloads through your app’s update check, or from your site. The device page at /licenses/manage works with their key.
One place per key
A key that already exists in Clavem, in any account, is skipped rather than copied.
Not a merchant of record
Clavem does not take payments or handle tax. It sits next to Stripe, not in place of it.
A new service
Clavem launched in November 2026. Keys verify offline against a public key you hold, and you can export everything as CSV, so the risk of trusting a new vendor is bounded. See offline verification.
Questions
Migration questions.
When does Lemon Squeezy stop processing payments?
On 31 March 2027. Lemon Squeezy closed new sign-ups on 16 November 2026, its migration tooling opens on 2 December 2026, and its documentation says: “We won’t be able to extend.”
Does Stripe Managed Payments include license keys?
No. Lemon Squeezy’s migration documentation says: “Managed Payments does not offer license-key management or file and link hosting.” Its comparison page says to connect a fulfilment or licensing app, or build your own. Clavem is a licensing and fulfilment app that works with Stripe.
Will my customers’ existing license keys keep working?
Yes, once you import them. Clavem keeps each key string, status, device limit, expiry and device activation, and answers with the same store, product, variant and order numbers Lemon Squeezy returned. The importer has not yet been run against a live Lemon Squeezy store, because new accounts cannot be opened. It was built from the published API documentation.
Do I have to change my app?
One line: the hostname of the License API. The paths, parameters and response shape match the Lemon Squeezy License API. Versions of your app that customers already have installed will keep calling Lemon Squeezy until they update, so ship the update before 31 March 2027.
Do I have to give you my Lemon Squeezy API key?
Only if you want the automatic import. The key is used to read your keys during the import and is not stored. The alternative is a CSV export, which needs no key.
Will Lemon Squeezy’s own License API keep answering after March 2027?
That is not documented. Do not rely on it. Move your app to a License API you control, and decide what your app does when it cannot get an answer.
Is Clavem a replacement for Lemon Squeezy’s checkout?
No. Clavem does not take payments or act as a merchant of record. It is the license, download and update layer that sits on Stripe. Lemon Squeezy recommends Stripe Managed Payments for the payment side.
What does it cost?
Free for your first 50 active licenses, then flat monthly plans from $29. There is no cut of your sales. See the pricing page for the limits.