This guide addresses a recurring failure reported in user forums: deleting the old app before confirming the new token. The safe method is staged and verifiable. It begins with an inventory, protects the last working path, follows current official documentation, and tests the result before cleanup.
Quick scan
In brief
List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token.
Test a fresh sign-in in a private browser before removing the old registration.
Photograph nothing that exposes the QR seed or recovery code to cloud galleries.
1. List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token
List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token. This action advances the goal to move every MFA-protected account to the new phone while preserving at least one independent recovery path. It also addresses the concrete failure mode “deleting the old app before confirming the new token.” Capture the starting state and keep the last working device, session, or copy available until the new path has passed an independent test.
For “1. List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token,” verify the result from a fresh session or second device. Note the exact screen, version, owner, and time without copying secrets. If the result cannot be repeated, return to the preserved state rather than stacking another irreversible change on top.
2. Generate or verify backup codes and store them separately from both phones
The next move is specific: Generate or verify backup codes and store them separately from both phones. Do it before any reset, deletion, migration, or firmware change connected with move every MFA-protected account to the new phone while preserving at least one independent recovery path. The mistake to prevent is discovering that recovery codes were stored only on the phone being replaced; a screenshot of success is not enough if the recovery channel has never been tested.
Use “2. Generate or verify backup codes and store them separately from both phones” as a checkpoint. Confirm the account or hardware identity, test one representative action, and record both the successful and failed behavior. Keep recovery codes, keys, or exports outside the affected device and never paste them into a search box or support chat.
Action map
What to do next
| Layer | Focus | Working instruction |
|---|---|---|
| Check | 1. List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token | List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token. |
| Action | 2. Generate or verify backup codes and store them separately from both phones | The next move is specific: Generate or verify backup codes and store them separately from both phones. |
| Verify | 3. Test a fresh sign-in in a private browser before removing the old registration | Start this stage with test a fresh sign-in in a private browser before removing the old registration. |
3. Test a fresh sign-in in a private browser before removing the old registration
Start this stage with test a fresh sign-in in a private browser before removing the old registration. The purpose is move every MFA-protected account to the new phone while preserving at least one independent recovery path, not merely reaching the next screen. Because assuming cloud sync covers work, banking, gaming, and custom TOTP entries equally, change one variable and observe the exact function that was failing before continuing.
Under “3. Test a fresh sign-in in a private browser before removing the old registration,” include a stop condition: loss of the only copy, an unmatched key identifier, unstable power during a write, an unknown administrator, or instructions for a different model. Preserve evidence and escalate at that boundary instead of improvising.
4. For work or school accounts, confirm whether an administrator must reset the method
A reversible workflow makes move every MFA-protected account to the new phone while preserving at least one independent recovery path easier to verify. For work or school accounts, confirm whether an administrator must reset the method. Label any export with date and device, separate it from the live system, and make sure its location does not depend on the account currently being repaired.
The scenario behind “4. For work or school accounts, confirm whether an administrator must reset the method” is deleting the old app before confirming the new token. Test the safer alternative on one account, file, or endpoint first. When it works, repeat the check after a restart or clean sign-in so cached state does not create a false pass.
5. Photograph nothing that exposes the QR seed or recovery code to cloud galleries
For “5. Photograph nothing that exposes the QR seed or recovery code to cloud galleries,” follow the official path: Photograph nothing that exposes the QR seed or recovery code to cloud galleries. Match the service domain, device model, hardware revision, region, and ownership type before downloading software or changing security state. Forum advice can identify a symptom but cannot verify those identifiers for you.
The risk is discovering that recovery codes were stored only on the phone being replaced. Document the decision that permits the next action and the route back if it fails. On managed equipment, involve the administrator before clearing enrollment, encryption, or authentication records that may be controlled elsewhere.
Protect the recovery route for move every MFA-protected account to the new phone while preserving at least one independent recovery path
List each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token. Treat that instruction as an evidence step for move every MFA-protected account to the new phone while preserving at least one independent recovery path. A useful result states what was tested, from which account or network, and whether background synchronization, active sessions, metadata, or permissions also changed.
The reason for this discipline is assuming cloud sync covers work, banking, gaming, and custom TOTP entries equally. Review hidden state after the visible fix: recovery addresses, forwarding rules, OAuth grants, DNS, encryption, backups, and pending queues as relevant to “Protect the recovery route for move every MFA-protected account to the new phone while preserving at least one independent recovery path.” Remove temporary access only after rollback is no longer needed.
A dry run for deleting the old app before confirming the new token
A calm incident record begins with generate or verify backup codes and store them separately from both phones. Tie it to “A dry run for deleting the old app before confirming the new token” and to the intended outcome: move every MFA-protected account to the new phone while preserving at least one independent recovery path. Avoid a chronological diary of every click; preserve the few observations that change the diagnosis or next action.
Name the avoided error—deleting the old app before confirming the new token—and the point where specialist help becomes safer than another attempt. Store the summary away from the affected device. That makes the next response start with a tested method instead of an anxious memory.
What to preserve before cleanup
Finish “What to preserve before cleanup” by proving both normal use and recovery. Test a fresh sign-in in a private browser before removing the old registration. Then sign out, reboot where appropriate, and repeat the critical action with the old fallback still available. The aim is move every MFA-protected account to the new phone while preserving at least one independent recovery path under ordinary conditions, not a one-time success.
Do not close the incident while discovering that recovery codes were stored only on the phone being replaced remains possible. Confirm alerts, backups, ownership, and the location of recovery material. Delete exposed temporary copies, but retain the short non-secret record that explains the verified route and its stop conditions.
How to verify the final state
For work or school accounts, confirm whether an administrator must reset the method. This action advances the goal to move every MFA-protected account to the new phone while preserving at least one independent recovery path. It also addresses the concrete failure mode “assuming cloud sync covers work, banking, gaming, and custom TOTP entries equally.” Capture the starting state and keep the last working device, session, or copy available until the new path has passed an independent test.
For “How to verify the final state,” verify the result from a fresh session or second device. Note the exact screen, version, owner, and time without copying secrets. If the result cannot be repeated, return to the preserved state rather than stacking another irreversible change on top.
When to stop and escalate
The next move is specific: Photograph nothing that exposes the QR seed or recovery code to cloud galleries. Do it before any reset, deletion, migration, or firmware change connected with move every MFA-protected account to the new phone while preserving at least one independent recovery path. The mistake to prevent is deleting the old app before confirming the new token; a screenshot of success is not enough if the recovery channel has never been tested.
Use “When to stop and escalate” as a checkpoint. Confirm the account or hardware identity, test one representative action, and record both the successful and failed behavior. Keep recovery codes, keys, or exports outside the affected device and never paste them into a search box or support chat.
A two-minute record for the next incident
Start this stage with list each account and whether it uses TOTP, push approval, passkey, SMS, or a vendor-specific token. The purpose is move every MFA-protected account to the new phone while preserving at least one independent recovery path, not merely reaching the next screen. Because discovering that recovery codes were stored only on the phone being replaced, change one variable and observe the exact function that was failing before continuing.
Under “A two-minute record for the next incident,” include a stop condition: loss of the only copy, an unmatched key identifier, unstable power during a write, an unknown administrator, or instructions for a different model. Preserve evidence and escalate at that boundary instead of improvising.
The final recovery rehearsal
A reversible workflow makes move every MFA-protected account to the new phone while preserving at least one independent recovery path easier to verify. Generate or verify backup codes and store them separately from both phones. Label any export with date and device, separate it from the live system, and make sure its location does not depend on the account currently being repaired.
The scenario behind “The final recovery rehearsal” is assuming cloud sync covers work, banking, gaming, and custom TOTP entries equally. Test the safer alternative on one account, file, or endpoint first. When it works, repeat the check after a restart or clean sign-in so cached state does not create a false pass.
