How to Migrate Lemon Squeezy License Keys Without Reissuing Them
Customers can retain the exact key they already have when the key is exportable and its source variant maps to a destination product. Review existing activations and check the licensing call from your backend, app, or plugin.
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.
Which license fields carry over?
LicenseFerry imports the original key text, expiration timestamp, and activation limit. You map the source variant to a destination product and configure its feature entitlements. Disabled keys become revoked. Time-limited keys retain their original expiry, including keys whose expiry has passed.
What happens to existing device activations?
The CLI flags records with existing device activations so you can review them. Legacy instance IDs may not match the identifiers your new client stores. Use --reset-devices only after choosing a reactivation plan, then tell affected customers how to reactivate with the same key. Their original device limit still applies. Dry-run the device reset before importing.
How do I verify that the same keys still work?
- One destination product for every source variant in scope.
- The same key unlocks the expected features in staging, within its eligibility and seat limits.
- Expired and disabled keys fail validation.
- A second import leaves existing equivalent records alone and flags conflicts for review.
Recover if the cutover fails
Save the staging report and track the backend deployment or client release that changed the endpoint. Keep a known-good config and rollback procedure. Use a separately tested rollback destination while its API is available and reconcile any activations created after the cutover.
Follow the CLI migration checklist and test the client’s online license checks. If your app also needs offline validation, compare LicenseFerry and LicenseSeat’s validation workflows.