A new phone should be a happy upgrade, right up until you realize your two-factor codes live on the old one and every account is about to ask for a number you can no longer see. Google Authenticator has a good answer to this, and it does not require the cloud: a built-in export that hands your codes to the new phone over a QR code, entirely offline. The trouble is that people do it in the wrong order, wipe or return the old phone too soon, or hit one of a few predictable snags and end up locked out anyway. Done in the right sequence, the move takes a couple of minutes and touches no server. Here is how to transfer Google Authenticator to a new phone safely, and how to get unstuck when the export does not go smoothly.
The single rule that prevents most disasters is simple: do the transfer while the old phone still works and still has your codes, and confirm the new phone before you erase or hand back the old one. Everything below is built around that order.
Before you start, do this first
Install Google Authenticator on the new phone from its official app store, but do not add any accounts to it yet, since the import will bring them over. Keep the old phone charged, unlocked, and nearby, because the export is generated from it. Know what carries over: only the accounts stored inside Google Authenticator transfer, not codes kept in other apps or accounts secured by text-message codes. And decide your method now. The offline QR export needs no account and no internet, while Google’s newer optional cloud sync backs your codes up to your Google account instead. This guide uses the offline export, which keeps everything on your two devices.
The offline transfer, step by step
On the old phone, open Google Authenticator and tap the menu, then choose Transfer accounts and Export accounts. The app asks you to confirm with your fingerprint or lock-screen PIN before it will show anything, which is a safety step, not a glitch. Next it lets you tick the accounts you want to move, all of them by default, and then it displays a QR code. On the new phone, open Google Authenticator, tap the plus button, choose Import accounts and then Scan QR code, and point the camera at the old phone’s screen. The accounts appear on the new phone within seconds, still generating the same codes. Menu wording shifts a little between app versions and between Android and iPhone, but the path is always export on the old, import on the new. Google’s own Authenticator help shows the current screens if yours look different.
If you have a lot of accounts
The export is not always a single QR code. Google Authenticator packs a limited number of accounts into each code, around ten, so if you protect many accounts you will get a series of QR codes to scan one after another, and the iPhone app tends to split them more aggressively. Scan each one in turn until the new phone has them all. One detail matters here: Google does not let you regenerate the exact same export later, so before you scan, take a screenshot of each QR code as a temporary safety net, and delete those screenshots once the move is confirmed. That way a mid-scan interruption does not strand you.
Verify the new phone before you wipe the old one
This is the step people skip and regret. Before you factory-reset, sell, or return the old phone, prove the new one works. Pick one important account, log out and back in on a computer or another device, and complete its two-factor prompt using the code now showing on the new phone. If it accepts the code, the transfer took. Only then should you retire the old phone. Keeping it intact and in your hands until you have confirmed at least one or two logins is the difference between a clean upgrade and a frantic recovery. There is no rush to erase the old device the same day.
When the offline transfer is not possible
The QR export only works if the old phone still functions and shows the codes. If that phone is already lost, broken, or wiped, there is nothing to export from, and the path changes. If you had turned on Google Authenticator’s optional cloud sync earlier, sign into the app with the same Google account on the new phone and your codes should restore. If you did not, you cannot recover the codes from the app itself. Instead you recover each account individually: use the backup or recovery codes you saved when you first set up two-factor, or go through each service’s account recovery process to disable and re-enable two-factor on the new phone. It is slower, which is exactly why doing the transfer before the old phone is gone matters so much.
Common problems and quick fixes
A few snags come up repeatedly. If the new phone will not scan the QR, turn up the old phone’s screen brightness, hold it steady, and make sure you chose Scan QR code rather than manual entry. If only some accounts came across, you likely had multiple export QR codes and missed one, so run the export again and scan every code it produces. If the codes on the new phone are rejected as wrong even though they look right, the usual cause is the phone’s clock: set the date and time to update automatically, since these codes are time-based and a drifting clock produces codes the server will not accept. And remember that moving to a new phone does not change the accounts themselves, so if one service still shows the old device, remove it in that account’s security settings once the new phone is confirmed.
Two-factor protects your most sensitive accounts, so treat this carefully. App menus and steps differ across versions and between Android and iPhone, keep your saved backup codes somewhere safe as a fallback, and never wipe the old phone until you have logged into at least one account with the new one. When money or identity is involved, verify each critical account rather than assuming the batch moved.
What To Know
- Google Authenticator moves codes to a new phone offline with a built-in QR export, no cloud or internet required.
- Export on the old phone through Transfer accounts, then Import accounts and scan the QR on the new phone.
- Many accounts produce several QR codes, around ten each, so scan them all, and screenshot them as a temporary backup.
- Verify a real login with a code from the new phone before you factory-reset, sell, or return the old one.
- If the old phone is already gone, restore only works if you had cloud sync on; otherwise recover each account with its backup codes.
Frequently Asked Questions
Can I move Google Authenticator without a cloud backup?
Yes. Google Authenticator has an offline export that transfers your codes directly from the old phone to the new one over a QR code, with no Google account or internet involved. On the old phone, open the menu and choose Transfer accounts, then Export accounts, and on the new phone choose Import accounts and scan the code. Cloud sync is a separate, optional feature. The QR method keeps everything between your two devices, which is the private way to migrate if you prefer not to store codes in the cloud.
Do I need my old phone to transfer Google Authenticator?
For the offline QR method, yes. The export is generated on the old phone and scanned by the new one, so the old device has to work and display the QR code. This is why you should transfer before you wipe or return it. If the old phone is already lost or broken, the only app-based recovery is Google Authenticator’s optional cloud sync, and that works only if you had turned it on beforehand. Otherwise you recover each account through its own backup codes or account recovery.
Why do the codes on my new phone not work?
The most common reason is the phone’s clock. Authenticator codes are time-based, so if the new phone’s date and time are off, the codes it shows will be rejected as invalid even though they look normal. Go into the phone’s settings and set the date and time to update automatically over the network, then try again. If only some accounts fail, you may have missed one of several export QR codes, so re-run the export and scan every code it generates.
Does the offline export move all my accounts at once?
It moves the ones you select, and by default that is all of them, but they may be split across multiple QR codes. Google Authenticator packs roughly ten accounts into each export code, so a large collection produces a sequence of codes rather than one. Scan them in order until every account appears on the new phone. Only accounts stored inside Google Authenticator transfer this way; codes you keep in other apps, or accounts protected by text-message codes, are not part of the export.
Is it safe to keep both phones set up during the move?
Yes, and it is the recommended approach. Having the codes on both the old and new phone for a short window is exactly what lets you verify the new device before retiring the old one. Once you have logged into a couple of accounts with the new phone and confirmed it works, wipe the old phone or remove Google Authenticator from it. Leaving codes on a phone you are about to sell or recycle is the only risk, so make erasing the old device the final step, not the first.
What To Do Next
Set up Google Authenticator on the new phone, run the export from the old one, scan every QR code, and confirm a real login before you erase anything. If you are still choosing between apps, see our comparison of Google versus Microsoft Authenticator for moving 2FA without cloud backup, and read up on the ways authenticator backups quietly fail so you are not caught out. The technology section has more on keeping access to your accounts through a phone upgrade.