Before changing phones, separate your Mozilla backup codes from your account recovery key

Before replacing the phone that holds your authenticator, check two different Mozilla account safeguards. Backup authentication codes provide an alternative when you cannot use the authenticator. An account recovery key serves a different purpose: retaining access to encrypted Sync data when resetting a forgotten password. One should not be filed away under the assumption that it replaces the other.
Start while your existing phone and account access still work. Keep the old device until you have completed the move and checked a fresh sign-in on a device you control. This is a preparation checklist, not a promise that every locked account can be recovered.
Make an inventory without exposing the secrets
Write down which account you are checking, which device holds its authenticator and where its recovery material is stored. Record locations and dates in the checklist, not the codes themselves. A useful inventory lets you find the right material without becoming another copy of every secret.
Open account management through Firefox or a known Mozilla address. Avoid following an unexpected recovery message. If you manage several accounts, check the account identity before changing anything; a correctly stored code for a different account will not solve the problem in front of you.
Mozilla's setup instructions require a recovery method to complete two-step authentication. Backup authentication codes are single-use. Downloading a file is only the first half of preparation: open the saved copy and make sure it is readable in the location you intend to rely on. Do not leave the only copy on the phone being replaced.
Check the recovery key separately
In account settings, the account recovery key has its own entry under Security. Mozilla explains that this key protects access to encrypted synchronized data during a password reset. Without it, resetting a forgotten password can mean losing the server-side Sync data.
Label the two types of material distinctly. A file called simply “backup” is easy to misread during a stressful recovery. Include the account and purpose in your private filing system, then choose storage you can access without first needing the unavailable phone or the locked account.
Do not test the arrangement by deliberately forgetting a password, wiping a device or resetting an account. A safer initial check is whether you can locate and read the required material while keeping existing access intact. A recovery exercise should not create the emergency it is meant to prepare for.
Finish the phone change before discarding the old setup
Mozilla's device-change guidance describes disabling and then re-enabling two-step authentication for the new setup. Re-enabling it invalidates the old backup codes. Follow the current instructions for your account and save the newly issued set before treating the migration as finished.
Recovery-phone availability varies. Do not assume that an SMS option exists simply because you have supplied a phone number elsewhere. Confirm the actual recovery choices shown in your account. If a code is rejected while the authenticator is still available, Mozilla advises checking the correct account entry and accurate device time.
If access is already lost, consult >Mozilla's lockout guidance (opens in a new tab). A previously saved backup code or an eligible signed-in device may provide a route, depending on the situation. Do not sign out of your remaining working session merely to experiment.
Complete the move by checking the new setup, securely storing current recovery material and marking superseded copies as obsolete. The goal is a recovery path you can actually reach, with its purpose understood, before the old phone leaves your hands.


