Transferring Google Authenticator to a New Phone
New phone day should be exciting, not stressful, but for anyone with a dozen or more accounts protected by Google Authenticator, it's usually the moment a small wave of dread sets in. The good news is that transferring has gotten genuinely easy since Google added a proper migration flow, and there are three separate ways to do it depending on what you have access to. The less-good news is that the built-in transfer has a few sharp edges that trip people up, especially anyone with a large number of accounts. This guide covers the clean path, the common failure points, and how to decide whether you should even stick with Google Authenticator once you're set up on the new phone.
Before You Touch Your Old Phone
The single most common mistake is wiping, selling, or handing off the old phone before confirming the new one actually works. Do not do anything irreversible until you've checked all of the following:
- Your old phone is still charged, unlocked, and in your possession
- Google Authenticator on the old phone is updated to its latest version, since older versions handle the transfer flow differently or lack it entirely
- Your new phone has Google Authenticator installed and is connected to the internet
- Both phones can be placed side by side, since one method requires scanning a QR code from one screen with the other phone's camera
If your old phone is already gone, broken beyond use, or you never got to this checklist in time, skip straight to the "Old Phone Is Already Lost" section further down, that's a different recovery path entirely.
Method 1: Google Account Sync
Since Google added cloud sync, this is the path most people should use first. On your old phone, open Google Authenticator, tap the profile icon in the top right, and check whether your accounts show as already synced to your Google account. If not, tap the option to back up codes using your Google account and sign in. Give it a moment, a small cloud icon with a checkmark confirms sync completed. On the new phone, install Google Authenticator and sign in with that same Google account, and every account reappears automatically, no QR scanning required at all.
The trade-off is one worth understanding rather than dismissing: your 2FA secrets are now stored inside your Google account. If you'd rather nothing touch Google's servers, use Method 2 instead.
Method 2: Direct Phone-to-Phone Transfer
This is the method that moves accounts directly between devices using a locally generated QR code, nothing goes through Google's servers at any point. On the old phone, open Google Authenticator, tap the three-dot menu, choose "Transfer accounts," then "Export accounts." Select which accounts to move, you can select all of them at once, and tap Next. One or more QR codes will appear on screen.
On the new phone, open Google Authenticator, tap the three-dot menu, choose "Transfer accounts," then "Import accounts," and tap "Scan QR code." Point the new phone's camera at the QR code shown on the old phone's screen.
Here's the part that catches people off guard: Google Authenticator can only fit a limited number of accounts into a single QR code, roughly ten per code depending on account name length. If you have more accounts than that, the export screen will generate multiple QR codes in sequence rather than one. You need to scan every single one of them on the new phone, in order, and it's easy to assume you're done after the first scan when two or three more are still waiting. Before you close the app, double check the account count on the new phone matches the count you exported from the old one.
Once every account shows up correctly, do not immediately delete anything from the old phone. Verify first, covered below, then remove the accounts from the old device afterward to avoid confusion about which device is now the "live" one.
Method 3: Manual Re-Enrollment
If your old phone still works but is too outdated to support the transfer feature, or the app itself is an old version that predates it, you can still move accounts one at a time manually. Log in to each service on a computer, navigate to its security or two-factor authentication settings, disable 2FA (you'll be asked to enter the current code from your old phone to confirm), then re-enable it and scan the fresh QR code with your new phone. It's slow if you're doing this for fifteen or twenty accounts, but it's completely reliable and works regardless of app version.
What Actually Goes Wrong During Transfer
Beyond the multi-QR-code issue above, a few other problems come up repeatedly. Codes that show as "invalid" immediately after a transfer are almost always a clock drift issue, not a failed transfer, TOTP codes depend on both phones agreeing closely on the current time, and a phone with automatic time sync disabled will generate codes that are subtly out of step. Our guide on fixing authenticator time sync issues walks through the exact settings to check.
Another common failure: partial transfers where some accounts appear correctly and others silently don't show up at all. This usually means one of the sequential QR codes from Method 2 was missed during scanning, or the export step selected only some accounts rather than all of them. Recount before you trust the migration is complete.
Finally, some services detect a 2FA re-enrollment as a suspicious security event and will send you an email alert or temporarily require you to re-verify your password. That's expected behavior, not a sign anything went wrong, most services do this specifically because a 2FA change is a common attacker move.
Old Phone Is Already Lost or Broken
If you no longer have the old phone in hand, none of the transfer methods above apply. Instead:
- Check whether Google account sync was already enabled before the phone was lost, if so, install Google Authenticator fresh on the new phone and sign in, your accounts will reappear
- Use any backup codes you saved when you first set up 2FA on each account
- Fall back on each service's individual account recovery process, our full walkthrough is in Lost Your 2FA Device? Here's What to Do
Verify Everything Before You Wipe the Old Phone
This step gets skipped constantly and it's the one that actually prevents lockouts. For every single account that transferred, open it in Google Authenticator on the new phone, log in to the corresponding service, and confirm the code is accepted. Do this one account at a time rather than assuming a successful-looking transfer screen means every code actually works. If you want to sanity check a specific secret key independently, our browser-based TOTP code generator will generate the current code for any secret so you can compare it against what your app shows, useful for spotting a bad transfer before it becomes a lockout.
Should You Switch Authenticator Apps Instead of Just Transferring?
A phone upgrade is a natural moment to reconsider whether Google Authenticator is still the right tool, since you're already about to re-touch every account's 2FA settings. A few honest signals that it's worth switching:
If you've been burned by a lost-device scenario before and want backup you fully control rather than depending on Google's sync, Aegis on Android gives you a local encrypted vault with reliable export and import, no cloud account required. If you're on iOS and want the same local-first philosophy, Raivo offers a comparable open-source approach with an iCloud backup option you opt into rather than one forced by default. If you already use Bitwarden as a password manager and want your codes to live alongside it (run as a standalone app rather than merged into your vault, so you don't collapse two factors into one), Bitwarden Authenticator is worth the switch.
If none of that resonates and Google Authenticator has simply worked fine for you, there's no urgency to change. The transfer methods above exist precisely so you don't have to switch apps just because you switched phones.
Frequently Asked Questions
Can Google Authenticator run on two phones at the same time?
With Google account sync enabled, yes, both phones will show valid codes for every synced account simultaneously. Without sync, the built-in export and import feature moves accounts rather than duplicating them, so if you want both phones active you'd need to re-export from the source phone a second time before removing anything.
Will my codes stop working the moment I start the transfer?
No. Accounts on the old phone stay fully active until you manually delete them there. During the transfer window, both the old and new phone will generate valid, matching codes for the same accounts.
I finished the transfer but codes on the new phone are rejected. What's wrong?
The overwhelming majority of the time this is a clock sync problem, not a bad transfer. Go to the new phone's date and time settings and confirm "automatic date and time" is switched on. Even a drift of thirty to sixty seconds is enough to make otherwise-correct codes fail, since TOTP codes are time-windowed.
Can I move directly from Google Authenticator into Authy or another app?
Not as a direct import, there's no cross-app transfer standard between different authenticator apps. You'll need to disable and re-enable 2FA on each account individually, scanning the fresh QR code into whichever new app you've chosen instead.
I have around 30 accounts. How many QR codes should I expect during export?
Expect somewhere around three to four QR codes for that many accounts, since each code can only hold a limited batch. Scan every code shown in sequence, and count the total accounts on your new phone afterward to confirm none were skipped before you consider the migration finished.
