How to Use Google Authenticator Transfer – Move Codes to New Phone

Upgrading to a new phone often brings one nagging question: how to move all those two‑factor authentication codes from the old device. Google Authenticator stores time‑based one‑time passwords locally, so without proper planning, a phone switch can lock you out of accounts. Fortunately, the app now offers several transfer methods, from QR code export to cloud sync.

Whether you are switching from Android to iPhone, moving within the same platform, or even migrating codes to Apple’s Passwords app, the process has become more flexible over the years. The key is knowing which method fits your situation — and what to do if the old phone is no longer available. This guide covers every official option and explains the security considerations behind each.

Before you begin, ensure both devices have the latest version of Google Authenticator installed. The steps differ slightly between platforms, but the core logic remains the same: export from the old phone, import on the new one.

How to Transfer Google Authenticator to a New Phone

Key insights

• Most users need to transfer Google Authenticator when upgrading phones, but often forget to export before wiping the old device.
• Google Authenticator does not support cloud sync by default, making the transfer process manual and potentially risky if the old phone is lost.
• Since iOS 18, Apple Passwords can import Google Authenticator codes, simplifying the move for iPhone users.
• Using Google’s built-in account sync (optional) allows recovery of codes without the old phone.
• The most common transfer mistake is not enabling export from the old device, leading to locked accounts.

How to Transfer Google Authenticator Codes to Another Account or Email

Moving codes to a different Google account

Google Authenticator does not natively let you move codes from one Google account to another. Instead, you must remove the old account from the app and add the new one. However, if you have enabled account sync, signing in with a different Google account on a new device will pull codes associated with that account — not the ones saved under a previous account.

To transfer codes between accounts, the most reliable method is to manually re‑add each service using the original QR code or secret key provided by the service when 2FA was first set up. Some services allow you to view or regenerate the secret key in their security settings.

Updating the email associated with your 2FA

Changing the email linked to your Google account does not automatically move your Authenticator codes. You will need to sign out of Google Authenticator and sign back in with the new email if you use account sync. Without sync, the codes remain on the device until you manually export them to another phone or delete them.

Can You Transfer Google Authenticator to Other Apps Like Apple Passwords or Microsoft Authenticator?

Exporting codes to Apple Passwords (iOS 18+)

With iOS 18, Apple introduced the ability to import 2FA codes into its Passwords app. The process involves exporting your codes from Google Authenticator as a QR code and then scanning that QR code into the Passwords app. Once imported, the codes sync across all Apple devices via iCloud. After a successful transfer, it is recommended to delete the codes from Google Authenticator to avoid duplicate entries.

Importing from Microsoft Authenticator to Google Authenticator

Moving from Microsoft Authenticator to Google Authenticator is manual. Open Microsoft Authenticator, go to the account settings, and look for the option to display the secret key or export a QR code. Some services allow you to view the TOTP secret directly. Then, in Google Authenticator, select the option to add a code manually or scan the QR code. If the secret key is not visible, you may need to disable 2FA on the service and re‑enable it using Google Authenticator.

How Secure is Google Authenticator for Transferring Codes?

Encryption during transfer

When using the manual export/import method, the QR code is generated locally on the old device and encrypted using your device’s PIN or biometrics. The code is not sent over the internet, which reduces the risk of interception. Google’s optional account sync transmits codes via encrypted channels, but it stores them in the cloud — a trade‑off between convenience and security.

What happens if you lose your phone?

If you lose your phone without having enabled account sync or generated backup codes, recovering access to your accounts becomes difficult. The official Google support thread indicates that without the old phone, the best course of action is to contact each service individually, verify your identity through alternative methods, and re‑enable 2FA on the new device. Backup codes, if generated beforehand, can be used to log in and reset the authenticator app.

Best practices for secure 2FA backup

For maximum security, keep a printed copy of backup codes in a safe place. Use a dedicated password manager that supports TOTP secrets as an additional layer, but be aware that storing codes online increases the attack surface. Google’s own Password Manager is separate from Authenticator and uses encryption, but it does not handle 2FA codes directly.

How Has Google Authenticator Transfer Evolved Over Time?

1. 2010: Google Authenticator launched for 2FA verification.
2. 2013: Support for multiple accounts and manual entry added.
3. 2019: Export/import feature introduced (3‑dot menu).
4. 2023: Google begins testing cloud sync option (optional).
5. 2024: iOS 18 allows transfer to Apple Passwords.
6. 2025: Current best practice: use export or sync before migrating.

What Is Known and What Remains Unclear About Transfer Methods?

Why Does Transferring Google Authenticator Require Careful Planning?

Transferring Google Authenticator codes is essential when upgrading devices, but the process requires planning. The primary method is to use the app’s export function to generate a QR code that the new phone scans. Without the old phone, users must rely on backup codes or enabling Google’s optional cloud sync beforehand. The rise of iOS 18’s Apple Passwords import and third‑party migration tools adds complexity but also convenience. Security remains a key concern: users should avoid sharing QR codes and keep backup codes offline.

Among the available resources, the official Google support article (Get verification codes with Google Authenticator) is the most authoritative. Lifewire’s guide (published December 2025) provides up‑to‑date screenshots, while community threads on Reddit and CloudHQ offer user perspectives but lack official verification. No single source covers all transfer scenarios comprehensively, and there is a notable gap in guidance for transferring to a new email or account.

What Do the Sources Say About Transferring Google Authenticator Codes?

“In the Authenticator app, tap Menu and then Transfer accounts and then Import accounts. Scan QR code created on the old device.”

— Google Support (support.google.com/accounts/answer/1066447)

“For anyone looking to transfer from one account to another: in the first account, you will have to click three horizontal lines on top‑left and …”

— Reddit user (r/google)

“To move your 2FA codes from an old phone to new one, you first need to connect your old phone’s Google Authenticator app to your Google account.”

— CloudHQ support article

What Should You Do Next to Keep Your 2FA Safe?

Moving forward, Google may transition to mandatory cloud sync, eliminating the manual export option. Apple Passwords integration could become bidirectional, and more authenticator apps will likely support standard TOTP URI import/export. For now, the safest approach is to generate backup codes, enable cloud sync if you trust the trade‑off, and always export codes before wiping an old device. For a deeper guide on setting up 2FA on Google accounts, see How to set up two‑factor authentication on Google accounts.

Frequently Asked Questions