Migrating Lemon Squeezy license keys without locking out a single user
Updated November 2026 · Lemon Squeezy stops processing payments March 31, 2027
If you sell a desktop app, a WordPress plugin, a Figma plugin, a CLI or anything else that asks for a license key, you have a problem the SaaS founders don't: your code is already running on your customers' machines, and it's calling Lemon Squeezy.
Lemon Squeezy's license API (/v1/licenses/activate, /v1/licenses/validate, /v1/licenses/deactivate) stops working when the platform shuts down. Every copy of your app that checks a key against it needs to be pointed somewhere else before March 31, 2027, through an update your users actually install.
Moving the keys is the easy part. This guide is about the hard part: keeping old installs working.
Step 1: Export keys and activations
You need more than the key strings. For every key, export:
- the key itself
- status (
active,inactive,expired,disabled) activation_limitandactivation_usageexpires_at- the order and customer it belongs to
- every instance (activation): instance ID, name and when it was created
Activations matter. If you drop them, every customer suddenly has all their seats free again, or worse, your new system thinks they've used none and lets keys be shared freely.
// List all license keys for a store (Lemon Squeezy API, JSON:API format)
const BASE = "https://api.lemonsqueezy.com/v1";
const headers = {
Accept: "application/vnd.api+json",
Authorization: "Bearer " + process.env.LS_API_KEY,
};
async function listAll(path) {
const out = [];
for (let page = 1; ; page++) {
const res = await fetch(BASE + path + "&page[number]=" + page + "&page[size]=100", { headers });
const json = await res.json();
out.push(...json.data);
if (page >= json.meta.page.lastPage) break;
}
return out;
}
const keys = await listAll("/license-keys?filter[store_id]=" + process.env.LS_STORE_ID);
const instances = await listAll("/license-key-instances?filter[store_id]=" + process.env.LS_STORE_ID);
The full export, including every other resource, is in How to export all your Lemon Squeezy data.
Step 2: Decide where keys will live
Option 1: your new provider's built-in license keys. Polar and Dodo Payments both have license keys built in. If you're moving there, check whether you can import existing keys with their activation counts. If you can, keys keep their exact strings and your customers never need a new one.
Option 2: your own key service. If you're moving to Stripe Managed Payments or Paddle (no built-in keys), or the import isn't possible, run a small key service yourself: a table of keys and activations, plus an endpoint your app calls. Your new provider's order paid webhook creates keys for new customers.
Step 3: Put an endpoint you own in front of it
Whichever option you choose, don't point your app straight at a payment provider's API again. Point it at an endpoint on your own domain, like https://license.yourapp.com/validate, which talks to whatever system holds the keys.
That way, if you ever change provider again, you change one server. Not every install of your app.
A neat trick: make your endpoint accept the same request and return the same response shape as Lemon Squeezy's license API. Then your app update is a one-line change, the base URL, and your existing parsing code keeps working.
// A Lemon Squeezy-compatible /validate endpoint (simplified)
app.post("/v1/licenses/validate", async (req, res) => {
const { license_key, instance_id } = req.body;
const key = await db.licenseKeys.find(license_key);
if (!key) return res.status(404).json({ valid: false, error: "license_key not found." });
const instance = instance_id ? await db.instances.find(key.id, instance_id) : null;
const valid = key.status === "active" && (!key.expires_at || key.expires_at > new Date()) && (!instance_id || !!instance);
res.json({
valid,
error: valid ? null : "license_key is not active.",
license_key: {
id: key.id, status: key.status, key: key.key,
activation_limit: key.activation_limit, activation_usage: key.activation_usage,
created_at: key.created_at, expires_at: key.expires_at,
},
instance: instance ? { id: instance.id, name: instance.name, created_at: instance.created_at } : null,
meta: { store_id: key.store_id, order_id: key.order_id, product_id: key.product_id,
variant_id: key.variant_id, customer_email: key.customer_email },
});
});
Step 4: Ship the app update, early
This is the step with a hard deadline you don't fully control. Users have to install the update, and app store and plugin directory reviews take time.
- Release the update in January 2027 at the latest, so it has months to spread.
- Validate against your own endpoint first, and fall back to Lemon Squeezy while it still exists.
- Cache successful validations locally with a timestamp, and allow an offline grace period (say 14–30 days). Then a short outage, or the Lemon Squeezy cutover itself, doesn't lock anyone out.
- Log which app versions are calling Lemon Squeezy directly, so you can see the old builds disappear.
Step 5: Decide what old builds do
Some users will never update. After March 31, 2027 their copy of your app calls an endpoint that no longer answers. You choose what happens:
- Strict: treat "can't validate" as "invalid". Simple, but you'll lock out paying customers and get support tickets.
- Lenient: if the last successful validation was recent, keep working and show a banner asking them to update. This is what we recommend for most products.
Whatever you choose, email customers with keys before the deadline: "Please update to version X so your license keeps working." Link straight to the download.
By destination
| Destination | License keys |
|---|---|
| Stripe Managed Payments | Not built in. Run your own key service fed by Stripe webhooks |
| Paddle | Not built in on Paddle Billing. Run your own key service |
| Polar | Built in as a benefit. Check whether existing keys can be imported |
| Dodo Payments | Built in. Check import of existing keys and activation limits |
| Creem | Supported. Confirm import and validation options |
Don't want to do this yourself? We'll do the whole migration at a fixed price.
Questions
Will my existing Lemon Squeezy license keys keep working after migrating?+−
They can, if you import them into the new system with their activation counts and point your app at an endpoint that validates them. Key strings can stay exactly the same.
Do I need to release an app update?+−
Yes, if your app calls the Lemon Squeezy license API directly. Old builds can't reach Lemon Squeezy after shutdown. Ship the update early so it spreads before March 31, 2027.
Can I build an endpoint that's compatible with the Lemon Squeezy license API?+−
Yes. Accept the same request fields and return the same response shape, then your app update only needs to change the base URL.
Which Lemon Squeezy alternatives have built-in license keys?+−
Polar and Dodo Payments have license keys built in, and Creem supports them. Stripe Managed Payments and Paddle Billing don't, so you'd run your own key service.