Check your authenticator separately before erasing or trading in your old phone. A restored account name is not always a working sign-in method.

This guide covers Google Authenticator and Microsoft Authenticator. The first decision is which app stores your codes; the second is whether you still have the old device.

Choose the matching situation

SituationNext step
Google Authenticator with account syncUse the same Google Account on the new phone
Google Authenticator with local-only codesExport from the old device and import on the new one
Microsoft Authenticator, iPhone to iPhoneCheck backup, restore, then finish account verification
Microsoft Authenticator, Android to iPhoneRe-register accounts; the backup cannot cross platforms
Old phone unavailable, no usable backupUse each account provider’s recovery process

These routes come from Google’s transfer instructions and Microsoft’s restore guidance.

Google Authenticator: sync or export

If the old app saves codes to a Google Account, sign into that same account inside Authenticator on the new iPhone. Check the selected profile if entries are missing.

For codes kept without account sync:

  1. On the old device, open Authenticator’s menu.
  2. Choose Transfer accounts → Export accounts, unlock the device and select the entries.
  3. On the new phone, choose Transfer accounts → Import accounts.
  4. Scan the export QR code. There may be several.

Keep the QR codes private: they carry the information needed to reproduce those verification codes.

Do not delete synced entries from the old app to clean it up. Google says deletion also removes them from other synced devices.

Microsoft Authenticator: check the account type

Microsoft’s migration documentation calls for iCloud Drive, Keychain and backup to be enabled on iOS, including Authenticator under the apps saved to iCloud.

Restoring the app is followed by an account check:

Account typeWhat to expect
Third-party accounts using rotating codesSupported code entries can restore
Personal Microsoft account using only rotating codesCode entry can restore
Microsoft passwordless sign-inSign in again to finish setup
Work or school accountThe name restores; further sign-in/setup is required

For work access, open the restored entry and complete its prompts. If your organisation requires registration that you cannot perform yourself, use its help desk.

Passkeys need separate attention. A credential saved only on the old phone needs a replacement; a synced credential may be available through its credential manager. Test before removing the old method.

What if Microsoft restore does not appear?

Follow Microsoft’s restore page for your platform and app screen. iOS recovery depends on iCloud; use the same relevant accounts and complete any additional verification shown.

Microsoft limits backup restoration to the same device type. An Android backup is not an iPhone migration route. Keep Android available to authorise re-registration where possible.

Avoid repeatedly removing accounts just to make the screen look right. First establish which backup exists and which account it belongs to.

A useful test before you erase anything

Our suggested check is one real sign-in per important account, using the new phone when verification is requested. Keep an existing signed-in session available during the test.

Make a short list: main email, work account and any service you cannot easily recover. Mark each one only after its new-phone method succeeds. A familiar list of account names is not the test.

If the old phone is already gone and recovery fails, use the service’s backup codes, alternative verification or official account recovery. Restoring an unrelated phone backup is not evidence that a missing authenticator entry can be recovered.

For the rest of the move, see new-iPhone transfer options when iCloud is full.

Based on official Google and Microsoft documentation checked on September 14, 2026. Menu wording can vary by app version. No new-iPhone hardware testing is claimed.