Switching phones without moving your two-factor codes over is how people get locked out of their own accounts. It happens more often than you'd think.
If you're wondering how to use Google Authenticator transfer, there are two ways to do it: sign in to a Google Account inside the app so codes sync automatically, or manually export and import them using a QR code between two devices.
Which one applies to you depends on whether your codes are already linked to a Google Account.
What "Transfer" Actually Means: How to Use Google Authenticator Transfer
The word "transfer" gets used loosely, but it covers two genuinely different processes. One is automatic codes tied to a signed-in Google Account move with you whenever you sign in on a new device.
The other is manual a one-time QR export and import between two physical devices, used when you're not syncing to an account at all.
According to Wikipedia, Authenticator generates these codes using the same time-based one-time password standard that underlies most authenticator apps, which is part of why the transfer process looks similar across competing apps too.
Most people assume it's one feature. In practice, it's a fork in the road, and picking the wrong path is usually where confusion starts.
Also Read:Blippi Net Worth
How to Transfer Codes Using Google Account Sync
If your codes are saved to a Google Account, this is the easier route, and it doesn't require holding two phones at once.
As reported by TechCrunch, this account-sync option was added to remove the old single-device limitation, where losing a phone meant losing every code stored on it.
Requirements:
- Android 6.0 or above, or iOS 4.0 or above
- An active Google Account signed into the app
Checking if sync is on: open Authenticator and look at your profile icon in the top right. A cloud with a green checkmark means you're synced. A gray cloud with a slash through it means you're not codes are living only on that device.
To sync on a new device, install Authenticator, sign in with the same Google Account, and your existing codes appear automatically. No QR code needed.
Teams that manage 2FA across multiple accounts commonly report that sync is the more reliable method for reducing lockout risk, simply because it removes the single-point-of-failure problem of one physical device.
One thing worth clarifying: syncing doesn't delete anything from the old device. Codes stay put there too, until you manually remove them or stop syncing.
Also Read:IDM Mean
How to Manually Transfer Codes (Export and Import)
This is the method for accounts not linked to Google sync — or for anyone who'd rather keep codes off the cloud entirely.
Requirements:
- Both the old and new device, physically in hand
- Same operating system on both (Android to Android, or iOS to iOS)
- Latest version of the Authenticator app on both
On Android:
- Install Authenticator on the new device and tap Get Started
- Choose Scan a QR code
- On the old device, open Authenticator, tap the menu icon, then Transfer accounts, then Export accounts
- Confirm your identity if prompted
- Deselect any accounts you don't want moved, then tap Next
- A QR code appears — scan it with the new device
On iOS: the sequence is nearly identical, though the menu icon sits in a slightly different spot depending on app version. Export accounts, generate the QR code, scan it on the new phone.
In practice, this usually finishes in under a minute per account.
Larger batches of accounts sometimes split into multiple QR codes, which is easy to miss if you're moving quickly.
Same as with syncing, exporting doesn't remove accounts from the old device automatically. You'd need to delete them there separately if that's the goal.
Can You Transfer Between Android and iOS?
This is where most guides go quiet, and it's a fair question if you're switching platforms rather than replacing a same-brand phone.
Manual QR export and import is platform-locked it's built to move codes within the same OS, not across. Account sync is the more realistic path for a cross-platform move, since it isn't tied to device type at all, only to being signed into the same Google Account.
That said, this is general understanding rather than a documented guarantee for every edge case, so treat it as the likely route, not a certainty for every single app you've set up 2FA on.
Also Read:Snapchat Story Downloader
Transferring Without Your Old Device
Lost phone, broken screen, stolen device none of that has to mean starting every 2FA setup from scratch.
Backup codes. When you first set up 2-Step Verification, Google generates ten single-use codes. Each works once. If you're through all ten, new ones can be generated from your account's Security settings. These exist specifically for this scenario.
A saved QR screenshot. If you screenshotted the barcode during initial setup, that image can be re-scanned on a new device to restore the account.
Worth noting: a screenshot sitting unprotected in your camera roll is itself a security gap. If you keep one, it deserves the same protection as a password.
Also Read:Alex Hormozi Net Worth
Security Considerations During Transfer
Codes synced through a Google Account are encrypted both in transit and at rest that's documented, not assumed.
What's less discussed is the handling on your end. Screenshots, printed backup codes, exported files anything living outside the app is only as safe as wherever you're storing it.
Most of the risk in this process isn't the transfer mechanism itself. It's what happens to the paper trail afterward.
Troubleshooting Common Transfer Issues
|
Issue |
Likely Cause |
What to Try |
|
QR code won't scan |
Poor lighting, camera angle, or an expired code |
Regenerate the export QR code and rescan in better lighting |
|
Accounts missing after transfer |
Deselected during export, or app version mismatch |
Check the export selection step again; update both apps to the latest version |
|
Sign-in delayed after enabling Authenticator |
Google applies a security hold on new verification methods |
This can take up to 7 days; a trusted passkey or security key on the account may shorten it |
|
Codes not appearing on new device after sync |
Not signed into the same Google Account, or sync toggled off |
Confirm the cloud icon shows a green checkmark, not a gray slash |
Conclusion
Google Authenticator transfer works one of two ways: automatic sync through a signed-in Google Account, or manual QR export between two same-platform devices.
Knowing which applies to your setup avoids most of the confusion people run into mid-switch.
FAQ
Does transferring remove codes from my old device?
No. Both syncing and manual export leave codes on the original device. They stay there until removed separately.
Can I transfer Google Authenticator codes from Android to iPhone?
Manual QR transfer is limited to the same platform. Account sync is the more realistic option for moving across Android and iOS.
What if I lost my old phone and have no backup codes?
Check for a saved QR screenshot from setup. Without either backup codes or a screenshot, recovery generally requires contacting the service tied to that account directly.
Is Google Authenticator sync secure?
Codes synced to a Google Account are encrypted in transit and at rest. Screenshots and printed codes outside the app aren't covered by that protection.
How long is a transfer QR code valid?
This isn't publicly specified with an exact time limit. If a code fails to scan, regenerating it via Export accounts is the standard fix.
