Direct conclusion: There are 3 ways to migrate Google Authenticator when changing phones: cloud backup sync, exporting a transfer QR code, and rebinding using the recovery key—ranging from fastest to slowest. If you neither saved the recovery key beforehand nor enabled cloud backup, you will have to undergo the Binance 2FA reset process (which requires video facial recognition and takes 24-48 hours). For account operations, access the official Binance website; App users can download the Binance Official App for Android, and Apple users can refer to the iOS installation tutorial to download.
Many people factory reset their old phones immediately when upgrading, only to find their new phone lacks Authenticator data, locking them out of their Binance account. Whether you can recover quickly depends entirely on your preparation before the migration.
Comparing the Three Migration Methods
| Method | Prerequisite | Time Needed | Difficulty |
|---|---|---|---|
| Cloud Backup Sync | Old phone enabled Google account backup | 1 min | Very Easy |
| Export QR Code | Old phone is still usable | 3 mins | Easy |
| Rebind w/ Recovery Key | You wrote down the 16-digit key | 5 mins | Easy |
| Reset 2FA (Fallback) | None of the above | 1-2 Days | Medium |
Below are the details for each method.
Method 1: Cloud Backup Sync (Easiest)
Google Authenticator added cloud backup functionality in versions released after April 2023. If your old phone used this version and was logged into a Google account, all verification code entries are automatically backed up to Google Cloud.
Steps
Step 1: Check if Cloud Backup is Enabled on the Old Phone
Open Authenticator → tap your profile picture (top right) → see if it displays "Syncing to xxx@gmail.com". If it does, it's enabled. If not, click to log into your Google account to start syncing.
Step 2: Install Google Authenticator on the New Phone
Search for "Google Authenticator" in the App Store or Google Play (the developer must be Google LLC).
Step 3: Log In with the Same Google Account on the New Phone
Open Authenticator → profile picture (top right) → Sign in → enter the Google account used on the old phone.
Step 4: Wait for Automatic Sync
The new phone will automatically pull all backed-up codes, including the Binance entry. This takes just seconds.
Notes
- Cloud backup is disabled by default, and older versions lack this feature.
- You must use the exact same Google account.
- Users in mainland China need a VPN to log into Google accounts on Android.
- iOS users are generally not restricted by VPN requirements for this.
Method 2: Export Transfer QR Code
If your old phone is still functional, use the export feature to generate a migration QR code.
Steps
Step 1: Prepare the Old Phone for Export
Open the old Authenticator → tap the three-dot menu (top right) → "Transfer accounts" → "Export accounts".
Step 2: Select Entries to Migrate
If you have 2FA for multiple exchanges (Binance, OKX, Coinbase), you can select all or check specific ones. Migrating just Binance is enough.
Step 3: Generate the Transfer QR Code
Tap "Next" to generate a specific QR code. This code is highly sensitive. Whoever scans it gets your 2FA permissions. Therefore:
- Do not screenshot and send it via chat apps.
- Do not let anyone else scan it for you.
- Close it immediately after use.
Step 4: Scan to Import on the New Phone
After installing Authenticator on the new phone, tap "+" → "Scan a QR code" → point your camera at the old phone's screen to complete the import.
Step 5: Clean Up the Old Phone
Once you verify the new phone's Binance entry generates working codes, manually delete the Binance entry from your old phone: long-press the entry → Delete. Otherwise, both phones will generate codes, increasing your security risk.
Notes
- You can export up to 10 entries at a time; do it in batches if you have more.
- The QR code expires in 1 minute, after which you must regenerate it.
- Cross-platform migration is fully supported (iOS export to Android scan, and vice versa).
Method 3: Rebind Using the Recovery Key
If you saved the 16-digit recovery key (letters A-Z + numbers) when you initially set up 2FA, you can rebind it manually on your new phone.
Steps
Step 1: Locate Your Original Recovery Key
Recall where you saved it: a physical notebook, a password manager (like 1Password / Bitwarden), or an encrypted document.
Step 2: Install Authenticator on the New Phone
Download Google Authenticator or the official Binance Authenticator.
Step 3: Manually Add the Key
Tap "+" → "Enter a setup key" → Fill in:
- Account name: Binance
- Your key: Paste the 16-digit key
- Type of key: Select "Time based" (default)
Once added, it will start generating 6-digit dynamic codes.
Step 4: Log In to Binance with the New Code
Go to the Binance login page, enter your password and the new dynamic code. If it logs you in, the migration is successful.
Important Details
The recovery key is essentially the exact same data as the QR code displayed during initial setup, just in text form. If one phone binds it using the key, another phone can bind the same key, and both devices will generate the exact same dynamic codes.
Method 4: Reset 2FA (Fallback Solution)
If none of the above methods work—your old phone is lost, no cloud backup, no recovery key saved—you must go through the Binance 2FA reset process.
Steps
Step 1: Select "Security verification unavailable?" on the Login Page
After entering your email and password, click this link on the 2FA verification page.
Step 2: Choose the Reason for Reset
- Lost phone
- Factory reset device
- Accidentally deleted Authenticator
- Lost recovery key
Step 3: Identity Verification
You will need to submit:
- Photos of the front and back of your ID (or passport)
- A 5-10 second video of yourself holding the ID
- Reading an official prompt sentence
Step 4: Await Review
Standard review takes 24-48 hours. Upon approval, you will be notified via email to rebind your 2FA.
Step 5: Rebind + 7-Day Cooling-Off Period
Binding a new Authenticator triggers a 7-day withdrawal cooling-off period, during which all withdrawals are disabled.
3 Things You Must Do After Migration
Once the migration is complete, immediately do these three things for security:
- Log out of all Binance devices: Account → Security → Devices → Log out of all devices, then log back in with your new phone.
- Resave your recovery key: Go into your Authenticator and write down the current key again (it can be viewed in the entry details on some apps, though Google may hide it; if so, you'd need to rebind entirely to get a fresh one).
- Test a withdrawal: Initiate a small withdrawal to confirm your 2FA works properly.
Best Paths for Different Scenarios
| Scenario | Recommended Method |
|---|---|
| Old phone works + plenty of time | Method 2 (Export QR code) |
| Old phone works + Mainland Android | Method 2 (Doesn't rely on Google services) |
| Old phone works + International User | Method 1 (Cloud sync is fastest) |
| Old phone is broken but you have the key | Method 3 |
| Nothing is available | Method 4 (The forced fallback) |
FAQ
Q: Can the Authenticator on my old phone still be used after migrating to the new one?
Yes. Unless you actively delete the entry, the old phone will continue to generate codes. Both devices generate identical codes because the underlying key is the same.
Q: I accidentally deleted the Authenticator App and lost all data. What do I do?
If cloud backup wasn't enabled, proceed with Method 3 or Method 4. If it was enabled, simply logging back into your Google account will restore the data.
Q: Did an iOS upgrade wipe out my Authenticator?
iOS upgrades typically do not affect app data. If you had iCloud backup on and chose to "Keep app data", reinstalling the app should restore it. Otherwise, follow Method 3 or 4.
Q: Can I use a third-party Authenticator instead of Google?
Yes. Authy, Microsoft Authenticator, and the Binance Authenticator all support Binance 2FA. They all use the standard TOTP algorithm and are fully compatible. Changing apps doesn't require resetting Binance; just scan the original key again.
Q: Should I store my recovery key in cloud notes?
Not recommended. Cloud notes (OneNote, Evernote, Notion) are prime targets for hackers. Putting your key there is handing them the lock. Writing it down on physical paper is the safest, followed by an encrypted local password manager (like 1Password).
Q: Can I withdraw immediately after migrating?
Yes. Export migration and cloud sync do not trigger Binance's risk controls. However, using Method 4 (Reset 2FA) imposes a 7-day withdrawal ban, which is the biggest penalty.
Q: What if I'm changing my phone number at the same time as my phone?
Complete your 2FA migration before changing your phone number. Doing both simultaneously risks getting stuck—you might have the 2FA unready on the new phone while being unable to receive SMS on the old number.
Q: Is Authy's cross-device sync better than Google's?
Authy's multi-device sync is a default feature and feels smoother. However, Authy has dropped support for its desktop version, though mobile is still maintained. Just pick one and stick with it; avoid switching midway.
Summary
The ideal way to migrate Google Authenticator is by having cloud backup enabled beforehand (takes 1 minute). The next best option is exporting a QR code from your old phone (takes 3 minutes). The fallback is rebinding via a saved recovery key. If you prepared nothing, you must endure the 2FA reset process, waiting 1-2 days for facial verification and suffering a 7-day withdrawal ban. Therefore, never skip the step of writing down your recovery key when first setting up 2FA.