PasswordX

Keep access when you move your TOTP authenticator

Prepare independent recovery, move TOTP one account at a time, and verify access before retiring your old authenticator.

A new phone or a different place to keep codes changes your recovery plan as well as your daily sign-in. Before retiring the old setup, prove that the new one works and that you have another way in. Keep your current authenticator and signed-in sessions available while you check.

TOTP generates changing codes from a shared secret and time, as specified in RFC 6238. The setup QR code or text key carries the secret needed to generate future codes. Treat that setup material as a credential, rather than an ordinary screenshot you can leave in a chat or photo folder.

Make a list before moving anything

List the services in your current authenticator. For each, record the login name, where you keep the password, and the recovery options the service offers. Mark accounts you cannot currently open. Resolve those first instead of discovering the problem after erasing the old phone.

PasswordX can save TOTP information in a personal password record and generate the corresponding code. Saving that information is separate from changing enrollment at the protected service. Check the service's own instructions for an authenticator transfer, an additional authenticator, or replacing the existing setup.

Use a known website address and confirm the intended account. Personal and work accounts at the same provider can look similar. Follow workplace rules for work credentials rather than moving them into personal storage as part of the same cleanup.

Check the recovery chain independently

Keeping the password and TOTP secret in the same vault is convenient. Access to that unlocked vault can also expose both. Decide whether the account's consequences call for a separate trusted authenticator or another supported method before choosing the new location.

Then imagine that the new location is unavailable. Can you obtain the recovery material without it? A backup file on the same lost phone and a recovery code inside a locked vault can both leave you dependent on the thing you are trying to recover.

Do this check for the password manager itself, the email account used for recovery, and the protected service. Write down what you can open first with nothing else unlocked. Identify a route you can actually use before changing the working arrangement.

Save the service's recovery material

Look for backup codes or another recovery option in the service's security settings. Follow its own instructions; recovery rules vary. For example, Google documents that its backup codes are single-use and that generating a replacement set invalidates the old set.

Keep the required material somewhere protected and independently accessible. A sealed paper copy in a secure location may suit one person; another may use a separately protected digital location. Label it clearly enough to identify the account without including unnecessary personal information.

If you print a new set, replace obsolete copies. If you intentionally use a backup code to test access, mark it used and follow the service's instructions for maintaining the remaining set. Avoid testing recovery by deleting your only working authenticator first.

Move and verify one account at a time

Use the service's supported process for the move. If it requires replacement enrollment, complete the code confirmation there. Try a fresh sign-in using the new authenticator while retaining your original session and recovery material. Mark the account complete only after the sign-in succeeds.

If codes are rejected, check the selected account, setup secret, and device time. Time is part of the TOTP calculation. Follow the service's troubleshooting instructions before repeating enrollment. Keep unresolved accounts on your list rather than assuming that copying a record proves a working sign-in.

Know what the code protects

A changing code can still be entered into a fake website and relayed to the real one. NIST's authentication guidance does not classify manually entered OTP codes as phishing-resistant. Check the website before entering both password and code; do not approve requests merely because a caller knows your name.

If setup material may have been copied, replace that secret through the protected service and review other access paths. Removing a record from your authenticator does not tell the service to reject another copy. Retire the old device only after every needed account has a verified new sign-in and a reachable recovery route.

Sources

  1. https://datatracker.ietf.org/doc/html/rfc6238
  2. https://support.google.com/accounts/answer/1187538?hl=en
  3. https://pages.nist.gov/800-63-4/sp800-63b/authenticators/