Why do I need the old number to switch to a new one?

Many services send a confirmation code to the current number before accepting a replacement, and messengers such as WhatsApp check both. Once the old number stops receiving SMS, those changes become recovery cases.

What if I have already lost the old number?

Use backup codes or your recovery email to get in, then change the phone number. For accounts without those, you will need each service's account-recovery process, which can take days.

Should bank details be changed online or in person?

Check the bank's own process early. Many require the change inside the banking app with extra checks, and some ask you to call or visit a branch, so start those first.

Can a virtual number be my new recovery number?

Only if you will control it for as long as the account needs it. For anything important, make an authenticator app, passkey or backup codes the main recovery path, with the phone as a secondary factor.

How to Migrate Accounts to a New Phone Number

Changing phone number sounds like a settings job, but the old number is often what authorises the change. Let it lapse too early, whether through a carrier switch, a move abroad or an expired rental, and the accounts you meant to protect start asking for codes you can no longer receive.

This guide sets out a sequence that keeps both numbers useful for as long as you need them: fixing a deadline, sorting accounts by how they use your number, moving messengers and 2FA accounts in the right order, and checking the result with real codes before the cutoff.

Number migrations fail from ordering, not difficulty

Changing your phone number — new country, new carrier, retiring an old SIM, or moving accounts onto a dedicated verification number — is individually trivial per account and collectively treacherous, because the old number is usually needed to authorize its own replacement. Do the accounts in the wrong order, or let the old number die first, and you're locked out of the exact accounts you were trying to protect. The entire craft is sequencing while both numbers are live.

The migration sequence

Freeze the deadline: confirm exactly when the old number stops receiving SMS (carrier cutoff, rental expiry). Everything below happens before that date, with margin.
Build the account list from your password manager, then sort into three buckets: number-as-identity apps (WhatsApp, Telegram, Signal, Viber), number-as-2FA/recovery accounts (email, banks, exchanges, social), and number-on-file-only (deliveries, loyalty cards — batch these last, casually).
Messengers first, via their built-in flows: each has a change-number feature that migrates chats, groups, and contacts — WhatsApp under Settings → Account, Telegram in profile settings, Signal on reinstall. These flows require receiving codes on both numbers; they are impossible after the old number dies.
2FA accounts next, one at a time: log in, add the new number, confirm it, remove the old one, and — while you're there — switch the account to TOTP or passkeys so the next migration doesn't involve SMS at all. Banks often require doing this in-app or in-branch; start them early.
Verify by test, not memory: before cutoff, trigger a real SMS challenge on your five most critical accounts and confirm codes arrive on the new number.

If the old number is already gone

Recovery inverts the workflow: backup codes and recovery email become your entry path, then each service's identity-verification process for the stragglers (ID upload, waiting periods). It works, slowly. The lesson survivors take away is architectural: anchor accounts to factors that don't churn — authenticator apps, passkeys, backup codes — and treat any phone number, personal or virtual, as a replaceable component rather than the foundation. Migrations then become five minutes of settings, not a rescue operation.

How should you track a migration so nothing is missed?

A migration spread over a couple of weeks needs a simple tracker, because it is easy to believe you changed an account when you only added the new number and never removed the old one. A spreadsheet or a tagged collection in your password manager is enough.

For each account, record:

Work through the tracker in short daily sessions rather than one marathon, and sort unfinished items by risk each time. Email accounts deserve special care, because they usually reset everything else; confirm the new number and recovery email there before touching less important services.

If you can, keep the old number active for a few days after the last change. Stragglers you forgot, such as a delivery app or an old two-factor prompt from a shared work tool, will show up as messages on the old SIM, and each one is a row you missed. Add it, fix it, and only then let the old number go.

The service name and its bucket: messenger, 2FA or recovery, or contact detail only.
Whether the new number is added, confirmed by code, and the old number removed.
Whether the account now has an authenticator app, passkey or fresh backup codes.
Any service that needs a branch visit, phone call or waiting period, with the date you started.
The date you last saw a real SMS from that service arrive on the new number.

Lawful SMS verification only. Follow each platform’s terms. Ucode is not for bulk account farming or ban evasion.

Key takeaways

Sequence matters: finish every change while both numbers can still receive SMS.
Messengers first: their change-number flows move chats and contacts but need both numbers live.
Test, do not assume: trigger real codes on your most important accounts before the old number goes.

In short

Number migrations go wrong when the old number dies before its replacement is confirmed. Set a cutoff date, list accounts by how they use the number, move messengers first and 2FA accounts next, verify with real codes, and use the move to shift key accounts to non-SMS factors.