Lemon Squeezy is winding down. It stopped taking new stores on November 16, 2026 and stops processing transactions, subscription renewals included, on March 31, 2027. Its recommended replacement, Stripe Managed Payments, takes over checkout, tax and disputes, but it doesn't deliver files, download links or license keys.
If you sell software with Lemon Squeezy license keys, that leaves two jobs: move your payments, and move your licensing before your customers' keys stop working. This post covers the second one. You can keep every key your customers already have.
The dates that matter
From Lemon Squeezy's migration guide (checked November 16, 2026):
- November 16, 2026: no new users or stores.
- December 2, 2026: migration tooling for Stripe Managed Payments opens for eligible stores.
- Mid-January 2027: latest recommended start. The full move can take up to 8 weeks.
- March 31, 2027: Lemon Squeezy stops processing transactions.
The licensing deadline is earlier than it looks. Your customers need an app update that checks keys somewhere other than the Lemon Squeezy License API, and that update has to reach them before March 31. Plan to ship it well before then.
What carries over, and what doesn't
Keymint stores each imported key exactly as it is. The string your customer pasted into your app last year is the same string Keymint looks up, so nobody gets a new key and nobody gets an email.
keybecomes the license key, unchanged (upper and lower case kept).user_emailanduser_namebecome the customer: matched by email, or created.activation_limitbecomes the activation limit (empty means unlimited).expires_atbecomes the expiry date (empty means perpetual).statusanddisabled: disabled keys import disabled.instances_countdoesn't carry over: activations start at zero.
That last one is the one to know. Lemon Squeezy's activation instances belong to its API and can't be moved, so each customer's device activates once more with Keymint the first time your updated app runs. It stays within the same activation limit.
Step 1: Export your keys
Lemon Squeezy's List all license keys API returns your keys as JSON, and Keymint reads that response as it is. Pages hold up to 100 keys, so save each page as its own file:
curl -s "https://api.lemonsqueezy.com/v1/license-keys?filter[store_id]=YOUR_STORE_ID&page[size]=100&page[number]=1" \
-H "Accept: application/vnd.api+json" \
-H "Authorization: Bearer $LEMONSQUEEZY_API_KEY" \
> lemon-squeezy-keys-1.jsonIncrease page[number] until a page comes back empty. A CSV with Lemon Squeezy's column names works too.
These files hold your customers' keys, so treat them like passwords: keep them out of shared drives and chat, and delete them once the import is done.
Step 2: Import them into Keymint
- Create a free Keymint account and a product for your app.
- Open the product's License keys tab (or Licenses) and select Import.
- Choose your file. Keymint recognizes the Lemon Squeezy format and checks every row first. Problems are listed with their row numbers, and nothing is saved until they're fixed.
- Select Import.
Importing the same file twice is safe: keys already in the product are skipped. Files of more than 500 keys are sent in batches of 500 for you, and imported keys count toward your plan's license limit. The import guide has the full file format.
Step 3: Switch your app's key checks
This is the part your customers actually see, as an app update. Wherever your app calls the Lemon Squeezy License API, call Keymint instead.
Before:
const res = await fetch("https://api.lemonsqueezy.com/v1/licenses/activate", {
method: "POST",
headers: { Accept: "application/json", "Content-Type": "application/x-www-form-urlencoded" },
body: new URLSearchParams({ license_key: licenseKey, instance_name: deviceName }),
});
const { activated, instance } = await res.json();After, calling the Keymint API directly:
const res = await fetch("https://api.keymint.dev/key/activate", {
method: "POST",
headers: {
Authorization: `Bearer ${KEYMINT_CLIENT_API_KEY}`, // a client key: the kind meant to ship inside your app
"Content-Type": "application/json",
},
body: JSON.stringify({
productId: "YOUR_PRODUCT_ID",
licenseKey, // the same key the customer already has
hostId, // a stable ID for this device: generate it once and store it
}),
});
if (res.ok) {
const { expirationDate } = await res.json(); // null when the key never expires
// Licensed.
} else if ([401, 402, 403].includes(res.status)) {
// Key rejected: invalid, expired, disabled, or over its activation limit.
} else {
// Couldn't reach Keymint: let the user try again.
}It's the same shape as the call you're replacing, so it works from any language or framework. Instead of an instance_name, send a hostId that stays the same for the device: a UUID your app generates on first run and saves, for example.
If you'd rather not write that yourself, the Node.js, Go, Python and C# SDKs wrap the same call and create the device ID for you:
import { KeyMint } from "keymint";
const client = new KeyMint(KEYMINT_CLIENT_API_KEY);
await client.activateKey({
productId: "YOUR_PRODUCT_ID",
licenseKey,
hostId: KeyMint.getOrCreateInstallationId(),
}); // throws on a rejected key, with the same status codesThe Lemon Squeezy calls map like this:
- activate →
POST /key/activate(activateKeyin the SDKs) with a stablehostIdinstead of an instance name. - validate → the same activate call from the same device. A device that's already activated doesn't use another slot.
- deactivate →
POST /key/deactivate(deactivateKey) with the samehostId, to free a slot when a customer moves to a new machine.
Keymint also gives you things the Lemon Squeezy License API didn't have: device-locked activations, floating seats for teams, and signed offline licenses for machines that can't reach the internet. You can switch them on later, per product.
Step 4: Issue keys for new sales
Once payments run through Stripe (Managed Payments or your own account), let your Stripe webhook create a Keymint key for each purchase. Keymint emails the key to the customer. The Stripe subscription licensing guide walks through the webhook, including revoking keys when a subscription ends.
Keymint works with any payment provider that sends signed webhooks, so you're not tied to Stripe either.
A timeline that works
- Now: create your Keymint product and import your keys. They work in Keymint right away, while Lemon Squeezy keeps working too.
- December–January: ship the app update that checks keys with Keymint. Old versions keep using Lemon Squeezy until March 31; new ones use Keymint, with the same keys.
- Before you switch payments: connect your new checkout's webhook to Keymint so new customers get Keymint keys.
- Before March 31: import once more to pick up keys sold since your first import (already-imported keys are skipped; change those in Keymint if they changed in Lemon Squeezy), and remind customers on old versions to update.
Get started
Keymint has a free plan, and paid plans are flat monthly prices with no cut of your sales. See Moving off Lemon Squeezy for a side-by-side comparison, or go straight to the import guide.