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

What it is and why it matters

Switching carriers in 2027 is really two separate operations that most people conflate into one. The first is transferring the phone *number* itself, which is governed by Local Number Portability (LNP) rules and handled entirely by the two carriers. The second is transferring the *contacts* stored on the device or in the account. Carriers never owned your address book — it lives in Google, iCloud, Samsung Cloud, or a CRM-synced account — so the actual contacts transfer is a cloud-sync problem, not a carrier problem. This distinction matters because the most common failed transfer happens when someone assumes that canceling the old carrier will "hand off" contacts automatically. It will not. If you cancel service before the number ports and before contacts are backed up, 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 either scan a QR code from the new carrier or use 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. That makes the switch itself faster, but it does nothing for contacts — those still live in whichever cloud account you configured as the sync target.

For a RevOps or sales team, this matters more than for a typical consumer. Rep phones often carry 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 are actually managing when you switch carriers are: (1) the phone number 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.

It also helps to understand where contacts can physically live on a modern phone, because that determines which transfer method works. There are four storage locations: the cloud account (Google, iCloud, Samsung), the device's local storage, the SIM card itself (rare but still present on some budget and older devices), and a third-party app database such as a CRM mobile app or a dialer. A contact can exist in more than one of these at once, and the phone's contacts app usually merges duplicates visually while keeping separate underlying records. When you switch carriers, only the cloud account and any app-level sync survive automatically. Device-local contacts survive only if you migrate the whole device or restore a backup. SIM-resident contacts survive only if you explicitly export them. CRM contacts survive only if the sync integration re-authenticates on the new device.

The step-by-step process

The safe sequence is the same whether you are moving from one 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. Export a vCard file as a belt-and-suspenders fallback. Even with cloud sync confirmed, export a .vcf from the contacts app and email it to yourself or drop it in cloud storage. This takes two minutes and is the only recovery path if the cloud account gets locked or the sync target was misconfigured.
3. 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. The account number is not your phone number — it is a separate billing identifier you can find on a recent statement or by asking support.
4. 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.
5. 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.
6. Wait for port confirmation, which arrives by text or in-app notification, then confirm the new line has full service (calls, texts, data).
7. 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.
8. Only after contacts and number are both confirmed working, cancel the old carrier's plan to avoid double-billing.

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.

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 are 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. Apple's free iCloud tier is 5 GB shared, and a large contact list with photos can consume a nontrivial slice of that, so check storage headroom before relying on iCloud sync alone.

Timelines vary by transfer type. Porting a number between two carriers on the same network technology in the US typically completes within a few hours and often same-day. International ports, or ports involving a business or 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 are 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 fleet rollout, budget the labor cost too. A staggered batch of 5-10 lines per day across a 40-rep team takes roughly a week of part-time IT attention, but it avoids the far larger cost of a single cutover day where a broken CRM sync silently strips 40 reps of their pipeline contacts at once. The trade-off is straightforward: slower rollout, dramatically lower blast radius.

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 is 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.

A fifth failure, easy to miss, is shared Apple ID or Google account across a team. If several reps sign into a single shared account, contacts from one rep's phone can bleed into another's, and a carrier switch on one device can trigger a sync that overwrites another rep's address book. Confirm every rep has a distinct cloud account before you start.

Finally, some carriers throttle or delay eSIM transfers if the old and new carriers use incompatible network technology, 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 is 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 are 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 is 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 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.

There is also a method choice within the transfer itself. Cloud sync is the default and the fastest. A vCard export/import is the fallback when cloud sync is unavailable, misconfigured, or when you need a point-in-time snapshot you can verify. Direct device-to-device transfer (Apple's Move to iOS, Google's device setup) works when you are changing phones at the same time as carriers, but it copies whatever is on the old device, including stale duplicates, so clean up first. The trade-off is speed versus verifiability: cloud sync is fastest but hardest to audit mid-flight; vCard export is slowest but gives you a file you can open and count.

Related questions

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

Not the contacts themselves, if they are 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 had not 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 do not 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 do not show up after I switch? Check that you are 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 do not appear, manually import the vCard backup you exported from the old device.

Can I keep both carriers active during the switch? Yes, and it is 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 will 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://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?