Migration
Move from auth.gg or KeyAuth with a plan your customers can follow.
A licensing migration touches your application, customer access, and support process. Treat it as a tested cutover, not a weekend rewrite.
auth.gg and KeyAuth both provide licensing and authentication workflows, including key-based access and hardware-related controls. If you are moving from either one, the important work is not merely changing an endpoint: it is preserving the access rules your customers already understand while improving the operations behind them.
Inventory the access you already sold
Start with one system at a time. List the license types you have issued and their expiry rules. System Locker will not import certain personally-identifiable information, so you may skip that part.
We can help you map that model into System Locker's systems, keys, and authentication choices. We will also help you set up admin and reseller roles. The exact import and cutover path depends on the data you can export and the way your existing client is integrated, so it should be agreed before customers are asked to move.
Prove the new integration before the cutover
Create a test system and use real test keys before changing your production build. Confirm the login flow your app needs, version behavior, hardware handling, error messages, and the support tools your team will rely on after launch.
For a first pass, key-only Mikros is often the simplest fit. If you need account-based access, our auth APIs support that via the "Goliath" variations. When you're ready for launch, consider a production session with rotating heartbeat tokens instead.
Set one clear changeover point
Decide which build begins using System Locker, how long any old build remains supported, and what customers need to do. A concise announcement, an updated download, and a support path for edge cases are better than leaving two competing licensing states open indefinitely.
After the move, use authentication logs and the developer portal to watch the first real customer activity. That early window is the time to resolve missing records or unexpected device changes before they become a recurring support problem.
Start the migration conversation early.
Bring the details of one existing system, including its current key and expiry rules, and we can help you plan the first tested move.