Short answer up front: there are two ways to move Google Authenticator to a new phone. Use the old phone's "export accounts" feature to scan a code onto the new phone (the fastest route), or manually rebuild it on the new phone using the 16-character recovery key you saved earlier (this only works if you backed it up in advance). The second method is your only option if the old phone is already lost or broken. Once you're done, immediately test logging in at the Binance Official Site; app users can test the same way through the Official Binance App; iPhone users should follow the iOS installation guide to get the app set up first.
Google Authenticator doesn't connect to the internet or sync to the cloud by default. If you don't actively migrate it when you switch phones, your Binance entry simply won't appear on the new device, and your 2FA will stop working. Below is the full step-by-step for both migration methods, plus what to do if either one fails.
Google Authenticator is essentially a local-only tool:
When you switch phones, the new phone's Authenticator has no secret key stored, so it can't generate a valid code. Migration is really just about moving that secret key to the new device.
If your old phone still works and you can still open the Authenticator app, this is the fastest route.
Open Google Authenticator on the old phone, tap the three-dot menu in the top right, and select "Transfer accounts."
On some older versions this is labeled "Export accounts."
The app lists every 2FA account currently stored, including Binance and any other sites. Check the box next to "Binance"; you can select multiple other accounts to export at the same time.
Tap "Next."
The screen displays a QR code (a black-and-white square pattern). This code contains the secret keys for every account you checked.
Don't screenshot this code and post it anywhere online — anyone who gets hold of that screenshot can generate the same Authenticator codes as you and log into all of your accounts.
Download Google Authenticator on the new phone, tap the "+" in the bottom right, choose "Scan a QR code," and point the camera at the migration code on the old phone.
After scanning, the app shows "X accounts will be added" — tap "Import." Once the import finishes, your Binance entry appears in the new phone's Authenticator.
Log out of Binance and log back in. After entering your email and password, Binance will ask for a 2FA code. Open Authenticator on the new phone and enter the 6-digit code next to the Binance entry. A successful login means the migration worked.
If you're retiring the old phone:
If you're keeping the old phone as a backup device, it's fine to have both Authenticators active side by side — either one works for logging in, since they generate identical codes.
If your old phone is lost, broken, or stolen, Method One is off the table and the recovery key is your only option.
The recovery key is the 16-character alphanumeric string (also called the Setup Key) that was displayed on screen when you first linked 2FA. If you followed our advice and saved it in a password manager or on paper, dig it up now.
If you never saved a recovery key, skip ahead to "Method Three: Appeal for a 2FA Reset."
Search your app store for "Google Authenticator" and install it.
Open the app, tap the "+" in the bottom right, and choose "Enter a setup key" (not "Scan a QR code").
Fill in:
Tap "Add." The account appears in the app's list and starts generating 6-digit codes.
Log out of Binance and log back in, then enter the code Authenticator just generated. A successful login confirms the recovery worked.
Once you're back in your account via the recovery key, immediately:
If you never saved a recovery key and the old phone is unusable, your only path forward is Binance's "reset 2FA" appeal process.
No. This is Binance's anti-theft design and applies to every user equally. Even support staff cannot skip the waiting period. That's exactly why you should always keep your recovery key saved — so you're never stuck waiting 7 days.
| Method | Requirement | Time Needed | Fund Restrictions |
|---|---|---|---|
| Scan-and-export from old phone | Old phone still works | 5 minutes | None |
| Manual rebuild with recovery key | Key was saved | 3 minutes | None |
| Appeal for a 2FA reset | Neither of the above | 7+ days | No trading/withdrawals for 7 days |
Many people have more than just Binance in their Authenticator — Coinbase, Gmail, AWS, GitHub, and a dozen others besides. Migrating everything at once when you switch phones is far more efficient.
With Method One: check every account you want and generate a single QR code that imports all of them in one scan.
With Methods Two and Three: each account has to be handled individually. We recommend using a password manager (like 1Password) to keep a "secure note" for each account listing its recovery key and where that key came from.
Using Authy avoids this hassle entirely: Authy is a cloud-synced alternative to Authenticator. Log into your Authy account and every 2FA entry is restored automatically — no extra steps when you switch phones. The trade-off is that the security of your Authy account itself becomes critical, so your password needs to be strong and 2FA needs to be turned on.
Mistake One: The Binance entry is still on the old phone after exporting
This is normal — the old phone's entry isn't deleted automatically. If you want a clean handoff, delete it manually on the old phone.
Mistake Two: The code on the new phone doesn't match after scanning
This is usually a clock sync issue on the new phone. Go into Authenticator → Settings → Time correction → Sync now.
Mistake Three: Import shows "invalid QR code"
The migration QR code generated on the old phone has a short expiry window and stops working after a few minutes. Generate a fresh one and scan again.
Mistake Four: Two Binance entries show up in Authenticator
This happens if a backup accidentally gets scanned twice, producing two identical Binance entries that generate the same code. Just delete the extra one.
Mistake Five: Manually entering the key says "invalid key"
Check whether you mistyped a character when copying the key (0 and O, or 1 and l, are easy to mix up). Recheck the full 16 characters and re-enter it.
Q: Can I migrate Authenticator directly from iPhone to Android? A: Yes. Google Authenticator's export QR code is cross-platform — a code generated on iOS can be scanned by Android, and vice versa.
Q: Does the code on the old phone still work during migration? A: Yes. Exporting doesn't wipe the secret key from the old phone. Both the old and new phone will keep generating identical 6-digit codes at the same time.
Q: Can the recovery key be used more than once? A: Yes. The recovery key is generated by Binance's servers when you first bind 2FA, and it stays valid indefinitely (unless you turn 2FA off and back on in your account, which generates a new one).
Q: Can a password manager like 1Password replace Authenticator? A: Yes. 1Password supports TOTP (time-based codes). Scan the 2FA QR code with 1Password when you first bind it, and it will generate the same 6-digit codes. That said, it's slightly less secure than a standalone Authenticator app, since your password and your 2FA end up in the same basket.
Q: Can Authenticator run on multiple devices at once? A: Yes. Scan the export QR code on every device you want, and each one will generate identical codes. That said, it's best not to spread it across too many devices — three or fewer is a reasonable limit.
Q: If I'm changing my phone number and my phone at the same time, which should I migrate first? A: Migrate Authenticator first, since it doesn't depend on your phone number. Once Authenticator is working on the new phone, go into Binance and update the phone number bound to your account (that step requires 2FA verification). Doing it in the wrong order will leave you stuck.
Q: I turned on Google Authenticator's cloud backup — how does switching phones work now? A: The newer version of Google Authenticator supports cloud backup synced through your Google account. With that turned on, logging into the same Google account on your new phone restores everything automatically. We still recommend keeping your recovery key as an offline backup as well.
Q: Can Authy and Google Authenticator run side by side? A: Yes. The two apps don't interfere with each other. If you want to move from Google Authenticator to Authy, you'll need to handle each account individually through an unbind-and-rebind process on Authy.
Test a Binance login right away once you've finished migrating Authenticator, and only deal with the old phone after you've confirmed everything works. Keeping extra backups of your recovery key is always easier than going through a support appeal later.