How to migrate from Luarmor. Bring your keys, rebuild your flow.

The thing most people worry about when leaving Luarmor is their users, and that part is handled: vodka has a bulk key importer, so your existing keys keep verifying for your current users without anyone re-redeeming. What does not carry over automatically is the rest of the project. Account history, users, remaining durations and your old loader URL do not migrate, so you recreate your access rules in vodka and distribute a new loadstring.

Do it one working script at a time, with a way back at every step. This guide is the editorial walk-through; the reference is the migration guide, and the dated, sourced feature comparison is on vodka vs Luarmor.

• Your key strings move. Export your current keys and bulk-import them onto a vodka script. They keep verifying, so your users do not re-redeem.
• Your source moves, as source. You bring your original Lua or Luau code and build a fresh protected release with it. There is no import of Luarmor's protected output.
• Your access rules do not move. Tasks, lifetimes and HWID rules are recreated in vodka. This is a chance to tidy them, not just copy them.
• Your loader URL does not move. An old Luarmor URL does not become a vodka URL. You distribute the new vodka loadstring when you are ready.

Pick one script, ideally not your most popular, and take it all the way through before touching the next. Create it in vodka with your original source, build a protected release, and recreate your key flow: tasks and their order, key lifetime, and HWID rules. Then bulk-import that script's existing keys so its current users carry over.

The key system and all of its checks are enforced on the server, not in the loader, so verify that the imported keys behave the way they should before anyone relies on them.

The loader swap is the only moment your users feel the migration, so earn it with testing first:

• Run the real protected release in its target environment, with its dependencies and error paths.
• Test an imported key, an expired key and a revoked key against the new flow.
• If you use HWID locks, test a second device and a self-service reset.
• Keep your current Luarmor setup available as a fallback during the transition, and tell users plainly what is changing before you switch the loader.

Only when a script passes do you publish its vodka loadstring and point your community at it. Then move to the next script and repeat.