How to move Google Authenticator to a new phone
Key takeaways
- If your codes were already synchronized, install Authenticator on the new phone and sign in with the same Google Account.
- For codes stored only on the old phone, use Transfer codes to export them and scan the QR code on the new phone.
- Treat the export QR code like a password because it carries authentication secrets, and never email or upload it anywhere.
- Test real sign ins on the new phone before retiring the old one, and remember that deleting a synced entry removes it from every device.
You can move Google Authenticator to a new phone by signing in to the Google Account that stores your synced codes, or by exporting codes from your old phone and scanning them on the new one. The right method depends on whether you enabled synchronization and still have your old device. This article explains both routes, recovery options, and the checks to make before retiring your old phone. (security.googleblog.com)
What is the easiest way to move Google Authenticator to a new phone?
Google Account synchronization is the easiest option if your Authenticator codes were already saved to your account. Install Google Authenticator on the new phone and sign in with that same Google Account. For codes stored only on your old device, use the app’s export and import feature instead. (security.googleblog.com)
Choose your route before changing anything:
- Codes already synchronized: Use account sign-in, then check your entries.
- Codes stored locally, old phone available: Export from the old phone and import on the new phone.
- Old phone unavailable, no synchronized codes: Start with an alternative sign-in method or the affected service’s recovery process. (support.google.com)
The goal is not simply to install the app. It is to confirm that you can complete a fresh sign-in without relying on the device you are replacing.
Prepare before switching phones
Set aside a quiet moment for the transfer rather than doing it at the trade-in counter. Keep your old phone charged and available, and write down which accounts you expect to see. Include less frequently used accounts so they do not get overlooked.
Before beginning, work through this checklist:
- Keep a trusted session open. Leave an existing browser session available while testing the new phone.
- Check your passwords. Make sure you can access the accounts you will test.
- Locate recovery methods. Identify backup codes, security keys, or another approved sign-in option.
- Delay the reset. Do not erase or surrender the old phone until testing is complete.
For your Google Account, you can create backup codes under Security & sign-in → 2-Step Verification → Backup codes. Store them somewhere secure and accessible independently of your phone. Each code works once; creating a replacement set invalidates the previous set. (support.google.com)
Move synchronized codes through your Google Account
Synchronization saves your Authenticator codes to your Google Account rather than leaving them only on one device. Google introduced this feature to reduce the risk of losing access when a phone is lost, stolen, or replaced. It supports Authenticator on both Android and iOS. (security.googleblog.com)
To use this route:
- Install Google Authenticator on your new phone.
- Open the app and sign in with the Google Account holding your saved codes.
- Check the account labels against your old phone or your account checklist.
- Test sign-in using a code from the new device. (support.google.com)
Pay attention to the account you choose, especially if you use separate personal and work Google Accounts. Signing in successfully is only the first checkpoint; take time to inspect the entries before moving on.
If signing in to Google itself requires the old phone’s Authenticator code, use that phone while it is still available. Otherwise, choose an alternative verification method you previously configured, such as a backup code or security key. (support.google.com)
Transfer locally stored codes with a QR code
Manual transfer moves the information used to generate verification codes between devices. You are not copying a single temporary number; you are transferring the underlying authentication secrets. Treat the export screen as sensitive account information. (security.googleblog.com)
Update Google Authenticator on the old phone before beginning. Google’s transfer instructions require the old device containing your codes and the new device. (support.google.com)
Export from your old phone
Open Google Authenticator on the old device and follow these steps:
- Open the menu and select Transfer codes or Transfer accounts.
- Choose Export codes or Export accounts.
- Unlock the device when prompted.
- Select the entries you want to move and continue to the QR-code screen. (support.bitkub.com)
Review your selection carefully instead of assuming every entry is included. Keep the old phone on that screen while you prepare the receiving device.
Import on your new phone
Install and open Google Authenticator on the new phone. If you want to keep using it without synchronization, choose the option to use Authenticator without an account. Then open the import workflow. (fsw.teamdynamix.com)
- Open Transfer codes/accounts → Import codes/accounts.
- Select Scan QR code.
- Scan the export code displayed on your old phone.
- Complete every scan if the export produces multiple QR codes, then check the transfer confirmation. (support.bitkub.com)
QR-code scanning—also called 二維碼掃描 in Traditional Chinese—is the camera step in this workflow. Use Authenticator’s import scanner, rather than trying to interpret the transfer code yourself.
Keep the export QR code private. Do not email it, share it in a support chat, or upload it to an online decoder. Because it carries authentication secrets, treat it more like a password than an ordinary image. (security.googleblog.com)
What if you no longer have your old phone?
If your codes were synchronized, sign in to the same Google Account in Authenticator on your replacement phone. If they were not synchronized and the old device is unavailable, you will need to recover access through each affected service rather than export from the missing phone. (support.google.com)
For your Google Account, available alternatives may include:
- An unused backup code.
- A registered security key.
- A passkey on another device.
- Another phone already signed in.
- A previously configured backup phone number. (support.google.com)
At Google’s sign-in screen, choose Try another way to look for available alternatives. To use a saved backup code, select the backup-code option and enter an unused code. If no alternative works, follow Google’s account recovery process. (support.google.com)
For other accounts, follow the provider’s recovery instructions. Make a separate recovery checklist for each service, recording what you have tried and which accounts still need attention. Avoid repeatedly changing settings across several accounts at once.
If the old phone was stolen, also sign it out of your Google Account and change your Google password. Regaining access and securing the missing device are separate tasks; do not stop after completing only one. (support.google.com)
Why are the transferred codes not working?
A rejected code can result from an expired number, the wrong account entry, or incorrect device time. Check those possibilities before assuming the transfer failed. Google Authenticator now uses the operating system’s time settings; its former time-correction setting is no longer available in version 7.0. (support.google.com)
Try these checks in order:
- Confirm the service and username. Similar labels can make the wrong entry easy to select.
- Use a fresh code. Wait for the displayed number to change before trying again.
- Check device time. Make sure the phone’s time and local time zone are correct.
- Check the signed-in Google Account. Missing entries may be saved under a different account. (support.google.com)
Change one thing at a time and retest. Keep notes if several accounts are affected, so you can distinguish a general phone issue from a problem with one particular entry.
Verify access before retiring the old phone
Use a fresh sign-in screen to test your new setup while keeping your existing trusted session open. Start with important accounts, then work through the rest of your checklist. Mark each account complete only after its new-phone code is accepted.
Be careful during cleanup: deleting a synchronized Authenticator entry also deletes it from other devices where it is synchronized. Do not remove individual synced entries merely to clear the old phone. (support.google.com)
Review the old phone under your Google Account’s device-management settings and sign out the sessions you no longer need. Google notes that a device can have multiple sessions, so inspect all entries associated with it. (support.google.com)
The practical takeaway is simple: choose synchronization or manual transfer, verify real sign-ins, and only then retire the old device. Treat successful access—not the appearance of codes—as your finish line.
Related guides
Sources
- Google Online Security Blog: Google Authenticator now supports Google Account synchronization
- Get verification codes with Google Authenticator - iPhone & iPad - Google Account Help
- support.google.com
- Fix common issues with 2-Step Verification - Google Account Help
- Google Online Security Blog: Introducing portability of Google Authenticator 2SV codes across Android devices
- Get verification codes with Google Authenticator - Android phone & tablet - Google Account Help
- Bitkub Support
- How To: Export Google Authenticator Security Codes on iOS and Android
- See devices with account access - Google Account Help