Changing Phones? Sync Google Authenticator Before You Wipe the Old One

A person holding a mobile phone while preparing to move account verification codes.

Written by

in

A new phone is exciting; discovering that your two-step verification codes stayed behind is not. Google Authenticator can sync codes across devices when you sign in to your Google Account, but the safe move is to verify the destination before resetting or trading in the old phone.

Check how Authenticator is being used

Open Google Authenticator on the old phone and check whether you are signed in to the Google Account you intend to use for sync. Google’s current help says code synchronization requires a supported app version—version 6.0 or later on Android and 4.0 or later on iOS. If you deliberately use Authenticator without a Google Account, your codes are not being synced through that account.

Install the official Authenticator app on the new device and sign in to the same Google Account if sync is enabled. Give it time to load, then compare the list of services with the old phone. Do not assume that installing the app alone moves codes: codes set up separately by other services may require their own migration process.

Prove access before wiping

Choose one important account and verify that the new phone’s current code works at sign-in. Keep the old phone available until you have confirmed the important services and their recovery options. If an account uses a provider-specific transfer process, follow that provider’s official instructions rather than deleting the old entry prematurely.

When the move is complete, review the signed-in devices and remove access from the old phone as appropriate. Keep a separate recovery method for accounts that matter most. Google Authenticator sync reduces the risk of losing codes during a device change, but account recovery still depends on each service’s settings.

Featured image credit: Anders on Wikimedia Commons — Public domain.

Official references

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *