Replacing a phone can disrupt two-factor authentication if your authenticator app is not moved correctly.
This guide explains how to move Google Authenticator to new phone, what to do before switching, and how to recover access if anything goes wrong.
What Google Authenticator actually stores
Google Authenticator generates time-based one-time passwords, or TOTP codes, for accounts that use two-factor authentication.
The app stores secret keys locally on your device, which is why changing phones requires a transfer or re-enrollment process.
Because the codes are tied to the secret keys, simply installing the app on a new device is not enough.
You must move the account entries or reconfigure each protected account with a new QR code or setup key.
Before you switch phones
Preparation reduces the risk of lockout.
Before you begin, make sure you can still access the old phone, at least long enough to transfer the codes or update each account.
- Keep the old phone charged and unlocked.
- Verify you know your passwords for important accounts.
- Have backup codes saved for critical services such as Google, Microsoft, GitHub, or banking apps.
- Confirm your new phone can receive SMS, email, or push notifications for recovery steps.
If you use authenticator codes for work accounts, crypto wallets, or password managers, coordinate with those services in advance.
Some platforms require manual re-enrollment instead of app transfer.
How to move Google Authenticator to new phone
The Google Authenticator app includes a transfer feature that lets you move accounts from one Android or iPhone to another.
The process depends on whether you are moving to the same platform or switching between Android and iOS.
Transfer accounts using the built-in export feature
On the old phone, open Google Authenticator, tap the menu or settings icon, and look for a transfer or export accounts option.
The app will usually prompt you to select the accounts you want to move and display a QR code.
On the new phone, install Google Authenticator, open the app, and choose the import or scan QR code option.
Scan the code shown on the old phone to complete the transfer.
Once imported, the new device should generate the same rotating codes as the old one.
After the transfer, check a few accounts immediately.
Log in to services such as your Google Account, Amazon, Dropbox, or other protected platforms to confirm the six-digit codes work.
Use QR codes or setup keys when transfer is not available
Some accounts may not support a direct app transfer, especially if they were added manually or if the old phone is unavailable.
In that case, sign in to each service and re-enable two-factor authentication.
Most services will provide one of the following:
- A QR code to scan with the new phone.
- A manual setup key to enter into the authenticator app.
- Recovery codes to regain access before generating a new authenticator secret.
This method takes longer, but it is often the most reliable way to ensure the new device is correctly linked to each account.
What to do if you still have the old phone
If the old phone works, treat it as your safest recovery tool.
Use it to verify every account before wiping, selling, or trading in the device.
- Open each important account and confirm the authenticator entry is active.
- Review whether the account has backup codes available.
- Disable and re-enable two-factor authentication only if required by the service.
- Keep the old phone for a few days in case a transfer problem appears.
Do not factory reset the old device until you have tested logins from the new phone.
If one account fails, the old phone may still be your fastest way back in.
What if you lost the old phone?
When the old phone is gone, the recovery path changes.
You cannot extract Google Authenticator codes from the lost device, so you must use account-level recovery options.
Start with the most important services first and look for backup codes, recovery email, recovery phone number, or support-assisted verification.
If you still have access through a logged-in browser session, change the two-factor method from within the account security settings.
For services that do not offer backup codes, you may need to contact support and prove your identity.
This is common with banks, enterprise tools, and some cryptocurrency exchanges.
How to verify that the transfer worked
After moving Google Authenticator to a new phone, test the accounts that matter most.
Open the protected service, sign out if necessary, and sign back in using the code from the new device.
Watch for common warning signs:
- The code is accepted on one device but not the other.
- The app shows an account, but the numbers do not match expected logins.
- A service says the code is invalid even though the time appears correct.
If codes fail, check the phone’s automatic time settings.
Authenticator apps rely on accurate time, and even a small clock drift can cause verification errors.
Security tips after moving your authenticator
Once the transfer is complete, take a few security steps to reduce future risk.
A phone upgrade is a good moment to strengthen account recovery and reduce dependence on a single device.
- Store backup codes in a password manager or secure offline location.
- Review recovery email addresses and phone numbers for accuracy.
- Enable biometric or passcode protection on the authenticator app if available.
- Consider a second authenticator device for critical business accounts.
If you manage sensitive logins, remember that Google Authenticator does not sync every account in a way that guarantees easy recovery across all devices.
A secure backup plan matters as much as the transfer itself.
Common mistakes to avoid
Most transfer problems happen because users rush the process.
Avoid these mistakes when changing phones:
- Factory resetting the old phone before confirming the new one works.
- Assuming every account moved automatically with the app.
- Forgetting to update authenticator entries for work, banking, or crypto platforms.
- Ignoring backup codes until after access is lost.
- Relying on screenshots of QR codes, which can create security risks.
Careful verification is more important than speed.
A few extra minutes spent checking each account can prevent hours of account recovery later.
When to contact support
Contact support if you cannot access backup codes, lost both phones, or receive invalid-code errors after a verified transfer.
Support teams can often reset two-factor authentication after identity verification, though the process varies by service.
For enterprise environments, your IT administrator may need to remove and re-enroll the authenticator on your behalf.
Keep in mind that security policies can differ across Google Workspace, Microsoft 365, Okta, Duo Security, and other identity platforms.
Quick checklist for moving Google Authenticator
- Keep the old phone until new logins are tested.
- Use the app’s transfer feature when available.
- Re-enroll accounts that do not transfer automatically.
- Save backup codes before making changes.
- Verify time settings on the new device.
- Test access to critical accounts immediately.
Following these steps makes how to move Google Authenticator to new phone far less stressful, especially when your most important accounts depend on it.