Newsletter Subscribe
Enter your email address below and subscribe to our newsletter
Switching phones and worried about losing access to your accounts? Here's how to use Google Authenticator transfer: sign into your Google Account to sync codes automatically, or manually scan a QR code between old and new devices.
Which method applies depends on whether your codes are already linked to a Google Account.
There isn't just one path here, and that trips people up more than it should. Google Authenticator generates time-based one-time passwords for two-factor authentication, according to Wikipedia, and moving those codes to a new phone comes down to two distinct methods that behave differently depending on your setup.
If your Authenticator app is already signed into a Google Account, this is the easier route. Install Authenticator on the new phone, sign in with the same Google Account, and your codes appear automatically. No QR scanning, no old device required at that moment.
If you're using Authenticator without a Google Account meaning your codes live only on the device itself you'll need both phones in hand.
The old phone generates a QR code, and the new phone scans it. This is the method most people picture when they think of "transferring" Authenticator, and it's also where most confusion happens.
Before doing anything else, it's worth confirming which situation you're actually in.
Open the app and look at the top right corner. A cloud icon with a checkmark next to your profile picture means your codes are synced to a Google Account.
A crossed-out or gray cloud icon means they're not, and you'll need the manual method instead. This one detail saves a lot of unnecessary QR scanning.
Manual transfer follows roughly the same logic on both major platforms, though the menu wording differs slightly.
Here's something competitors rarely spell out clearly: the export/import process isn't platform-locked.
A QR code exported from an Android device can be scanned by an iPhone running Authenticator, and vice versa, because both versions of the app read the same QR format. The steps are functionally identical export on the old OS, scan with the new one.
Just make sure both apps are updated to their latest version before starting. Older app versions occasionally use a slightly different export format, and mismatched versions are a common, avoidable reason a scan fails.
This is one of the more common points of confusion, and understandably so.
Manual export and import copies the codes to the new device. It does not remove them from the old one. Your old phone keeps working with those same codes until you manually delete them or reset the device.
Sync behaves differently once you're signed into a Google Account on a new device, that account becomes the active source, and disconnecting sync on one device can affect what's stored centrally.
Before this sync option existed, as reported by TechCrunch, codes were stored only on the single device that generated them, so losing that device without a backup meant losing access outright.
In practice, most people don't notice this distinction until they're troubleshooting a "why do I have two working codes" situation.
Not everyone has both phones in hand. Lost, broken, or stolen devices are a real and common reason people search for this exact process.
If you generated backup codes when you first set up 2-Step Verification, they still work here. Go to your Google Account's 2-Step Verification settings, find the backup codes section, and use one to sign in and re-establish authentication on the new device. Each code works once.
If you saved a screenshot of the original QR code, or wrote down the setup key when you first configured an account, you can use either to re-add that account manually on the new device through the app's "add account" option.
This is the scenario nobody wants, and it's also the one with the least clean answer. Without a synced Google Account, backup codes, or a saved QR code, the account-specific 2FA codes generally can't be recovered through Authenticator itself.
At that point, recovery depends entirely on the account and service in question — most platforms have their own account recovery process for exactly this situation, separate from Authenticator.
Also Read: dreamwithjeff.com hack
Both methods work. Which one fits depends less on preference and more on what you already have set up.
|
Factor |
Sync (Google Account) |
Manual (QR Export/Import) |
|
Requires old device present |
No |
Yes |
|
Requires Google Account sign-in |
Yes |
No |
|
Codes removed from old device |
No, remains linked centrally |
No, stays on old device |
|
Works across platforms (Android/iOS) |
Yes |
Yes |
|
Best for |
Ongoing, low-effort backup |
One-time device switch |
If you're likely to switch devices again, or you just don't want to think about this process a second time, syncing to a Google Account is the lower-maintenance choice.
If you're intentionally avoiding linking codes to a Google Account, for privacy or account-separation reasons, manual transfer is the only route and it's a fine one, as long as you still have your old phone.
Most transfer issues come down to a handful of repeat causes.
Screen brightness, glare, and camera distance cause more failed scans than people expect. Increase brightness on the phone showing the QR code, and hold the scanning phone steady about six to eight inches away.
Also Read: error susbluezilla new version
Before generating an export QR code, Authenticator asks you to confirm it's really you typically through your phone's existing lock method, whether that's a fingerprint, face scan, or PIN.
It's a safeguard against someone else exporting your codes if they briefly get hold of your unlocked phone.
Also Read: feedbuzzard advertising
If an account doesn't show up after import, double-check it wasn't accidentally deselected during the export step. It's an easy checkbox to miss when transferring several accounts at once.
Authenticator can hold codes for more than one Google Account on the same device. Tap your profile picture, choose Add another account, sign in to the additional account, and allow it to start saving codes.
Each account's codes stay associated with that account specifically, which matters if you ever need to sync or transfer just one of them later.
Also Read: iamrestaurant.com
Google Authenticator transfer comes down to two paths: automatic sync through a Google Account, or manual QR export between two physical devices.
Which one you need depends on whether your codes are already linked to an account and whether your old phone is still accessible.
No. Manual export and import copies codes to the new device without removing them from the old one. You'd need to delete them manually or reset the old phone separately.
Yes. The QR export/import process works across platforms as long as both apps are updated to their current versions.
Use backup codes generated during initial 2FA setup, or a saved QR screenshot/setup key. Without either, recovery depends on each individual account's own process.
Manual QR transfer doesn't require internet access. Syncing through a Google Account does, since it needs to connect to your account.
Manually transferred codes work immediately after scanning. Synced codes also appear right away once you're signed into the same Google Account.