LicenseFerry API and Migration CLI
Inspect and encrypt your Lemon Squeezy records locally. An active destination workspace is needed for import and verification. The CLI preserves eligible perpetual and fixed-term keys and reports records that need review.
Install the Migration CLI
Use Node.js 24.10 or later. Download the npm package or install it from this URL. The CLI can inspect and encrypt exports locally before your destination is ready.
npm install --global https://licenseferry.com/downloads/licenseferry-cli-v0.1.0.tgz
licenseferry --helpInspect, then export
For a first review, load LEMON_SQUEEZY_API_KEY locally and run inspect for one product. Replace the example store and product IDs with your own and choose the mode that matches your source key. Share only aggregate counts. If you later export, load LICENSEFERRY_ARCHIVE_PASSPHRASE with a generated passphrase of at least 20 characters and keep it separate from the archive.
licenseferry inspect --store 123 --product 456 --mode test
licenseferry export --store 123 --product 456 --mode test --out ./test-licenses.lfls
licenseferry report --file ./test-licenses.lflsDry-run, apply, and verify
Create the destination products in your staging console. Set LICENSEFERRY_ADMIN_TOKEN locally for that organization and map each source variant ID to a destination product slug. List any feature values required by your app.
{
"456": {
"productSlug": "desktop-app",
"entitlements": { "edition": "pro" }
}
}Save the mapping as mapping.json. Replace the example target with your staging origin, review the preview, and apply only after confirming the product mapping and entitlements.
licenseferry import --file ./test-licenses.lfls --mapping ./mapping.json --target https://licenses.example.com --dry-run
licenseferry import --file ./test-licenses.lfls --mapping ./mapping.json --target https://licenses.example.com --apply
licenseferry verify --file ./test-licenses.lfls --mapping ./mapping.json --target https://licenses.example.comThe CLI keeps the original key and flags conflicting records for review. The CLI leaves subscription-linked keys out of automatic import and flags historical device activations for review. For a reviewed device reset, add --reset-devices to preview, apply, and verify. Keep the original device limit and tell affected customers to reactivate on the updated app.
Cut over deliberately
Verify representative activation, retry, seat limit, validation, and deactivation behavior in an app build. Track any remaining clients that still call the old API. Treat a subscription move and a license move as separate projects.
Read the client API guide or use the coding assistant prompt.