Migrate your licensing system without breaking a single key
You already have customers. Move them onto Keylight without re-issuing keys or risking activations — import the keys you already have, keep them working, and offer your latest version as an upgrade.
You don't have to rebuild or reissue your keys
The two things that make migrations scary are rebuilding your licensing and disrupting paying customers. Keylight removes both. The keys you already issued come over as they are, your old app keeps running untouched, and customers move to your new version on their own schedule.
Two options, depending on where you are
Pick the one that matches where your app is today.
Your old app can't ship an update
The old build has its own licensing and never calls Keylight — so nothing you do here can break it. Import your customers into Keylight and the customer portal offers them the move to your new version. The old build runs on its own until they come over.
Your app is shipping a new version
Import your existing customers as they are, so their current key validates in the new build the moment they update — no re-issuing keys, no re-delivery, no support queue.
Example: shipping a major version
Say you've sold v1 through v14 over the years, v15 is going out, and you want to offer your existing customers a discounted or free upgrade.
Import the old keys
Export your customer list and upload it once. The keys you already issued come over intact — each license tagged Migrated, so you can watch the backlog shrink as people move.
Offer the upgrade
Switch on an upgrade to your v15 tier. From the portal, v1 holders move up in a click — same key, new entitlements and limits.
Let the old versions fade
No forced cutover. Old builds keep running on their own while customers upgrade on their own schedule — you retire them once the traffic dries up.
How to bring your users over
Bulk import is the foundation — then customers can self-serve, or we can lend a hand.
Bulk import
Upload your customer list as a CSV. Keep the keys you already have — Keylight creates new ones only where you don't.
See docs for bulk import →Self-claim
Customers migrate themselves — they enter their old key and Keylight issues a fresh one.
See docs for self-serve →Talk to us
Big base, missing keys, or messy data? We'll help you plan the transition.
Email [email protected] →Already selling? We'll move you over.
Switching from Lemon Squeezy, Paddle, Gumroad, Creem, or your own setup is free — we bring your existing customers over and keep the keys you already issued, so nobody has to buy again.
Frequently asked
Will my customers’ existing license keys keep working?+
Yes — when you still have them. Keylight’s bulk import preserves the keys you already issued: upload them and they validate in your Keylight-powered build immediately, with no re-keying. For any customer whose original key you no longer have, Keylight generates a fresh one. Either way the license is tagged Migrated so you can track the cutover.
Do I have to email every customer a new key?+
No. When you import the keys you already issued, customers keep the exact key they have — there is nothing to re-deliver. You only email a key to customers whose original key you could not supply, because those are newly generated.
How long does migrating take?+
The import itself is one CSV upload from Licenses → Import, with a preview before anything is written. Most of the effort is exporting your customer list from your current tool. There is no window where licensing is down — your old build keeps running on its own validation until customers move to your new version.
What if I don't have my old license keys anymore?+
Import by email alone. Keylight generates a fresh signed key for each customer and can email it to them. They swap their old key for the new one the next time they launch — they are never asked to repurchase.
Ready to ship?
Create your account and start licensing your apps in under a minute. Free forever tier included.
Start Free