Move Google Authenticator to a new phone without losing access
Check whether Google Authenticator codes are synced or stored only on the old phone, then transfer and test access before erasing the device.
In brief
Do not wipe the old phone as soon as the new one displays the Authenticator icon. First determine whether your codes are synchronized with the intended Google Account or exist only on the old device. Those are different migration paths.
A new phone is ready when it can complete the sign-ins you need, not when the app has merely been installed. Testing while the old device is available keeps a simple move from becoming several separate recovery cases.
Identify the current storage mode
Open Authenticator on the old phone and check its profile/account state. Signing in on the new phone can synchronize codes associated with that Google Account. Codes used without an account need a manual transfer while the old device is still available.
Make an account checklist without writing down the secret codes: main email, school login, password manager and any other service you must retain. If an entry is missing, check the correct Google Account before creating a replacement or wiping anything.
Documentation for these steps: Google — Authenticator setup, sync and transfer ↗
Transfer privately, with both phones present
For a manual move, open Transfer codes → Export codes on the old phone and choose the required entries. On the new phone, use Transfer codes → Import codes and scan the displayed QR code. A larger set may produce more than one QR image.
Keep this screen away from other cameras and screen sharing. It is not a normal website QR code to decode for a tutorial. If a transfer image was exposed, review the affected services and replace their authenticator setup through their own security settings.
Documentation for these steps: Google — Authenticator setup, sync and transfer ↗
Test a real sign-in before declaring success
Use a separate trusted sign-in session to test the new phone’s code for each important service, while retaining a working recovery route. Match the account name carefully: similar labels for personal and school accounts are easy to confuse.
If a code is rejected, check the selected service, whether the code expired, and the phone’s date/time settings. Current Authenticator uses the operating system’s time; an old tutorial’s in-app time-correction menu may no longer exist. Follow the service’s verification help rather than repeatedly guessing.
Documentation for these steps: Google — Authenticator setup, sync and transfer ↗ · Google — Recover your account ↗
Retire the old phone without deleting the wrong thing
Confirm that you have usable backup codes or another accepted second factor for important accounts. Keep those separately from the phone. A screenshot of Authenticator is neither a reliable migration method nor a safe recovery archive.
When synchronization is in use, deleting entries on the old phone can also delete them elsewhere. Follow the device’s account-removal and secure-erasure process only after testing. If the old phone is missing, work through the affected services’ recovery options; a blank new installation cannot recreate local-only secrets.
Documentation for these steps: Google — Authenticator setup, sync and transfer ↗ · Google — Recover your account ↗
Before you act
The transfer QR code contains authentication secrets. Scan it only in the intended Authenticator import flow; do not email it, screenshot it for cloud storage or put it into a general QR reader. If the old phone is already lost and codes were not synced, use each service’s recovery process.
What to do next
- On the old phone, check the Authenticator account and whether the required entries are present.
- Use the same account for synced codes, or use Transfer codes → Export codes for a manual move.
- On the new phone, confirm the entries and test sign-in to each important service.
- Verify backup methods before erasing the old device; do not delete synced entries as a device-cleanup shortcut.
