How to Transfer Google Authenticator to a New Phone
Changing phones can lock you out of important accounts if your two-factor codes are not moved correctly.
This guide explains how to transfer Google Authenticator to a new phone, what to do before switching, and how to avoid common recovery problems.
What Google Authenticator stores
Google Authenticator generates time-based one-time passwords, often called TOTP codes, for accounts that use two-factor authentication.
In many cases, the app stores these codes locally on the device unless cloud sync is enabled, which means a phone swap can interrupt access if you do not prepare first.
Because the app is tied to your account setup, not just the app itself, the safest transfer method depends on whether you are moving from Android to Android, iPhone to iPhone, or switching platforms.
Before you move: prepare your accounts
Before opening your new phone, check which accounts rely on Google Authenticator.
Email, banking, crypto exchanges, social media, and work systems may all use one-time codes.
- Confirm that you can still sign in to each account.
- Locate backup codes saved when two-factor authentication was enabled.
- Make sure your recovery email and phone number are current.
- Keep the old phone charged until the transfer is complete.
If an account offers alternative verification methods such as passkeys, SMS, security keys, or authenticator backup codes, keep those options available during migration.
How to transfer Google Authenticator to a new phone using sync
If you use a newer version of Google Authenticator with Google Account sync enabled, the process is simpler.
Your codes can be backed up to your Google Account and restored on a new device after you sign in with the same account.
Steps for sync-based transfer
- On the old phone, open Google Authenticator.
- Confirm that sync is enabled and that the app is connected to your Google Account.
- Install Google Authenticator on the new phone from the App Store or Google Play.
- Sign in with the same Google Account used on the old phone.
- Verify that your codes appear on the new device.
- Test one or two accounts before erasing the old phone.
This method is convenient, but you should still confirm that every important entry transferred correctly.
Not all organizations allow recovery through synced codes, and some enterprise systems use separate policies.
How to transfer Google Authenticator to a new phone with QR codes
If sync is not available or you prefer a manual transfer, Google Authenticator supports exporting accounts from the old phone and importing them on the new one using a QR code flow.
Steps for QR-based transfer
- Open Google Authenticator on the old phone.
- Look for the transfer or export accounts option in the app settings.
- Select the accounts you want to move.
- Generate the QR code shown by the old device.
- On the new phone, install and open Google Authenticator.
- Choose the import or transfer option and scan the QR code from the old phone.
- Check that every account appears in the new app.
This transfer method is useful because it does not depend on backup sync, but it requires both devices to be available at the same time.
Keep the old device secure during the process, since the QR code can expose your authentication seeds if someone else sees it.
How to move Google Authenticator from Android to iPhone or iPhone to Android
Cross-platform transfers are possible, but they usually require manual steps.
If you are switching between operating systems, you may need to use the export feature, scan the transfer QR code, or re-enroll each account individually.
For some services, you may need to log in to the account’s security settings and replace the old authenticator with the new one.
Common examples include Microsoft account, Amazon, PayPal, GitHub, and many banking portals.
- Use the old phone to export codes if the app supports it.
- Install Google Authenticator on the new device before removing the old device.
- Re-scan each service’s QR code if re-enrollment is required.
- Update any device-specific security settings tied to the old phone.
If a service does not let you migrate the code directly, treat the move as a fresh setup rather than a transfer.
What if you lost the old phone?
Losing the old phone makes the process harder, but not always impossible.
Start with any service that offers backup codes, account recovery prompts, or alternate verification methods.
Recovery steps to try
- Use saved backup codes for the account.
- Sign in from a trusted device or browser if one exists.
- Contact the service’s support team for identity verification.
- Use recovery email or phone-number options where available.
If Google Authenticator was synced to a Google Account, install the app on the new phone and sign in with that account first.
If sync was not enabled and no backup exists, you may need to complete account-specific recovery steps.
How to verify the transfer worked
Do not erase your old phone until you confirm that the codes on the new device work.
Open one account at a time and complete a login challenge to verify the new authenticator entries.
Pay special attention to high-risk accounts such as email, financial services, cloud storage, and password managers.
If a code fails, check whether the service uses time-based tokens, whether the device clock is correct, and whether the entry was fully migrated.
Common mistakes to avoid
Many people lose access because they rush the switch or assume the app itself contains the backup.
Avoid these frequent errors:
- Deleting Google Authenticator from the old phone before confirming the new one.
- Forgetting to save backup codes for each account.
- Skipping time and date settings, which can break TOTP code validation.
- Assuming every account will migrate automatically.
- Resetting the old phone too early.
Also remember that some accounts, especially enterprise or workplace systems, may require an administrator to re-register the authenticator.
Best practices for future phone upgrades
Once you complete the transfer, take a few minutes to make future moves easier.
A secure authentication setup is much easier to manage when you have more than one recovery path.
- Store backup codes in a password manager or another secure offline location.
- Enable Google Account sync if you want easier recovery across devices.
- Keep recovery email and phone details current.
- Review which accounts support passkeys or hardware security keys.
- Test critical logins a few times a year to confirm your backup methods still work.
If your organization supports FIDO2 security keys or passkeys through platforms such as Google Password Manager, Microsoft Authenticator alternatives, or device-native passkey systems, consider adding them as a stronger fallback than SMS alone.
When to contact support
If you cannot access an important account after the transfer, contact the service provider directly.
Be ready to provide proof of identity, recent login details, payment information, or administrative credentials if required.
Support teams can usually reset two-factor authentication, but they may need time to verify ownership.
The sooner you start the process, the faster you can regain access without risking account lockout.
By preparing first, choosing the right transfer method, and verifying each account carefully, you can move Google Authenticator to a new phone with minimal disruption.