Changing phones is one of the most stressful security concerns for cryptocurrency users — how do you migrate Google Authenticator from the old phone to the new one? If handled improperly, you could lose access to exchange accounts and funds. This article provides detailed solutions for every scenario. If you're using an exchange, the first thing you should do after visiting Binance is back up your authenticator keys.
Scenario 1: Old Phone Is Still Available (Easiest)
If your old phone is still functional, the migration process is very straightforward.
Method A: Use Google Authenticator's Transfer Feature
Google Authenticator has a built-in account transfer feature:
- Open Google Authenticator on the old phone
- Tap the three-dot menu in the upper right
- Select "Export accounts" or "Transfer accounts"
- Choose the accounts to export
- A QR code will appear on screen
- Install Google Authenticator on the new phone
- Open the authenticator on the new phone and select "Import accounts"
- Scan the QR code displayed on the old phone
- Verify that the codes on both phones match
Method B: Use Backup Keys
If you saved the secret key (e.g., JBSWY3DPEHPK3PXP) during setup:
- Install Google Authenticator on the new phone
- Tap "+" to add an account
- Select "Enter a setup key"
- Enter the account name and your backup key
- Confirm the new phone's code matches the old phone
Scenario 2: Old Phone Is Lost But You Have Backup Keys
If you previously backed up the key strings:
- Install Google Authenticator on the new phone
- Manually enter each account's backup key
- Restore all accounts one by one
- Log into each platform to verify everything works
This is precisely why we repeatedly emphasize the importance of backing up keys — they're your lifeline when your phone is lost.
Scenario 3: Old Phone Is Lost With No Backup (Most Difficult)
This is the worst-case scenario, requiring you to contact each platform's support to reset the authenticator.
Contact Exchange Support
Using Binance as an example:
- On the login page, click "Unable to use authenticator"
- Select "Reset via identity verification"
- Submit the following materials:
- Registered email/phone number
- ID document photos
- Selfie holding the ID document
- Account-related information (recent trades, deposit records, etc.)
- Wait for review, typically 1–7 business days
- After approval, rebind a new authenticator
Important Notes During Reset
- Some exchanges temporarily disable withdrawals during 2FA reset (typically 24–72 hours)
- Prepare as many identity verification materials as possible to speed up the review
- Don't submit multiple requests, as this may be flagged as suspicious activity
Preventive Measures: How to Avoid This Problem Again
1. Back Up Your Keys
When binding the authenticator, always write down the key string on paper and store it in a safe place (like a safe or sealed envelope).
2. Use Authy Instead
Authy supports encrypted cloud backup and multi-device sync. Even if you lose your phone, logging into Authy on a new phone restores all authenticators.
3. Multi-Device Sync
When binding the authenticator, scan the QR code with two devices simultaneously. If one is lost, the other still works.
4. Save QR Code Screenshots (Encrypted Storage)
Store the binding QR code screenshots in an encrypted password manager (like 1Password or Bitwarden). Don't store them in your phone's unencrypted photo library.
5. Use a Password Manager
Password managers like 1Password and Bitwarden also support TOTP, allowing verification codes to sync across multiple devices.
Security Reminders
When handling authenticator migration, pay extra attention to security:
- Delete old device data after migration: Ensure the authenticator data on the old phone is completely wiped, especially if the old phone will be sold or given away
- Don't migrate in public places: QR codes and keys are sensitive information; being photographed by others equals a leak
- Beware of fake support agents: When contacting an exchange to reset 2FA, confirm you're using official channels. Scammers impersonate support to steal your information
- Verify immediately after migration: After binding on the new phone, immediately try logging in to ensure everything works
- Don't search for "authenticator recovery" services online: These are mostly scams
- Always back up going forward: Learn from the experience and back up every time you bind a new authenticator. You can use the Binance Official App (Apple users, refer to the iOS Installation Guide) to manage security settings within the platform
Where Is Google Authenticator Data Stored?
Authenticator data is stored locally on the phone and is not uploaded to Google Cloud (unless you've actively enabled Google Account sync). This is why losing your phone means losing the verification codes.
Is My Account Safe During 2FA Reset?
Exchanges typically freeze withdrawal functions during 2FA reset to prevent anyone from exploiting this window to steal funds. Login and viewing functions may still be available.
Can I Use Multiple Authenticator Apps Simultaneously?
Yes. You can add the same account to both Google Authenticator and Authy (using the same key). Both apps will generate identical verification codes.
Why Are Codes Wrong After Changing Phones?
The most common reason is inaccurate time on the new phone. Ensure the new phone's time is set to automatic sync. Another possibility is an incorrectly entered key — double-check carefully.
Is Authy's Cloud Backup Secure?
Authy uses end-to-end encryption to protect cloud backups, offering good security. However, you need to set a strong encryption password. If you forget this password too, the backup becomes unrecoverable.