How do I transfer my contacts when switching carriers in 2027?

What it is and why it matters

Switching carriers in 2027 is functionally two separate operations that people conflate into one: transferring the phone *number* (called Local Number Portability, or LNP) and transferring the *contacts* stored on the device or in the account. Carriers only own the number; they never owned your address book, so the actual contacts transfer is a cloud-sync problem, not a carrier problem. This distinction matters because most failed transfers happen when someone assumes canceling the old carrier will "hand off" contacts automatically — it will not. If you cancel service with your old carrier before the number ports and before your contacts are backed up to a cloud account, you can permanently lose both.

By 2027, nearly every flagship device ships eSIM-primary or eSIM-only, which changes the mechanics slightly: instead of physically moving a SIM card, you're either scanning a QR code from the new carrier or using carrier-to-carrier eSIM transfer built into iOS and Android, where the new carrier's profile downloads directly onto the device while the old one is still present. This makes the switch itself faster, but it does nothing for contacts — those still live in whichever cloud account (Google, iCloud, Samsung Cloud, or a CRM-synced account for business phones) you've configured as the sync target. For a RevOps or sales team specifically, this matters more than for a typical consumer: rep phones often have hundreds of live prospect and customer contacts, some synced from a CRM via a mobile app, some added manually in the field. Losing those on a botched carrier switch is a direct revenue-continuity risk, not just an inconvenience.

The core things you're actually managing when you "switch carriers" are: (1) the phone number itself moving from carrier A to carrier B, (2) the physical or virtual SIM/eSIM provisioning, (3) the contacts and their sync source, and (4) any carrier-specific services layered on top — visual voicemail, RCS messaging, spam-call filtering, MDM enrollment for company-owned devices. Treating all four as one step is where most transfer problems originate.

The step-by-step process

The safe sequence is the same whether you're moving from a major national carrier to another, or from a national carrier to an MVNO. Skipping the backup step or canceling old service too early are the two most common points of failure.

1. Back up contacts to the cloud first. On Android, confirm Settings > Google > Backup shows contacts syncing to your Google Account. On iPhone, confirm Settings > [your name] > iCloud has Contacts toggled on. If contacts live only on the SIM card (rare now, but common on older or budget phones), export them to a vCard (.vcf) file manually before doing anything else.
2. Get your account number and port-out PIN from the current carrier. Every major US carrier requires this PIN (sometimes called a transfer PIN or NPA) to authorize the port; without it the new carrier cannot pull the number.
3. Sign up with the new carrier and give them the old number plus the port-out PIN during activation. Do not cancel the old carrier's service yet.
4. Activate the new SIM or eSIM. For eSIM, this is usually a QR-code scan or an in-app "Transfer eSIM" prompt that appears when both phones are on the same Wi-Fi network and both carriers support the transfer.
5. Wait for port confirmation, which arrives by text or in-app notification, then confirm the new line has full service (calls, texts, data).
6. Sign into the same cloud account (Google/iCloud) on the new device or with the new SIM active, and let contacts resync. This is the actual "contacts transfer" step — everything before it was number and connectivity plumbing.
7. Only after contacts and number are both confirmed working, cancel the old carrier's plan to avoid double-billing.

Costs, timelines, and typical ranges

Number porting itself is free by federal rule in the US — the FCC prohibits carriers from charging a fee specifically for porting a number out, though some carriers charge an unrelated SIM/eSIM activation fee, usually in the $10–$35 range, when you start new service. Contacts transfer, since it rides on Google or Apple's free cloud sync, costs nothing beyond whatever storage tier you're already on (Google's free tier is 15 GB shared across Gmail, Drive, and Photos; contacts themselves take up a negligible fraction of that even with several thousand entries).

Timelines vary by transfer type. Porting a number between two carriers on the same network technology (e.g., two GSM-based carriers) in the US typically completes within a few hours and often same-day; international ports, or ports involving a business/multi-line account, can take 1–3 business days because they require manual verification of the account holder. The eSIM provisioning step itself — the actual profile download to the new device — usually takes under 10 minutes once the port is authorized. Contacts resyncing is nearly instant, typically under a minute for a few hundred contacts, once you're signed into the cloud account with an active data or Wi-Fi connection; a few thousand contacts with photos attached can take several minutes.

For a business switching an entire team of reps at once, plan for a staggered rollout rather than a single cutover day: port 5-10 lines at a time, confirm each ports cleanly with contacts intact, then proceed to the next batch. This limits how many reps are without a working phone simultaneously if something goes wrong with a batch, and it gives IT or RevOps time to catch a misconfigured MDM profile or CRM sync setting before it repeats across the whole team.

Where teams get it wrong

The single most common mistake is canceling the old carrier's service before confirming the port completed and contacts resynced on the new line — once the old account is closed, the port-out PIN becomes invalid and reactivating a canceled number is far harder than porting an active one, sometimes impossible if the number gets recycled to a new customer.

A second common failure is assuming contacts are tied to the SIM card. On modern smartphones, contacts almost never live on the SIM by default; they live in the cloud account. But contacts that were manually imported to the SIM years ago, or contacts on an older device being handed down to a new user, can genuinely be SIM-resident, and those will not follow a cloud-based transfer at all — they need an explicit "export to SIM" or "import from SIM" step in the contacts app settings.

A third failure specific to sales and RevOps teams: contacts synced from a CRM mobile app (Salesforce, HubSpot) via a middleware sync tool sometimes duplicate or silently drop when the underlying device account changes, because the sync tool was authenticated against the old device's identity rather than the person's identity. Before switching carriers on a rep's phone, confirm whether CRM contact sync is tied to the device or to the user's login — if it's device-tied, re-authenticate the sync app on the new device rather than assuming it will carry over.

A fourth failure is business account confusion: on multi-line family or business plans, porting one line sometimes requires the primary account holder's authorization even if a different person uses that line day-to-day. Confirm who the account owner of record is before initiating a port, especially for company-liable phone plans, or the port request will be rejected and the timeline resets.

Finally, some carriers throttle or delay eSIM transfers if the old and new carriers use incompatible network technology (for example, a CDMA-legacy carrier moving to a GSM-based one), which by 2027 is increasingly rare in the US but still surfaces with some regional or prepaid carriers. If your port stalls past 24 hours, that's the first thing to ask the new carrier's support team about.

Decision framework: when to choose what

Not every carrier switch calls for the same transfer method. The right approach depends on whether you're moving one personal device, a household plan, or a company's fleet of sales-rep phones.

For a single personal device, the standard cloud-backup-plus-port process above is sufficient; there's little reason to complicate it. For a family or shared plan, the added step is confirming who the account holder of record is and porting each line individually rather than trying to move the whole plan as one unit — carriers process ports per phone number, not per account. For a business fleet, especially one where phones are enrolled in an MDM (mobile device management) profile and reps' contacts are partially CRM-synced, the decision framework should favor a staggered batch approach over an all-at-once cutover: it isolates failures, keeps most of the sales team reachable throughout the switch, and gives IT a chance to fix a broken CRM re-authentication step on one device before it repeats across twenty.

Related questions

Do I lose my contacts if I cancel my old carrier too early?

Not the contacts themselves, if they're backed up to Google or iCloud — those stay in the cloud account regardless of carrier. What you risk losing is the phone number if the port hadn't completed yet.

Can I transfer contacts without transferring my phone number?

Yes. Contacts and number are independent; you can switch carriers and get a new number while still syncing your existing cloud contacts to the new SIM.

Does eSIM make contact transfer easier?

It speeds up activation, not contacts. eSIM removes the physical SIM-swap step, but contacts still depend entirely on your cloud account sync, same as with a physical SIM.

What happens to contacts on a company-owned phone under MDM?

They typically follow the user's CRM or email login rather than the device, but this depends on how the MDM profile is configured — confirm with IT before switching carriers on a managed device.

FAQ

Do I need my old carrier's permission to switch? You need a port-out PIN or account number from them to authorize the transfer, but you don't need their approval beyond providing that verification information — number portability is a right, not a courtesy the carrier can refuse.

How long does a carrier switch typically take from start to finish? For a single US line switching between compatible network types, expect a few hours to same-day for the port, plus a few minutes for eSIM activation and contact resync — often done within a single day.

What if my contacts don't show up after I switch? Check that you're signed into the same Google or Apple account on the new device or SIM, and that contacts sync is toggled on in settings. If contacts still don't appear, manually export a vCard backup from the old device as a fallback before doing anything else.

Can I keep both carriers active during the switch? Yes, and it's the recommended approach — keep the old line active until the new line is fully confirmed working with your number and contacts intact, then cancel.

Is there a cost specifically for transferring contacts? No, contacts transfer rides on free cloud sync services. Any fees you'll see are activation fees from the new carrier or, rarely, a SIM card fee, not a contacts-transfer charge.

Will switching carriers affect contacts synced from my CRM? It can if the sync integration is tied to the device rather than your user login — re-authenticate the CRM mobile app on the new device after the switch to be safe.

Sources

• https://www.fcc.gov/wireless-local-number-portability
• https://support.google.com/contacts
• https://support.apple.com/contacts
• https://www.gsma.com/esim/
• https://www.verizon.com/support/
• https://www.t-mobile.com/support
• https://www.att.com/support/
• https://www.consumer.ftc.gov/

Related on PULSE

• How do I set up eSIM on a new sales-team phone rollout?
• What's the fastest way to port a business phone line without downtime?
• How should RevOps manage CRM mobile sync across a rep's device changes?
• What's the difference between MDM-managed and personal contact sync for sales reps?
• How do I audit contact sync issues after onboarding a new rep's device?