How to move your contacts out of Google, step by step
De-Google your contacts in an afternoon: export via Takeout or directly, know what breaks (labels, photos), pick a destination, and keep sync sane after.
Moving your contacts out of Google is an afternoon’s work: export twice, import once, verify, then silence Google’s sync before it quietly rebuilds what you just moved. The data itself travels well — the planning is about the two things that don’t (labels and some photos) and the weeks you keep the old account as a safety net.
Export twice before you touch anything
Two exports, because they fail differently. The direct export at contacts.google.com → Export → vCard is the file you’ll import into the new home. The Google Takeout archive is the belt-and-braces copy: it wraps the same contacts in a full-account package, and if anything about the direct export turns out truncated or odd, you have an independent second pull to compare against.
-
Direct export from Google Contacts
Open contacts.google.com, click Export in the sidebar, scope it to All contacts, and choose vCard. Run it a second time with Google CSV if you want an editable copy too. Name the files by date: 2026-06-google-contacts.vcf.
-
Takeout archive
Go to takeout.google.com, click Deselect all, tick only Contacts, and export. The archive lands as a zip containing vCards split into folders (all contacts, your groups). Don’t be surprised by the structure — for the import you’ll still use the direct export; this copy is insurance.
-
Catch the device-only stragglers
On Android, contacts saved “on device” never reached Google and are in neither export. In the Contacts app, use Fix & manage → Export to file to write the local store to a .vcf as well. Three files total, all dated, all kept.
What breaks in transit
Be honest with yourself about the casualties before you start, so none of them surprises you after.
Labels and groups stay behind. Google’s contact labels are account structure, not card data — they are not inside the vCards, and no importer can resurrect them. Note down which people belong to which label first; rebuilding three or four groups at the destination is a ten-minute job when you have the list.
Photos are a maybe. Depending on export path and vCard version, contact photos arrive intact, downscaled, or missing. Spot-check after import and plan to re-add the few that genuinely matter.
Exotic fields flatten. Custom field labels, starred status, and “other contacts” (the auto-collected addresses Gmail hoards) either don’t export or arrive as generic fields. For most people this is noise; if you’ve built elaborate custom schemas, audit one card end-to-end before moving all of them. The format-level details — versions, encodings, multi-card files — are covered in our vCard guide.
Pick the destination
iCloud
The pragmatic choice for all-Apple households: native on every Apple device, zero extra software, solid web access. You are trading one large vendor for another — a trust decision more than an architecture change. Import is drag-and-drop on iCloud.com.
CardDAV provider
The open-protocol choice: privacy-focused mail hosts and self-hosted servers (Nextcloud and friends) speak CardDAV, and both iOS and Android can sync with it. No vendor owns the door, so the next migration is trivial. Mild setup cost on Android, which needs a small sync app.
Local-first app
The ownership choice: the primary copy lives in a file on your device, sync is optional rather than structural. Best for the relationship layer — notes, cadences, context — sitting on top of a lean system address book. The trade-off: it complements rather than replaces the phone’s dialer-facing store.
The deeper question behind the table is what you want to own. A CardDAV account keeps the familiar everything-syncs model under a protocol nobody can take hostage. A local-first setup inverts the model: your device holds the truth and servers are helpers — that’s the architecture Endearist is built on, with the address book staying lean in your system store and the relationship data in a local file you can copy like any other.
These aren’t exclusive. A common and sane setup: a minimal synced store (iCloud or CardDAV) for dialer and messengers, a local-first layer for everything you actually know about people.
Import and verify
-
Import the vCard at the destination
iCloud: sign in at iCloud.com → Contacts, gear icon → Import vCard. CardDAV providers: the web interface has an import function, usually under settings. Local-first apps: point the importer at the .vcf. One file, one pass.
-
Check the count first
The exported file’s contact count and the destination’s count should match to the contact. A mismatch means a truncated file or an importer that stopped at the first error — investigate before doing anything else.
-
Spot-check the awkward cases
Open five cards: one with umlauts or accents in the name, one with several numbers, one with a long note, one with a photo, one with an address. These five catch encoding, field-mapping, and photo problems in two minutes.
-
Dedupe once, properly
If the destination already held contacts, you now have overlaps. Run the built-in merge first, then catch the near-misses (“Max M.” vs “Max Miller”) with our free contact deduplicator — it runs entirely in your browser. The full merge workflow is in our duplicate-merging guide.
Keeping sync sane after the move
The move fails in week two if your phone keeps writing to the old store. Three settings close the loop.
Stop the writes. On Android, new contacts default into the Google account — change the default in the Contacts app’s settings, or sign the account out of contacts sync entirely (Settings → Accounts → your Google account → toggle Contacts off). On iPhone, set Settings → Contacts → Default Account to the new home, then disable Contacts on the Gmail account entry.
One writer, many readers. Mail apps, messengers, and backup tools with contacts permission can each re-introduce a store you just retired. After the move, audit which apps may write contacts and leave exactly one path that creates new people.
Watch the seams for a month. The mixed-store phase is where duplicates breed — the mechanics are the same ones our Gmail-and-iPhone sync guide walks through, just pointed at a different pair of accounts. Once the new home has held steady for a few weeks, delete the contacts from Google if you want the store empty — and keep the exported files forever, as the first entries in the annual backup ritual you’re now one export ahead on.
FAQ
What's the fastest way to export all my Google contacts?
**contacts.google.com → Export → vCard.** One click, one .vcf file, every contact in the account. Google Takeout produces the same data wrapped in a full-account archive split into several folders — useful as a second copy when you're leaving for good, but the direct export is the file you'll actually import elsewhere.
Do my Google contact labels survive the move?
No — **labels and contact groups stay behind**. They are account-level structure, not part of the individual vCards, so no destination can reconstruct them from the file. Before exporting, screenshot or note down which people belong to which label; rebuilding a handful of groups by hand takes minutes once the contacts themselves have arrived.
Do contact photos survive the export?
Sometimes — and that *sometimes* is the honest answer. Depending on the export path and vCard version, photos arrive intact, downscaled, or **not at all**. Treat photos as a bonus rather than a guarantee: spot-check a few cards after import, and expect to re-add the handful that matter. Names, numbers, emails, addresses, and notes travel reliably.
Where should my contacts live after Google?
Three realistic homes. **iCloud**, if your devices are Apple and you're trading one big vendor for another you trust more. A **CardDAV provider** — privacy-focused mail hosts or a self-hosted server — if you want an open protocol that any app can sync with. A **local-first app**, if you want the primary copy on your own device with sync as an option rather than a requirement.
What is CardDAV and why does it matter here?
**CardDAV** is the open protocol for syncing contacts between a server and your devices — the vendor-neutral counterpart to Google's proprietary sync. Both iOS and Android (via a small helper app) speak it. Choosing a CardDAV home means the *next* migration is trivial: any standards-compliant provider can take over, and no single company controls the door.
Can I keep using Gmail but move only my contacts?
Yes — mail and contacts are separate products that happen to share a login. Moving contacts to iCloud or a CardDAV provider changes nothing about your Gmail address or inbox. The one adjustment: tell your phone's mail and contacts settings to stop **writing new contacts to Google**, otherwise auto-saved addresses quietly rebuild the old store.
When is it safe to delete the contacts from Google?
After **two to four weeks of normal use** on the new home, not after the import. You want a full cycle of real life — a few new contacts created, an edit or two, a device reboot, one restore-style spot-check — before removing the safety net. Keep the exported .vcf files permanently either way; they cost nothing to store.
Why do I see duplicates after importing into the new account?
Usually because the destination **already held some of the same people** — old iCloud leftovers, a previous partial import, or your phone merging two stores into one view. Run the destination's built-in merge first, then a fuzzy pass for the near-misses the built-ins skip. Cleaning once, right after the move, beats living with a doubled address book.
Does the GDPR give me a right to this export?
Yes. **Article 20 GDPR** — data portability — obliges providers to hand over your data in a structured, commonly used, machine-readable format. Google's Takeout and the contacts export exist in their current, usable form partly because of that obligation. You're not exploiting a loophole; you're using a right that was written down precisely for this situation.
What happens to contacts my Android phone saved as 'device only'?
They were never in Google to begin with, so neither Takeout nor contacts.google.com includes them. Export them separately on the phone: **Contacts → Fix & manage → Export to file** (or the manufacturer's Import/Export menu) writes every local store to a .vcf. Check this before the move — discovering a forgotten device-only pocket of 80 people afterwards is a classic.
Should I sync the new account on all my devices at once?
No — settle one device first. Import on the web or one phone, let the count stabilize, fix duplicates, then enable the new account on the remaining devices. Adding three devices to a half-settled account multiplies every conflict. Sync is excellent at propagating a clean state — and equally excellent at propagating a mess.
Is a spreadsheet a reasonable destination for de-Googled contacts?
As an archive, sure — as a living address book, no. A CSV in a drawer is a fine extra backup, but it doesn't ring your phone, doesn't sync, and doesn't show caller names. The realistic destinations remain a synced account (iCloud, CardDAV) or a local-first app, with spreadsheet exports as the safety copies around them.