Migrate from KeyAuth
Plan entitlements, import keys, update the client and test the rollout
Moving from KeyAuth to PWF Auth involves customer entitlements, application code and the rollout of a new build. Keeping the same key strings can reduce customer friction, but the two systems do not share sessions or automatically synchronize licensing rules.
1. Record the existing entitlements
Before changing your production integration, retain an export of the customers and keys you intend to migrate. Record expiry or remaining time, active and banned status, permitted devices and the product each key unlocks. Keep a separate record of accounts or subscriptions that need a different migration path.
2. Create a test application
Follow Getting started and configure a separate test application. Match the intended rules in Applications, including sign-in behavior, trial settings and device limits. Import only a small set of your own test keys first.
The Import dialog accepts up to 5,000 keys at a time, one per line. Existing keys are skipped. Enable Other key formats when needed. Group imports by the intended duration and device allowance; review active customer entitlements before applying a plan to production keys.
3. Replace the licensing flow
| Responsibility | PWF Auth integration |
|---|---|
| Initialize your application | Configure the SDK with the new application's secret. |
| Authenticate a license key | Call the SDK login method and check success before unlocking protected work. |
| Maintain access while running | Start the heartbeat and handle the session-ended event. |
| Move a customer to another PC | Implement the configured hardware reset flow. |
| Issue or renew from your store | Configure a supported store integration or a scoped server-side Developer API key. |
Use the complete guide for C# / VB.NET, Python, C++ or Node.js / Electron. Method names and error handling are not interchangeable with another provider's SDK.
4. Test customer outcomes
- Valid keys sign in, while banned and expired entitlements remain refused.
- Imported customers receive the intended amount of access.
- Device binding and approved hardware changes behave as expected.
- A ban while the application is running reaches its session-ended handler.
- Network loss follows the chosen SDK's policy.
- Purchases and renewals issue the correct key once, including retried notifications.
5. Roll out the client update
Start with a small pilot and explain any sign-in or device-reset change to those customers. Deliver the new build through a channel the old client already uses. PWF Auth's update system cannot force an unmodified KeyAuth-only binary to migrate.
Keep the previous working build and entitlement export available while you verify the rollout. Decide which service is authoritative during the transition so a refund or ban is not applied to only one side. After adoption, retire the old integration according to your customer commitments.
Common questions
Can customers keep their key strings?
Yes, importing strings is supported. Remaining time, accounts and device bindings still need a migration plan.
Will an old build automatically use PWF Auth?
No. You must ship an updated client that uses PWF Auth's integration.
Can I move customer passwords with key import?
No. Key import is not an account or password migration. Plan the account sign-in transition separately and do not ask customers to send passwords through support.
Review the KeyAuth comparison, key import documentation and store integrations, then start with a test application.
Something missing or unclear? Tell us on Telegram