Make an access map before resetting anything
Replacing a phone can interrupt several linked accounts at once. Your exchange may depend on email; email may depend on an authenticator on the old phone. Start with a paper checklist of the services you use, their official sign-in addresses and the recovery methods you have configured. Record that a recovery method exists, not its secret value. This guide is a preparation exercise, not a promise that a provider will restore access.
Separate the methods that are easy to confuse
| Method | What to check before moving |
|---|---|
| SIM and SMS | You still control the registered number and can receive messages. |
| Authenticator app | Follow that app’s official transfer or recovery procedure. |
| Email account | Test access and review the configured recovery options. |
| Backup codes | Locate the protected copy; never paste it into a support chat. |
| Wallet recovery | Check the wallet’s own recovery method separately from exchange access. |
Changing a Pakistani mobile number does not automatically update every service that uses the old number. Use each provider’s account settings and current help instructions. Do not assume that a SIM change also transfers an authenticator.
Practise with the old phone still available
Choose a time when you can pause. Charge both devices, update through their official stores and open the service from a saved, verified address. Complete the provider’s supported migration, then test a normal sign-in on the new phone. Keep the old device until you have checked the linked email and other required accounts. If the provider introduces an additional review or withdrawal restriction, read its stated conditions rather than trying repeated workarounds. No particular waiting period is assumed here.
Use recovery codes only in the right place
For a Google Account using eligible two-step verification settings, Google documents backup codes as an alternative second step when the usual method is unavailable. Other providers have their own rules. Do not treat a Google code as an exchange recovery code. Store each service’s recovery material according to its official instructions, clearly separated from this non-secret checklist. A support agent asking you to send the complete set of codes is a reason to stop and verify the support channel.
A completion sheet and common questions
- New phone: normal sign-in tested on each required service.
- Email: accessible independently of a single lost device where the service supports it.
- Registered number: reviewed inside the account, not assumed from the SIM.
- Old device: retained until checks are complete; follow the manufacturer’s reset procedure only when ready.
- Recovery record: date and outcome recorded, with no passwords or codes.
Should I send CNIC images in a messaging group to speed things up? Do not use a public group as a recovery channel. If official support requires identification, verify the destination and the specific requirement first. What if the old phone is already lost? Use the provider’s official lost-device and recovery procedure; this checklist cannot replace identity review. Will moving the app move a self-custodial wallet? Do not assume so. Its recovery model must be checked separately before uninstalling or resetting anything.
Sources and method
Google Account Help: backup codes; the migration checklist is an original planning aid
