What Lemon Squeezy says is ending
As of November 2026, Lemon Squeezy’s migration pages give these dates: sign-ups closed on 16 November 2026, migration tooling for Stripe Managed Payments opens on 2 December 2026, the recommended latest start is mid-January 2027, and processing stops on 31 March 2027, including subscription renewals. They also say the deadline cannot be extended and that a full migration takes four to eight weeks.
Two statements matter for software sellers. Managed Payments “doesn’t deliver files, license keys, or download links”, and customers “may lose access to their license keys, files, and links after March 31, 2027” unless you move historical orders to a new fulfillment solution. Payments, keys and your app’s license calls are three separate moves, and only the first has official tooling.
Step 1: back up what Lemon Squeezy holds
The order export (the Export button on the Orders page, delivered by email as CSV) has no license key column, so it is not a key backup. Read the keys from the API instead. This script writes every key with its devices to licenses.json in the format Clavem’s file import reads. Create the API key under Settings, API in Lemon Squeezy. It needs Node 18 or later.
// LS_API_KEY=... LS_STORE_ID=... node export-ls.mjs
import { writeFile } from 'node:fs/promises';
const headers = { Accept: 'application/vnd.api+json', Authorization: `Bearer ${process.env.LS_API_KEY}` };
async function* list(path, filter) {
for (let page = 1; ; page++) {
const url = new URL(path, 'https://api.lemonsqueezy.com');
for (const [k, v] of Object.entries(filter)) url.searchParams.set(`filter[${k}]`, v);
url.searchParams.set('page[number]', page);
url.searchParams.set('page[size]', 100);
const res = await fetch(url, { headers });
if (!res.ok) throw new Error(`${res.status} ${url}`);
const body = await res.json();
yield* body.data;
if (page >= (body.meta?.page?.lastPage ?? 1)) return;
}
}
const licenses = [];
for await (const key of list('/v1/license-keys', { store_id: process.env.LS_STORE_ID })) {
const a = key.attributes;
const devices = [];
if (a.instances_count > 0)
for await (const i of list('/v1/license-key-instances', { license_key_id: key.id }))
devices.push({ instance_id: i.attributes.identifier, name: i.attributes.name, created_at: i.attributes.created_at });
licenses.push({
key: a.key, email: a.user_email, name: a.user_name,
status: a.disabled ? 'disabled' : a.status, // disabled wins over status
activation_limit: a.activation_limit ?? -1, // null means unlimited
expires_at: a.expires_at, created_at: a.created_at, devices,
});
}
await writeFile('licenses.json', JSON.stringify(licenses, null, 2));
Keep this file. It is also your rollback copy.
Step 2: import into Clavem
Create one Clavem product per Lemon Squeezy product and note its id. Then pick the route:
| Route | Keeps instance ids | Keeps original store, product and order ids in meta |
|---|---|---|
| Import, Lemon Squeezy, with an API key | Yes | Yes |
| File import of the JSON above | Yes, from devices |
No |
Use the API route unless you have a reason not to. Apps are told to compare meta.store_id and meta.product_id with their own values, and only the API import carries those numbers across. After a file import, meta carries Clavem’s own ids (the public demo key answers "store_id": 1, "product_id": 1), so any such check in your app needs new constants. The same applies to license_key.id.
Both routes keep the key string, the buyer, the status, the device limit, the expiry and the activated devices. A key already in your account is never overwritten, so a second run is safe. Imports count against your plan, but expired and disabled keys do not. Details are in Import existing licenses.
Import one product first and check the first page of results.
Step 3: check one key by hand
Pick a key and an instance id your app stored, and validate it against Clavem:
curl https://clavem.io/v1/licenses/validate \
-d license_key=38b1460a-5104-4067-a91d-77b872934d51 \
-d instance_id=f90ec370-fd83-46a5-8bbd-44a241e78665
You should see "valid": true and the instance. An instance that was not imported answers 404 with instance_id not found.. Your app should then call activate again instead of treating the key as bad.
Step 4: change the hostname and ship the update
The License API has the same paths, parameters and response shape, so the change is one constant. Installed copies of your app keep calling api.lemonsqueezy.com until the buyer updates, which is why this release has to go out well before 31 March 2027.
const LICENSE_API = 'https://clavem.io'; // was https://api.lemonsqueezy.com
const res = await fetch(`${LICENSE_API}/v1/licenses/validate`, {
method: 'POST',
headers: { Accept: 'application/json', 'Content-Type': 'application/x-www-form-urlencoded' },
body: new URLSearchParams({ license_key, instance_id }),
});
const data = await res.json();
if (!data.valid) showMessage(data.error);
Lemon Squeezy’s License API is rate limited to 60 requests per minute. Clavem allows 120 per 60 seconds per IP address and 60 per 60 seconds per license key. Read the response token if you want offline checks later; see offline verification.
Step 5: connect payments and decide about subscribers
Connect your Stripe account and map each Stripe product to a Clavem product, as described in Connecting Stripe. New purchases then create new Clavem keys. If you use Managed Payments, make one test purchase first: its purchases go through Stripe Checkout, so they should produce the events Clavem reads, but test it rather than assume it.
Subscriptions cannot be moved by Clavem. Lemon Squeezy’s pages say Managed Payments tooling will notify customers at least 14 days ahead and migrate eligible subscriptions, and that only subscriptions paid by card can move to another provider through its intake form. Cash App Pay subscriptions can move to Managed Payments but not elsewhere, and India-issued cards must be reauthorized. Your options for each subscriber are:
- Let the Lemon Squeezy tooling or a provider move the card, then keep the subscription running in Stripe.
- Ask the subscriber to subscribe again through your Stripe checkout link, and give them the new key.
- Keep them on Lemon Squeezy until their period ends, if the date allows.
Imported keys are not linked to a Stripe subscription, so Stripe events never change them. In Lemon Squeezy a subscription key stays valid until the subscription expires, so check what expires_at says on those keys before you trust it. For subscribers, set the expiry to the end of the paid period and move it forward when they renew:
curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
-H "Authorization: Bearer sk_clavem_…" \
-H "Content-Type: application/json" \
-d '{ "expires_at": "2027-05-19T00:00:00Z" }'
If you leave a merchant of record for plain Stripe, tax collection becomes your responsibility. That is general information, not advice; ask an accountant before you switch.
Rollback
Nothing in this plan removes anything from Lemon Squeezy. The import only reads from it, your app change is one constant, and your store keeps operating until 31 March 2027. Put the License API host behind a build flag or remote setting so you can flip it back before the deadline, and export Clavem’s keys from the Licenses screen (Export CSV) if you later move again. If an import went wrong, fix the source data and run it again: keys that exist are skipped, and devices are added once.
Questions
Does Lemon Squeezy's order export include license keys?
No. As of November 2026 the documented columns are identifier, order_number, product_name, variant_name, user_name, user_email, address and card fields, amounts, tax fields and date_utc. There is no license key column, so read keys from the API.
Will the License API at api.lemonsqueezy.com keep answering after 31 March 2027?
Lemon Squeezy does not document this. Plan as if it stops, and ship an app version that calls a service you control before the deadline.
Can PayPal subscribers be moved?
Not as PayPal subscriptions. Lemon Squeezy's migration pages say they cannot migrate to Managed Payments or to another provider, and customers must start a new subscription with a supported payment method.
Sources
- Lemon Squeezy migration guide (checked November 2026)
- Lemon Squeezy wind-down FAQs (checked November 2026)
- Lemon Squeezy digital fulfillment migration page (checked November 2026)
- Lemon Squeezy API, the license key object (checked November 2026)
- Lemon Squeezy API, list all license keys (checked November 2026)
- Lemon Squeezy API, list all license key instances (checked November 2026)
- Lemon Squeezy License API overview (checked November 2026)
- Lemon Squeezy, exporting orders (checked November 2026)
- Lemon Squeezy, license keys and subscriptions (checked November 2026)