Authenticator app not backing up on old phone to transfer to new one

Follow these steps to get Authenticator working on the new Android phone and stop notifications going to the old one.

1. Fix the backup error on the old phone (optional but recommended) The “Something went wrong” backup error usually means the recovery account isn’t signed in correctly.
   • Open Microsoft Authenticator on the old phone.
   • Go to ⋮ > Settings > Backup.
   • Make sure Cloud Backup is turned on and that a personal Microsoft account is signed in as the recovery account.
   • If you still see “Something went wrong,” turn Cloud Backup off and back on, then choose Continue or Change account and sign in again to create a fresh backup.
   If backup still fails, you can continue with manual re‑add of accounts (which you already started) and focus on redirecting notifications.
2. Make sure notifications don’t go to the old device Adding Authenticator on the new phone does not automatically unregister the old one. Microsoft or the organization must be told to forget the old device. For personal Microsoft accounts:
   1. Go to the two-step verification area of your Account Security page.
   2. Turn off verification for the old device / remove the old Authenticator registration.
   For work or school accounts:
   1. Go to the two-step verification area of your My Apps page or your organization’s company portal.
   2. Turn off verification for the old device / remove the old Authenticator registration.
   After this, new push notifications will no longer be sent to the old phone.
3. Re‑register Authenticator on the new phone for each account For each work/school or personal Microsoft account that should send notifications to the new phone:
   • On a computer, sign in to the account’s security/MFA page (for example, Security info, Additional security verification, or your school/work My Apps page).
   • Remove any old Authenticator app registrations if they are still listed.
   • Choose Add sign-in method (or similar), select Authenticator app, and follow the prompts to show a QR code.
   • On the new phone, open Authenticator, choose Add account, pick the correct account type, and scan the QR code.
   • Approve a test notification or code to complete registration.
   If push notifications still don’t arrive on the new phone:
   • On the new phone, open Authenticator → Settings.
   • Turn on App updates, Cloud Backup, and disable battery optimization for Authenticator.
   • In Settings > Notification Settings, ensure Show notifications is turned on.
   • Make sure the device’s Date & time are correct and try switching between Wi‑Fi and mobile data.
4. If notifications go to the wrong device during registration If a push is still going to the old phone when registering a credential:
   • Either approve it on the old phone once, then immediately remove the old device as described in step 2, or
   • Choose a different verification method (SMS, call, or code) during sign‑in if available, then complete the new registration on the new phone.
5. Special notes for school and work accounts
   • Whether push notifications are allowed is controlled by the organization. If notifications don’t work but codes do, the admin may have disabled one‑click notifications.
   • If locked out of a school or work account and no alternative method works, contact the organization’s IT/helpdesk and ask them to reset MFA for the account in the Microsoft Entra admin center so Authenticator can be set up again on the new phone.

Once the old device is removed from all security/MFA pages and each account is re‑registered on the new phone, notifications will be sent only to the new phone.

References:

• Back up account credentials in Microsoft Authenticator
• Microsoft Authenticator FAQs
• Troubleshoot problems with Microsoft Authenticator
• Migrate to a new iPhone for work