What has to move
A license system is four things: the keys, who owns them, which devices are activated on them, and the endpoint your app calls. Move all four, in that order, or an installed app will tell a paying customer their key is not found.
| Piece | Why it matters | Where it breaks |
|---|---|---|
| The key string | The customer has it in an email | A reformatted key no longer matches |
| Buyer, limit, expiry, status | Decides what the key does | A lost expiry turns a one-year license into a perpetual one, or the reverse |
| Activated devices | Each is saved in the app as an instance id | Without them, validation with instance_id returns “instance_id not found” |
| The endpoint | Compiled into every shipped build | Old builds keep calling the old host |
Lemon Squeezy’s migration pages say its fulfilment is not migrated automatically: Managed Payments “does not offer license-key management or file and link hosting”, and links and integrations “do not redirect automatically”. Plan the key move yourself.
Same call, new host
Clavem’s License API uses the same paths, parameters and response shapes as the Lemon Squeezy License API. The request below is a Lemon Squeezy validate call with the hostname swapped.
curl -X POST https://clavem.io/v1/licenses/validate \
-H "Accept: application/json" \
-d license_key=S1GNE-TDEM0-7K4QX-9WZ2P-H5RB8
Real response for the demo key, as of 19 November 2026:
{"valid":true,"error":null,
"license_key":{"id":1,"status":"active","key":"S1GNE-TDEM0-7K4QX-9WZ2P-H5RB8","activation_limit":3,"activation_usage":1,
"created_at":"2026-11-18T23:19:24.740Z","expires_at":null,"test_mode":false},
"instance":null,
"meta":{"store_id":1,"order_id":null,"order_item_id":1,"product_id":1,"product_name":"Inkwell",
"variant_id":1,"variant_name":"Default","customer_id":1,"customer_name":"Ada Lovelace","customer_email":"ada@example.com"},
"token":"sgt1.eyJ2IjoxLCJsaWQiOjEs..."}
The only new field is token, a signed statement your app can verify offline. Existing code can ignore it. I also called both services with an unknown key. They answered identically: HTTP 404 and {"valid":false,"error":"license_key not found."}.
Where the two differ
| Case | Lemon Squeezy | Clavem |
|---|---|---|
| Body encoding | Form-encoded, Accept: application/json |
Form-encoded or JSON |
Missing license_key |
HTTP 422 with message and an errors object |
HTTP 400 with {"valid":false,"error":"license_key: Invalid input: expected string, received undefined"} |
| Rate limit | 60 requests per minute | 120 per minute per IP address and 60 per minute per key |
| Browser calls | Not stated on the License API page | CORS allowed from any origin |
I observed the missing-key difference by sending an empty body to both on 19 November 2026. If your app treats HTTP 422 as “bad input” and anything else as “network trouble”, change it to read the error text or to treat any 4xx as a rejected request.
The order to do it in
- Import with a dry run. The importer reads keys, buyers, limits, expiry dates and devices. It keeps each key string exactly, and each device under its original instance id, so an app that saved an
instance_idcan validate with it straight away. Imports are safe to repeat. - Check a sample against the new host. Take ten real keys, including one expired, one with several devices and one that is at its limit. Validate each and compare the answers with the old service.
- Ship the app update that uses the new hostname, with the fallback below.
- Move new sales. Point checkout at Stripe, connect Stripe to the licensing service, and test a purchase end to end.
- Retire the old host in the app after the old service has closed.
Lemon Squeezy’s migration guide gives these dates: sign-ups closed on 16 November 2026, migration tooling opens on 2 December 2026, the latest recommended start for a migration is mid-January 2027, and processing stops on 31 March 2027. The guide says a full migration can take up to eight weeks.
Ask the new host first, then the old one
During the overlap, a customer’s key may be imported or not yet. This function asks Clavem first and falls back to the old host only on a 404:
const HOSTS = ['https://clavem.io', 'https://api.lemonsqueezy.com'];
async function validate(licenseKey, instanceId) {
for (const host of HOSTS) {
try {
const res = await fetch(host + '/v1/licenses/validate', {
method: 'POST',
headers: { Accept: 'application/json', 'Content-Type': 'application/x-www-form-urlencoded' },
body: new URLSearchParams({ license_key: licenseKey, ...(instanceId ? { instance_id: instanceId } : {}) }),
signal: AbortSignal.timeout(5000),
});
if (res.status === 404 && host !== HOSTS.at(-1)) continue; // not imported yet: try the next host
return { host, status: res.status, body: await res.json() };
} catch { /* network error: try the next host */ }
}
return null;
}
I ran it against both services. The demo key came back from clavem.io as valid, and an unknown key fell through to Lemon Squeezy and returned its 404. One caution: a Clavem 404 can also mean instance_id not found, where the key exists but the device was not imported. Read error before falling through, or only fall through when it says license_key not found.
What breaks after the move
Hard-coded id checks. Lemon Squeezy’s documentation tells apps to compare meta.store_id, meta.product_id and meta.variant_id with the values for their own store. Imported keys keep those original ids in meta. A license sold after the move is issued by the new service with its own ids, so an app that checks a single hard-coded store id rejects every new customer. Accept both sets of ids, or switch to the signed token’s pid claim for the product check.
Subscription licenses. An imported license has no Stripe subscription behind it in the new system, so Stripe renewal events do not extend it. Give imported subscription licenses an expiry that covers the overlap, extend them by hand when a customer renews, or re-issue them through a new Stripe purchase. A subscription that you moved to Stripe will bill, and the license needs your attention.
Webhook-driven provisioning. If your backend listened to Lemon Squeezy webhooks to learn about new license keys, those stop. Clavem has no outbound webhooks. Read license state with the management API instead.
Old app versions. Builds already installed keep calling the old host. Show an in-app message asking people to update while the old host still works, and keep the download page current.
Plan the rollback and the message
Decide before you ship what you will do if validation behaves differently from the old service. The safest rollback is also the reason for the dual-host fallback: because the new app build still asks the old host for keys the new one does not know, you can pause the import, fix the data and re-run it without locking anyone out. A repeated import never overwrites a key that already exists in the account. It only adds devices the key did not have.
Tell customers three things in your update notes: that their key does not change, that they should update the app, and what to do if the app says the key is not found. For the last, a short line pointing to your support address is enough, along with the device-management page where they can see and remove activations. Customers who were never told anything are the ones who write in, and a clear note saves the most mail.
Keep a list of every place the old hostname appears: the app, any website that validates keys server-side, build scripts, support tools and documentation. Lemon Squeezy’s guide lists “APIs and webhooks” among the integrations that do not redirect on their own, so a search of your repositories for the old hostname is part of the migration, not an afterthought.
Doing this with Clavem
The importer is described on the import page, and the Lemon Squeezy migration page has the sequence for sellers moving from a store that is closing. Keys keep their exact value, so customers do not need new ones.
Questions
Do apps already installed keep working after I move to a new license service?
Only if they can reach a service that knows their keys. An installed app calls the hostname it was built with. If that service stops answering, the app cannot validate online, so ship an update with the new hostname and keep the old host as a fallback while both exist.
Will the Lemon Squeezy License API keep answering after the shutdown?
Lemon Squeezy's migration pages say processing stops on 31 March 2027. They do not say whether the License API keeps answering after that date, so plan as if it will not.
Why does my app reject licenses sold after the migration?
Lemon Squeezy's documentation tells apps to check the store, product and variant ids in the response. Imported keys keep their original ids, but licenses sold after the move carry the new service's ids, so a hard-coded id check fails.