How to Migrate Google Authenticator After Changing Phones on OKX
When changing phones and migrating Google Authenticator,the safest approach is: if you still have your old phone, use Google Authenticator's built-in "Transfer Accounts" feature to scan a QR code and migrate everything at once.If the old phone is gone but you have saved the secret key, you can manually add and restore it on the new phone.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!!
Scenario A: Both Old and New Phones Available (Most Recommended)
This is the simplest and lowest-risk method—using Google Authenticator's official export/import feature to transfer all accounts at once.
On the old phone:
Open Google Authenticator, tap the three-dot menu (or profile icon) at the top right.
SelectTransfer Accounts→Export Accounts.
Choose the accounts you want to migrate (select all if desired), then tapNext.
The app will generate a combined QR code. Keep the screen on.
On the new phone:
Download and install Google Authenticator on the new phone.
Open the app, selectImport existing accounts?(appears on first launch).
ChooseScan QR code, then scan the QR code displayed on the old phone.
Once scanned, all account information will sync to the new phone, and theOKXverification codes will work immediately.
After migration, the verification codes on the old phone will still work, but it is recommended to uninstall the authenticator app or clear its data on the old device once the new phone is confirmed working to avoid confusion from dual bindings.
Scenario B: Old Phone Reset or Lost, But Secret Key Saved
If you saved the 16-character secret key provided during binding, you can manually restore it on the new phone.
Install Google Authenticator on the new phone and open the app.
Tap the+icon at the bottom right, selectEnter provided key.
Enter the saved secret key string (Base32 format, typically a 16-character alphanumeric combination).
You can customize the account name, e.g., "OKX Main Account," and set the time step to 30 seconds.
Save, and the verification codes will be restored and usable.
Key point: The secret key is the only credential. As long as you keep it, you can restore the binding no matter how many times you change phones.
Scenario C: Old Phone Gone, No Key Backup—Reset via OKX Security Center
If neither of the above conditions is met, you must reset the binding through the OKX platform's security center.
Prerequisite: You must still be able to log into your OKX account.
On the OKX App:
Open the OKX app, go toSecurity Center, and findAuthenticator App.
TapModify Authenticator App. The system will display a new QR code and secret key.
Use the new phone's Google Authenticator to scan the QR code or enter the key.
Return to the OKX page, enter the SMS verification code and the 6-digit dynamic code from the new authenticator.
Tap submit to complete the change.
On the Web:
Log in to the OKX website, go toSecurity Center→Authenticator App.
ClickModify, then scan the QR code with the new phone.
Enter the SMS verification code and the new authenticator's dynamic code, then confirm and submit.
24-hour restriction after reset: Regardless of the method used to modify the authenticator app, withdrawals and C2C selling will be unavailable for 24 hours after the change. This is a platform risk control measure, not a system error.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!!
Last Resort: Contact Customer Support
If the old phone is lost, the secret key was not saved, and you cannot log into your account, you must contact customer support to unbind.
Open the OKX app, go toHelp Center→Online Support, and send a message like "Unbind Google Authenticator."
Follow the support instructions to submit identity verification materials: front and back of your ID, recent transaction screenshots, and proof of registered phone number/email.
After approval (usually 1-3 business days), the existing authenticator binding will be removed.
Log in again and bind a new authenticator in the Security Center.
How to confirm successful migration
Open Google Authenticator on the new phone—it should display a 6-digit dynamic code. Then use that code to log into OKX. If you can access your account normally, the migration is successful.
FAQ
Can the old phone's Google Authenticator still be used after migration?If you used the export/import method, the codes on the old phone remain valid. It is recommended to uninstall the authenticator app or clear its data on the old device after successful migration to prevent security risks if the old device is used by someone else.
Can Google Authenticator be installed on two phones simultaneously?Yes. You can sync the same codes across multiple devices using the export/import method. However, note that the more devices bound to the same account, the higher the risk of key exposure, so it is generally not recommended.
Can a screenshot of the QR code from the old phone be used for recovery?Yes. If you saved a screenshot of the QR code or secret key during initial binding, you can scan it or enter the key on the new phone to restore. However, if the screenshot remains in your phone's gallery or cloud storage, it poses a leak risk, so it is recommended to delete it after migration.
After migration, if possible, generate a new set of backup recovery codes in the Security Center and store them offline in at least two separate locations (e.g., printed out and saved on an encrypted USB drive). This way, the next time you change phones, you won't need to go through the OKX reset process again.
