How to Transfer Contacts to a New Phone

Transferring contacts sounds trivial until you realise your contacts are not in one place. Some live in Google, some in iCloud, some on the SIM, and a few only on the old handset. Audit where yours actually are first — then the transfer itself is minutes, not a panic.

Updated September 2026By the AI Help Guide editorial team10 min read

The Audit

Seven Places Contacts Can Live — Check All of Them

The reason contact transfers fail is almost never the transfer. It is that the sender assumed one source of truth when there were several, and the phone's Contacts app politely merged them into a single list so the difference was invisible. On Android, open Contacts and look at the account switcher or the filter at the top; on iPhone, check Settings > Contacts > Accounts. Then work through this table.

Two rows matter most. Device storage is the classic silent loss: contacts saved there do not follow your Google or iCloud sign-in, so if you erase the old phone first they are gone. Messaging apps are the classic false comfort — people assume WhatsApp is a backup because it shows names, but it is reading the same phone book, not storing a copy of it.

If the audit turns up contacts in more than one place, consolidate before you move anything. Merge them in the web interface where you can see the full field set, then export a single vCard as your portable master copy. Doing this on the old phone while you still have it is far easier than reconstructing it later.

The Routing

Pick Your Method by Scenario, Not by Preference

There is no universally best transfer method; the right one depends entirely on which two ecosystems you are crossing. This table gives the recommended route and the reliable fallback for each combination.

The pattern worth internalising: same-ecosystem moves are a sign-in, cross-ecosystem moves are a file. Within Android or within iPhone, syncing is genuinely enough because both ends speak the same account language. The moment you cross over, a vCard is the honest tool — it carries the full field set and does not care which vendor made the handset.

Note also the one-way trap in the third row. People switching from Android to iPhone often assume that because their contacts are in Google, the iPhone will find them. It will not, unless you install and configure Gmail sync on the iPhone, and even then the sync is one-directional in practice and can create duplicates rather than a clean copy. Move to iOS, or a vCard, is the correct route.

The vCard, Done Properly

The Portable Master Copy

A vCard — a file ending in .vcf — is the closest thing to a neutral format for contact data, and handling it well is the difference between a clean migration and a duplicate mess. The workflow that works is: export from the source, import into a web interface first, review and merge there, and only then let it reach the phone.

Importing straight to a handset skips the review step, and handsets are poor at showing you what arrived. Google Contacts and iCloud both give you a visible list with full fields and a merge tool, which is where you catch the fact that "Mom" and "Mum" are the same person before fifty duplicates settle in. Keep the exported .vcf somewhere safe afterwards, too: it is a genuine backup, independent of any account, and it is the file that saves you if a merge goes wrong.

One practical caution: do not import the same vCard more than once into the same account. There is no deduplication on import, so a repeat run doubles everything, and unwinding that by hand across hundreds of entries is miserable. If a transfer looks incomplete, re-check the source rather than re-running the import.

Cleanup

Duplicates: Merge in the Cloud, Not on the Phone

Duplicates are the normal outcome of any migration that touches more than one source, because the same person arrives twice from two different places. The instinct is to fix them in the phone's Contacts app; resist it. Phones merge conservatively and slowly, and they do not give you a rollback.

Do it in the web layer instead. In Google Contacts, Fix & manage → Merge & dedupe reviews and combines matches, and you can undo before committing. In iCloud, select contacts and use Merge Duplicates. Both show you the field-level detail that a phone hides, which is what you need when two records have overlapping but non-identical numbers.

Export a vCard backup immediately before any bulk merge. A merge that combines the wrong two people — colleagues with the same name, or two relatives sharing a birthday — is easy to do and annoying to reverse, and the backup turns it from a chore into a non-event. Then spot-check the contacts that matter most: family, your employer, your bank's relationship manager, and anyone whose record has three or more numbers.

Verification

Before You Erase the Old Phone

Contacts are the data people verify least and miss most, because the list looks plausible even when it is a third complete. Run this before the old handset leaves your hands:

• Counts roughly match between the old phone's combined sources and the new phone's list, with any gap explained.
• A sample of records opens with all fields intact — email, address, birthday, photo, and every labelled number.
• Groups or labels survived, if you used them.
• A call, a text, and an email all work from three or four important contacts.
• Nothing arrived in "On device" storage when you meant it to sync.
• A .vcf export of the final list exists somewhere outside either phone.

That last item is the one that pays off years later. Phones get lost, accounts get locked, and a merge goes wrong occasionally; a vCard you kept is the only artifact that survives all three without needing anyone's cooperation.

Privacy

Treat the File Like What It Is

A contact list is a map of your relationships, with phone numbers attached — arguably more sensitive than your photo library, because it names other people who never agreed to share their details. Handle the export accordingly: do not mail vCards to unfamiliar addresses, do not stash them in a shared folder "for convenience," and review which apps hold contacts permission on the new phone before you assume only your address book can see them.

If the old phone contained work contacts, remember that they belong to your employer's data handling, not yours, and follow policy before migrating them onto a personal device. And when you finally do erase the old handset, confirm the contacts are backed up and removed from the device — a factory reset handles the latter, but only if you actually run it.