← 首页

Moving Your OKX Passkey and Authenticator to a New Phone Safely

Guides · 2026-09-26

Changing phones is one of the few moments when a well-secured OKX account can become inaccessible, not because anything was hacked, but because the security keys were stored on a device you no longer hold. Passkeys live in the credential store of the old phone, and authenticator codes live in an app that may not transfer automatically. If you erase or trade in the old phone before the new one is fully set up, you can lose the second factor that OKX asks for at login, at withdrawal, and when you change security settings. The safe approach is to treat the migration as a two-device operation: keep the old phone alive and signed in until the new phone has been tested end to end, then remove the old credentials deliberately. This guide walks through preparation, the migration itself, verification, and the cleanup and recordkeeping that follow. It is written for readers anywhere who use OKX, and it assumes you already have an account with a verified identity and at least one security key configured. Exact menus, supported methods, and timing rules change, so check the official help centre and your account settings as you go rather than relying on any single description, including this one.

Before you touch the new phone: inventory what is protecting the account

Start by writing down, on paper or in a password manager you can reach from a second device, every method that can currently open or approve actions on your OKX account. Typically that means your password, a passkey stored in the phone's credential manager or a hardware key, an authenticator app generating time-based codes, a phone number or email used for codes, and any recovery codes you saved when you first set things up. Log in to OKX on the old phone and open the security section of account settings to see which of these are listed as active, then note the label and date of each one. Do not screenshot this page and leave it in a photo gallery that syncs to cloud storage you do not control.

Next, decide which methods will move to the new phone and which will stay put. A passkey tied to the old device's credential store will not appear on the new phone by itself, and an authenticator app only transfers if it has an export or backup feature you have deliberately enabled. Anything you cannot migrate must be removed from the account and replaced from the new device, which is why you need at least one working method at all times. If your only second factor is on the old phone, plan to add a temporary second method first, from the old device, before you start removing anything.

Finally, check that you can still receive messages at the email address and phone number on the account. If your phone number is changing with the SIM, update that detail while you still have the old number active, because losing access to the registered number can turn a routine migration into a support case. Record the date you made each change so you can reconstruct the sequence later.

Migrating the passkey and authenticator in the right order

The rule that prevents lockouts is simple: add before you remove, and test before you delete. On the old phone, begin by setting up the new phone's credential manager or authenticator app so it is ready to receive a new credential. Then, still signed in on the old device, add the new passkey or the new authenticator entry to the OKX account from the security settings. Where the platform offers a passkey creation flow, it will usually ask you to confirm with an existing method, which is exactly why the old phone must still be functional at this stage.

Once the new credential appears in the account's list of active methods, do not remove the old one yet. Sign out of OKX on the new phone and sign back in using only the new passkey or the new authenticator code, so you have proof that the new method works on its own. Then perform a low-risk action that requires the same second factor, such as reviewing a security setting or opening a withdrawal confirmation screen without submitting it, to confirm the prompt reaches the new device. If any step fails, stop and fix it while the old phone is still available.

Only after that successful test should you remove the old passkey or the old authenticator entry from the account. If your authenticator app supports exporting accounts, some people prefer to move the existing entry rather than create a new one; either way, verify that the codes generated by the new app are accepted before deleting the old entry, because a mistyped secret or a clock problem will show up immediately as a rejected code. Keep the old phone powered on and connected until you have confirmed that removal completed and that login still works.

Testing the new phone as a real login and approval device

A migration is not finished when the setup screen says it succeeded. It is finished when the new phone has independently carried out every action you normally rely on. Work through a short list: sign in from a fresh session, approve a security-related confirmation, and confirm that notifications or approval prompts arrive on the new device rather than the old one. If OKX uses an in-app approval or a device-based confirmation for withdrawals, open that flow and check that the prompt is delivered to the new phone; you can abandon the flow before submitting if you only want to test delivery.

Pay attention to the small environmental details that break second factors. Automatic date and time must be enabled on the new phone, because time-based codes drift when the clock is wrong. Battery optimisation settings can delay or suppress approval notifications, so check that the OKX app and your authenticator are allowed to run and notify in the background. If you use a hardware key, confirm the new phone can communicate with it, and remember that a hardware key is a separate object that does not migrate with the phone at all.

If something does not work, resist the urge to remove the remaining working method to 'start clean'. That is the moment when a recoverable inconvenience becomes a locked account. Instead, keep the working method in place, note the exact error or behaviour, and consult the official help centre for the current steps for your situation before changing anything else. Support routes and required evidence differ by region and by account state, so follow the instructions shown in your own account rather than a general description.

Cleanup, old-device disposal, and what to record

After the new phone is proven, retire the old one in a controlled way. Remove the old passkey and the old authenticator entry from the account if you have not already, sign out of OKX on the old device, and then erase it. If you are selling, trading in, or giving away the phone, a factory reset is the minimum; if the device stored a passkey in a synced credential manager, also review that manager's list of saved credentials from another device and delete the entry that points at the retired phone. Check that your email account and password manager do not still hold session tokens for the old device.

Then rebuild your recovery position so the next phone change is easier. Confirm that recovery codes are current, that they are stored somewhere you can reach without the phone, and that the email and phone number on the account are ones you still control. If you added a temporary second method during the migration, decide whether to keep it or remove it, and if you remove it, do so only after verifying that at least two independent methods remain. Review the account's active sessions and sign out anything you do not recognise.

Finally, write a short record for yourself: the date you added the new passkey or authenticator, the date you removed the old one, the methods now active, where recovery codes are stored, and any support ticket reference if you needed help. This record is what turns a stressful migration into a repeatable procedure. For anything involving costs, such as fee tiers that may be affected by account changes, check the official fee page rather than relying on memory, and re-check the help centre for current security guidance whenever you repeat this process on a future device.

Risk boundary: OKX Independent Review

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.

Scenario checkpoint