To move an authenticator app to a new phone without losing account access, prepare recovery options first, follow the app’s official transfer or restore process, and test each important account on the new device before removing anything from the old one. If you are also moving data to a new Android phone, treat authenticator access as a separate check: a general phone backup does not confirm that every authentication method has transferred.
Key Takeaways
- Keep the old phone charged, available and unchanged until you have tested sign-in on the new phone.
- Authenticator transfer depends on the app and account type; a restored account name does not always mean its codes or sign-in credentials have been restored.
- Save recovery codes and confirm an alternative sign-in method before starting, especially for work, school, banking and email accounts.
- Verify accounts one by one on the new device, then remove the old device through each service’s account-security settings when appropriate.
What should you do before moving an authenticator app?
Before transferring an authenticator app, make a short account inventory, confirm your recovery options and keep both phones accessible. The key distinction is between moving the app and confirming that every website or service recognises the new device as a valid sign-in method.
Start by listing the accounts in the authenticator app. Note whether each entry uses a rotating one-time code, push approval, a work or school sign-in, or another credential. These methods can have different transfer and re-enrolment requirements. An authenticator app’s backup may restore some entries but not necessarily every credential or approval method.
- Keep the old phone operational. Charge it, keep its screen lock available, and do not erase or trade it in yet.
- Check recovery access. Confirm that you can use the account’s recovery email, secondary phone number, backup codes, passkey or security key where available.
- Review work and school accounts. Find out whether your organisation requires IT approval or a fresh device registration.
- Identify each authenticator app. Record the app name and the accounts it contains; do not assume different apps use the same transfer method.
- Use a trusted connection and private setting. Avoid exposing QR transfer codes or recovery codes to other people or cameras.
Recovery codes are a contingency, not a replacement for testing the new setup. Store them somewhere separate from the phone being replaced, and follow each service’s instructions for generating or replacing them.
How do you transfer Google Authenticator to a new phone?
Google Authenticator can move codes by syncing them through a Google Account or by exporting and importing them with a QR code. Which route applies depends on whether code syncing is enabled and how the app is set up on the old phone.
Option 1: Sync with your Google Account
On the new device, install Google Authenticator and sign in to the Google Account used to sync the codes. Google says codes are automatically synced to the new device when you sign in to that account in the app. If you have more than one Google Account, confirm that you are using the one associated with the saved codes.
If the codes do not appear, check the profile shown in the app and whether the old phone was using Authenticator without a Google Account. Google notes that codes kept only on the device are not available on other devices through account sync.
Option 2: Transfer codes using a QR code
If you use Google Authenticator without a Google Account, you can manually export codes from the old phone and import them on the new one. The current Google instructions use the app’s Transfer codes option: export the selected accounts on the old phone, then scan the QR code using the import option on the new phone. The app may create more than one QR code when transferring multiple accounts.
Keep the QR code private. It contains information needed to recreate the codes, so do not send it in a message, post it, or save it in a shared photo library. After import, compare the account list and test the relevant sign-ins while the old device remains available. Follow Google’s current Google Authenticator transfer instructions if menu names or steps differ on your app version.
How do you move Microsoft Authenticator to a new phone?
Microsoft Authenticator’s backup and restore options vary by platform and account type. Microsoft’s current guidance says an iOS backup cannot be restored to Android, or an Android backup to iOS; work or school accounts may require sign-in and registration again rather than restoring a complete credential.
Before switching phones
On the old phone, open Microsoft Authenticator and check its backup settings. On Android, Microsoft currently documents enabling Cloud Backup in the app’s settings and selecting a Microsoft personal account for the backup. On iOS, its instructions require the relevant iCloud settings and Authenticator backup to be enabled. The exact flow may change, so use the instructions for your current app and operating system.
After installing the app on the new phone
Use the app’s recovery or restore flow and sign in with the account used for the backup. Then inspect each entry rather than assuming that the list represents fully restored access. Microsoft says that work or school entries may restore only the account name; you may need to sign in again and register the new device. Some passwordless credentials also require signing in again after restore.
For an organisation-managed account, ask your IT administrator how to register the new phone before removing the old one. Microsoft’s Authenticator backup and restore guidance explains the current platform and account limitations.
How do you verify every account on the new phone?
Verify each service individually by completing a sign-in or approved re-registration on the new phone, then confirm that its recovery options still work. Seeing an account name or a changing code in the app is useful, but it does not prove that the service has accepted the new device.
- Start with essential accounts. Test primary email, password manager, financial services and work or school access first.
- Use the service’s normal sign-in page. Enter the current code or approve the prompt on the new device. Avoid repeatedly requesting codes if one fails; check the service’s instructions first.
- Complete device registration where required. Some services ask you to confirm the new phone, scan a fresh QR code or contact an administrator.
- Check recovery methods. Confirm that backup codes, a secondary method or account recovery details are current and accessible.
- Remove the old device only after success. Use each service’s security settings to revoke or remove the previous phone if it is no longer needed.
If you cannot sign in, do not delete the old authenticator entry or reset the old phone in an attempt to fix it. Use the service’s official recovery process or contact its support team. For Google Accounts, available alternatives can include another signed-in device, a backup code, a passkey or a security key, depending on the account setup. See Google’s 2-Step Verification recovery options.
What should you do with the old phone?
Keep the old phone intact until the new phone has passed the account checks that matter to you. Once you have verified access and completed any required device re-registration, remove the old phone from individual account settings as appropriate, then prepare it for trade-in, service or recycling.
Before erasing it, check that you are not relying on an authenticator entry, recovery code or approval prompt that exists only on the old device. A general device backup, app reinstall or SIM transfer should not be treated as proof that authenticator credentials have moved.
VERTU Tip: Make authenticator migration part of new-phone setup
If your next phone is a VERTU smartphone, include authenticator migration in the device handover checklist alongside contacts, photos and essential files. The transfer method is determined by the authenticator app and the account provider—not by the phone brand alone. Move each account using its official method, test access on the new phone, and retain the old device until those checks are complete.
This is a practical setup recommendation, not a claim that VERTU phones automatically transfer authenticator credentials or provide app-specific compatibility. For broader phone data and account-protection habits, keep the same disciplined approach: verify recovery access before a device is wiped or handed over.
Frequently Asked Questions
Can I move an authenticator app without the old phone?
Sometimes, but not always. Recovery depends on whether the app has a usable backup and whether each service allows another sign-in or re-registration method. If the old phone is unavailable, use the service’s official account recovery process rather than assuming an app reinstall will restore credentials.
Does a phone backup automatically transfer authenticator codes?
No, not reliably. Authenticator apps and individual services may use separate backup, sync or device-registration processes. Check the app’s official instructions and test each important account on the new phone before erasing the old one.
Can I transfer Microsoft Authenticator from iPhone to Android?
Not by restoring the same Microsoft Authenticator backup across those platforms. Microsoft’s current guidance says backups can only be restored to the same device type. You may need to register accounts again, particularly work or school accounts.
Should I delete the authenticator app from my old phone after transfer?
Only after you have verified access on the new phone. Test important accounts and complete any required re-registration first. Then remove the old device through the relevant services’ security settings before wiping it.
What if my authenticator codes appear but do not work?
Check the account entry, the device time and the service’s setup status before deleting anything. Make sure the code is for the correct account, and confirm that the service has enrolled the new authenticator. If it still fails, use that service’s recovery or support process while keeping the old phone available.
Conclusion
Moving an authenticator app is complete only when the important accounts work on the new phone and recovery options remain available. Prepare first, use the official transfer or restore steps for each app, re-register work accounts where required, and keep the old phone until testing is done. For more practical VERTU phone setup and ownership guides, visit VERTU Guides.
