How to Use Google Authenticator Transfer to Switch Phones Without Losing 2FA Codes

To use Google Authenticator transfer, sign into your Google Account so codes sync automatically, or manually export a QR code from your old device and scan it on the new one, according to Wikipedia. Which method applies depends on whether your codes are already saved to a Google Account.

How to Use Google Authenticator Transfer: Two Ways to Move Your Codes

There's no single "transfer" button — it splits into sync-based or manual. Most users are already on the sync path without realizing it, since signing in was the default during setup.

Method	Devices Needed	Works Without a Google Account
Automatic (sync)	New device only	No
Manual (QR export)	Both old and new device	Yes

Method 1 — Automatic Transfer by Signing In

How Automatic Sync Works

If codes are saved to your Google Account, signing in on a new device pulls them across automatically — no export, no scanning.

What You Need Before You Start

Your Google Account credentials, and a current app version: 6.0+ on Android, 4.0+ on iOS.

Steps to Sign In and Sync on a New Device

Install the app, sign in with the same account used previously. This usually completes within seconds; a short delay before all codes appear is normal.

Method 2 — Manual Transfer Using a QR Code

What You Need for Manual Transfer

This applies if you've used Authenticator without a Google Account. Both old and new devices need to be present and unlocked.

Step 1 — Prepare the New Device

Install Google Authenticator and tap "Get Started." Sign in here if future transfers should be automatic.

Step 2 — Export Accounts from the Old Device

Go to Menu, "Transfer accounts," then "Export accounts." Unlock the device, select accounts to move. Large batches may generate more than one QR code.

Step 3 — Scan and Import on the New Device

On the new device: "Scan QR code," then Menu, "Transfer accounts," "Import accounts," and scan while the code is still displayed.

Confirming the Transfer Worked

The app confirms once import finishes. Checking one code against a live login before deleting anything from the old device is a reasonable precaution.

Android vs iOS: What's Different in the Steps

Menu and Navigation Differences

The Menu, Transfer accounts, Export/Import flow is identical across platforms. Icon placement and menu triggers differ slightly.

Managing Codes After Transfer

On iPhone and iPad, editing means swiping left; deleting means swiping right. Android's gestures differ, and it's easy to follow iOS steps on Android by mistake — a mix-up support threads report fairly often.

Transferring Codes With Only One Device

Why the Standard Method Doesn't Work Here

Manual transfer assumes two phones — one displaying the code, one scanning it. Consolidating two accounts on one device breaks that assumption.

Using "Authenticator Without an Account" to Switch

The workaround uses "Use Authenticator without an account," then reassigning codes to a different account — a side effect of that mode, not a dedicated transfer feature.

What Happens to Existing Codes

This removes codes from every synced Google Account and keeps them only on that device. Worth understanding before starting, not after.

What Happens During and After a Transfer

Do Codes Stay on the Old Device?

Yes. Exporting copies codes; it doesn't remove them from the source.

Transferring Only Some Accounts

You choose which accounts to export — anything unselected stays put.

Multiple Accounts, Multiple QR Codes

Moving several accounts at once commonly produces more than one QR code, since each has a data limit.

Managing Multiple Google Accounts in Authenticator

Adding a Second Account

Tap your profile picture, then "Add another account." Teams managing shared logins often keep several accounts synced this way.

Switching Between Synced Accounts

Handled from the same profile menu — no re-transfer required.

If Your Old Device Is Lost or Unavailable

Manual transfer needs the old device to generate the export code, so loss or damage closes that path. If codes were already synced, signing in on a replacement device restores them without the original phone — a practical reason teams handling shared 2FA tend to favor sync.

Security Considerations During Transfer

How Codes Are Protected

Codes are encrypted in transit and at rest when synced, according to The Verge, though that doesn't remove the need for care during the transfer itself.

Risks of Screenshotting a QR Code

A screenshot of the export code is an unprotected copy of your account secrets, especially in a cloud photo backup — a shortcut most security-conscious users avoid.

Common Mistakes That Cause Transfer Problems

Outdated app versions often lack the transfer menu. Letting the QR code sit too long, or importing before exporting, are the two mistakes reported most.

Conclusion

Transferring Google Authenticator comes down to two paths: automatic sync through a signed-in account, or manual QR export when you're not. Knowing which applies to your setup avoids most confusion.

Frequently Asked Questions

Do I need both my old and new phone to transfer Google Authenticator?

Only for manual QR transfer. If codes are synced to a Google Account, signing in on the new device alone is enough.

What happens to my codes on the old device after transfer?

Nothing. Exporting copies codes to the new device; the old device keeps its copy until removed manually.

Can I transfer Google Authenticator codes without a Google Account?

Yes, through manual QR export and import, which requires both devices present at once.

Is it safe to screenshot the Google Authenticator QR code?

Not recommended. The code contains account secrets, so a screenshot is an unprotected copy of your credentials.

How to Use Google Authenticator Transfer With Only One Phone

Use "without an account" mode to reassign codes to a different account — this removes them from any previously synced accounts first.