Ahom Cybersecurity logo Ahom CybersecurityPlain-language security for people and small teams
Passwords and Accounts

How to Move an Authenticator App to a New Phone Safely

A new phone arrives, you wipe the old one and trade it in, and the next morning your email asks for a six-digit code from an app that no longer exists. This is one of the most common ways people lock themselves out of their own accounts.

Two smartphones side by side on a desk, one displaying a QR code and the other scanning it with its camera, next to a printed sheet of backup codes

A new phone arrives, you wipe the old one and trade it in, and the next morning your email asks for a six-digit code from an app that no longer exists. This is one of the most common ways people lock themselves out of their own accounts. If you plan to move an authenticator app to a new phone, the order of steps matters more than the app you use.

This guide covers the safe sequence, how the main authenticator apps handle transfers, what to do for accounts that will not transfer, and what to do if you have already wiped the old device.

The golden rule before you move an authenticator app

Do not reset, sell or trade in the old phone until every account works on the new one. That single rule prevents almost every lockout I have seen in support tickets.

Authenticator apps generate codes from a secret key stored on the device. The code changes every 30 seconds, but the secret never does. When the old phone is wiped, the secret is gone unless it was backed up or exported first. The service you log in to cannot show it to you again, by design.

So the job is simple in principle: get each secret onto the new phone, test it, and only then retire the old one. Plan for 30 to 60 minutes if you have 15 to 25 accounts. Keep both phones charged and on Wi-Fi.

Before you start: a short checklist

  • Make a list of every account using the authenticator. Open the app and write down each entry: email, bank, cloud storage, work tools, social media, game accounts.
  • Find your backup codes for the most important accounts. If you never saved them, generate fresh ones now while you can still log in. Our guide on where to keep 2FA backup codes covers safe storage.
  • Check that you know the password for each account. Some transfers require a fresh login.
  • Update both phones to the latest operating system and app version.

How the main apps handle a transfer

Each authenticator app takes a slightly different approach. Here is how the most widely used ones work at the time of writing.

AppTransfer methodWatch out for
Google AuthenticatorSign in to sync codes to your Google account, or use Transfer accounts to export by QR codeCloud sync is optional; check it is on before relying on it
Microsoft AuthenticatorCloud backup via iCloud on iPhone or a Microsoft account on Android, then restore on the new phoneBackups do not move between iPhone and Android; some work accounts need re-registering
AuthyEncrypted cloud backup restored with your phone number and backup passwordForgotten backup password means the backup cannot be decrypted
Password managers with codesCodes sync with the vault automaticallyCodes and passwords in one place, which some prefer to avoid

Using a QR export

If your app offers an export QR code, install the same app on the new phone, choose import or scan, and point the new phone's camera at the old phone's screen. Do this in private. That QR code contains every secret it lists, and anyone who photographs it can generate your codes.

Using cloud backup

Cloud backup is convenient, but confirm that it actually ran. Open the app's settings on the old phone and look for a recent backup time. Then restore on the new phone and compare a handful of entries before going further.

Step by step: the safe order

  1. Install the authenticator app on the new phone and sign in or set up backup restore.
  2. Transfer accounts by export, cloud restore or manual re-enrolment.
  3. Test each account. Log out of a service on a browser, log back in, and use a code from the new phone. Tick it off your list.
  4. For any account that did not transfer, log in using the old phone, go to the security settings, remove the old authenticator, and add a new one by scanning the fresh QR code with the new phone.
  5. Once every account on your list works, delete the entries from the old phone's app.
  6. Only now wipe and reset the old phone.

Work accounts managed by an employer often need step 4, because the organisation ties the authenticator to a specific device. Your IT team may have a self-service page for this, or may need to reset it for you.

Why cloud sync is not a reason to stop caring

A popular take is that authenticator cloud sync has solved the new-phone problem, so you no longer need to think about it. That is half true, and the other half is where lockouts happen.

First, cloud sync moves your risk rather than removing it. If your Google, Microsoft or Apple account is the place your codes live, that account now protects everything else. It needs a strong unique password, its own second factor that does not depend on the same phone, and up-to-date recovery options.

Second, sync quietly fails. It may have been switched off during setup years ago, or a work policy may block it. People discover this only after the old phone is gone.

Third, not every service supports authenticator codes at all anymore. Many now prefer passkeys, which sync differently and need their own check. If you are moving to a new device anyway, it is a good moment to read about when passkeys can replace your passwords.

Sync is a good safety net. It is not a substitute for testing.

If you already wiped the old phone

Do not panic, and do not start guessing codes. Work through accounts in order of importance.

  • Use backup codes if you saved them. Log in, remove the old authenticator, and add the new phone.
  • Try other second factors on the account, such as a security key, SMS or a trusted device that is still signed in.
  • Use the official account recovery process. Expect identity checks and waiting periods of anything from a few hours to several days for large providers. That delay is a security feature, not a bug.
  • Be wary of anyone offering to recover accounts for a fee. These are almost always scams.

Once you are back in, set up two methods for each important account so a single lost phone never causes this again. Our plain-language explainer on two-factor authentication explains which combinations work well.

Frequently asked questions

Can I use the same authenticator app on two phones?

Yes, with apps that support cloud sync, or by scanning the same setup QR code on both phones when you first enrol an account. Codes will match on both devices. This is a useful backup, but keep the second phone secure, because it carries the same access.

What happens if I lose my phone with my authenticator app?

You will need backup codes, another second factor, or each service's account recovery process to get back in. If your authenticator synced to the cloud, sign in to the app on a new phone to restore codes. Then remove the lost phone from your accounts wherever possible.

Do authenticator codes transfer automatically to a new iPhone?

Not always. Restoring an iPhone backup may not include authenticator secrets, depending on the app. Check the app's own backup or sync settings before switching, and test several accounts on the new phone before wiping the old one.

CV
Corin Vasquez

Corin has spent years helping non-technical people understand security, and writes to make defense feel doable rather than frightening.

More posts by Corin

More in Passwords and Accounts

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto