Skip to content
OTP Generator

Guide

How to Transfer Google Authenticator to a New Phone

Move Google Authenticator codes to a new phone with account sync or the export QR code, and learn how the otpauth-migration format can be decoded safely.

7 min readUpdated November 12, 2026Fact-checked against RFC 6238

Quick answer

Does Google Authenticator transfer codes automatically to a new phone?

Only if you were signed in to the app with a Google account and sync was turned on. In that case, signing in on the new phone restores your codes. Without sync, you must use the Transfer accounts export feature while you still have the old phone.

More answers
On this page

Before you wipe the old phone

The single most important rule: do not reset, trade in, or wipe your old phone until your codes work on the new one. Many people only discover their authenticator did not come along after the old device is gone, which turns a five-minute job into a long recovery process.

Google Authenticator gives you two ways to move your accounts: syncing through your Google account, and exporting them with QR codes. You can use either, or both.

Method 1: Google account sync

Newer versions of Google Authenticator can back up your codes to your Google account.

  1. On the old phone, open Google Authenticator and check the profile icon in the top corner. If you are signed in and sync is on, your codes are already backed up. A cloud icon or similar indicator usually confirms it.
  2. On the new phone, install Google Authenticator and sign in with the same Google account.
  3. Your accounts should appear after a moment.
  4. Test a code on one or two important services before relying on it.

Sync is convenient, but it means the security of your codes now depends on your Google account. Make sure that account has strong protection of its own, ideally a passkey or security key.

Method 2: export with QR codes

If you prefer not to use cloud sync, or want to move only some accounts, use the built-in transfer feature:

  1. On the old phone, open the menu and choose Transfer accounts, then Export accounts. You will need to confirm with your screen lock.
  2. Select the accounts to move. The app generates one or more QR codes; with many accounts it splits them across several codes.
  3. On the new phone, install Google Authenticator, choose to import or scan a QR code, and scan each code in turn.
  4. Check that codes on the new phone match the old one.
  5. Only when everything works, remove the accounts from the old phone.

This is a direct device-to-device transfer. Nothing is uploaded to Google in this method.

What is inside the export QR code

A normal 2FA setup QR code holds a single otpauth://totp/... link. The export QR code is different. It contains a link that starts with otpauth-migration://offline?data=, followed by a long string of encoded data.

That data is a Base64-encoded, compact binary structure (Protocol Buffers) that bundles several accounts together. For each account it stores the raw secret key, the account name, the issuer, the algorithm, the number of digits, and whether it is TOTP or HOTP. It is not encrypted, just encoded, so anyone who sees the export QR code can copy every account in it. Treat it like a sheet of passwords.

Decoding an export QR code

Because the format is not secret, the export can be decoded back into ordinary secret keys. This is useful if you want to:

  • Move accounts into a different authenticator app or password manager that cannot read Google's migration format.
  • Create an offline backup of your keys in an encrypted vault.
  • Check which accounts and settings you actually have.

Our Google Authenticator export decoder reads the migration QR code or link and lists each account with its Base32 key, all inside your browser. From there you can generate standard QR codes for each account with the 2FA QR code generator and scan them into any app, or verify keys with the TOTP generator.

Safety tips: do this on a device you trust, avoid taking screenshots of export codes, and clear any decoded keys from your screen and clipboard when you are done. Only decode exports of your own accounts.

Moving between iPhone and Android

Google Authenticator works the same way on both platforms, so switching from iPhone to Android or the other way round is no harder than a like-for-like upgrade. Both methods above work across platforms: sign in with the same Google account for sync, or scan the export QR codes from one phone with the other.

If you are also changing to a different authenticator app at the same time, export first, check whether the new app can import Google's migration format, and fall back to decoding the export into individual keys if it cannot.

Check your work before retiring the old phone

A transfer can look complete while hiding a problem, for example an account that was not selected for export or an entry that duplicated. Before you reset the old device:

  • Count the entries on both phones and make sure they match.
  • Sign in to your most important accounts, at least email, password manager, and banking, using codes from the new phone.
  • Look for non-standard accounts, such as ones using 8-digit codes or counter-based HOTP, and confirm they still work.
  • Tidy up labels while you are at it, so identical-looking entries are easy to tell apart.
  • Remember accounts outside Google Authenticator. If some codes lived in a different app, such as Microsoft Authenticator for work, move those too.

Only once everything checks out should you remove the accounts from the old phone and reset it.

If the old phone is already gone

If you did not have sync turned on and did not export your accounts, the codes cannot be moved; they existed only on that device. You will need backup codes, another registered factor, or each service's recovery process. Our lost phone recovery guide walks through the options.

Once you are set up again, turn on sync or keep an encrypted backup of your keys, and save fresh backup codes so the next phone switch is painless.

Frequently asked questions

Does Google Authenticator transfer codes automatically to a new phone?

Only if you were signed in to the app with a Google account and sync was turned on. In that case, signing in on the new phone restores your codes. Without sync, you must use the Transfer accounts export feature while you still have the old phone.

Is the Google Authenticator export QR code encrypted?

No. The otpauth-migration data is encoded with Base64 and Protocol Buffers but not encrypted. Anyone who scans or photographs it can obtain all the secret keys inside, so show it only to your own devices and never share it or store it as a plain image.

Can I import a Google Authenticator export into another app?

Some apps, such as several open-source authenticators, can read the migration format directly. If yours cannot, decode the export into individual secret keys and add each one manually or via a standard otpauth QR code generated from the key.

Need a code right now?

Paste your key and get the current 6-digit code in seconds. Free, private and nothing to install.