Migrate software licensing from Lemon Squeezy
If customers use a key to unlock a web app, desktop app, or plugin, export your Lemon Squeezy license records and test the original keys before switching endpoints. LicenseFerry’s local CLI supports perpetual and fixed-term keys.
Check one product’s keys locally
Run a free, read-only check with Node.js 24.10 or later and your Lemon Squeezy API key. The CLI reads from Lemon Squeezy and keeps the license keys on your computer. You can run it without a LicenseFerry workspace.
Install the downloaded package. Set LEMON_SQUEEZY_API_KEY in your local shell and replace the example IDs with your store and product IDs. Use --mode live for keys issued to customers and --mode test for test records.
npm install --global ./licenseferry-cli-v0.1.0.tgz
licenseferry inspect --store 123 --product 456 --mode liveThe counts section includes fields like these.
{
"counts": {
"licenses": 24,
"perpetual": 19,
"fixedTerm": 3,
"recurringOrMixed": 2,
"unknownBilling": 0,
"sourceActivations": 12
}
}Perpetual and fixed-term keys are candidates for a staging import. Recurring or unknown billing needs review. If you see existing activations, test an already-activated installation before switching endpoints.
Continue to encrypted export and staging or request a review for one product. Share only aggregate counts and the scenario you want to test.
Export keys while the seller API is available
Group products by variant and distinguish perpetual, fixed-term, and subscription-linked licenses. Save a local encrypted key export and keep a separate copy of your order history. Lemon Squeezy says transaction processing ends March 31, 2027. Check the shutdown timeline and licensing impact.
Test the import in staging
Map each source variant to an existing destination product. Confirm the exact key, expiration, revoked state, and seat limit before changing your app’s endpoint. Resolve conflicts and review existing devices using the key preservation checklist.
Switch the backend or client that validates keys
Find activation, validation, and deactivation calls. Test each against your new API with valid, expired, revoked, and seat-limited licenses. For a web app, verify the key from your backend and check that the signed-in buyer still has access to the right features. For a desktop app, plugin, or extension, test one already-activated installation and plan an update for versions that call the old service.
Use the licensing API contract or the desktop coding-assistant workflow to plan the integration.
Move billing and fulfillment independently
Stripe Managed Payments handles eligible payment migrations. Software licensing and customer download links need a separate fulfillment setup. If your web service grants access from subscription status alone, map existing accounts to the new subscription IDs and test renewals, cancellations, and refunds with your billing integration. The key import covers perpetual and fixed-term licenses. Lemon Squeezy’s fulfillment guidance.
Install the CLI and dry-run an import, compare documented Lemon Squeezy import workflows, or request a read-only migration review.