A new phone number can break access to an exchange, wallet dashboard, or recovery channel even when the blockchain address remains unchanged. SIM swaps and lost devices also create a window for account takeover. Overseas users may change carriers, cross a roaming boundary, or hold several numbers for work and family. This guide separates account identity from wallet custody and provides a safe handover sequence without asking anyone to reveal a secret.
Map every dependency
Before cancelling a number, list services that use it for login, alerts, withdrawal approval, recovery, and customer support. Include email, password manager, exchange, banking, and authenticator accounts. Mark which service can change the number only after identity review. A wallet seed generally does not depend on a SIM, while a hosted account may. This map prevents the common mistake of disabling the old number before moving a critical recovery path.
Prefer independent authentication
Where supported, use a passkey, hardware security key, or authenticator app rather than SMS alone. Keep backup codes offline and do not store them in a screenshot folder that syncs to every device. Test the new method while the old phone still works, then sign out of the old sessions. A stronger factor reduces SIM-swap exposure but does not remove phishing or malicious-app risk.
Transfer the authenticator carefully
Use the vendor’s documented export or transfer process and verify the destination device before deleting the old token. Some apps display a QR code that grants access; treat it like a secret and never send it through chat. Test a low-risk login and a recovery path. If a service requires a support ticket, use its official domain and provide only the requested identity evidence, never a seed or private key.
Change phone and recovery details
Update the number, email, trusted devices, withdrawal whitelist, and notification preferences in the service’s security settings. Check the effective time and any withdrawal lock. Save the confirmation in your records. If the service insists on a cooling period, keep the old channel protected until the change is complete. Never approve an unexpected reset because an agent claims the account will otherwise be closed.
Handle the old device
Sign out, revoke sessions, remove wallet extensions, erase eSIM profiles, and factory-reset the phone only after verifying that the new device works. Check whether cloud backups contain authenticator data or wallet screenshots. Keep the old device offline for a short review period if that helps confirm no dependency remains. A recycled phone should not retain browser autofill, recovery codes, or identity documents.
Document the handover
Record date, services changed, factors tested, outstanding locks, and official support references. Do not record passwords, seeds, or one-time codes. Tell a trusted family operator how to recognize a real alert and where the emergency instructions live. This creates a repeatable transition for the next move and makes it easier to distinguish a planned number change from a genuine takeover attempt.
Operational worksheet
Perform the number change in phases. First add the new authenticator or passkey and test a low-risk login. Next update the service number and wait through any stated cooling period while keeping the old channel protected. Then revoke old sessions, remove the old SIM or eSIM, and check recovery email and withdrawal settings. Export or print backup codes only through the vendor’s documented process and store them offline. Ask a family operator to identify which alert is planned and which is suspicious without sharing a code. If the old number is already lost, contact the carrier and service using official channels; do not approve an unexpected reset. Record each completed step and its date. The sequence reduces the chance that a rushed carrier change becomes an account takeover or an irreversible lockout.
If the carrier cannot protect the old number, treat it as exposed and prioritize email, passkeys, and service freezes. Check whether an authenticator backup was copied to a cloud account and revoke that account if necessary. A successful login is not enough; test the withdrawal approval path and alert delivery before discarding the old device.