How to back up your contacts — and actually test the restore

Backing up your contacts takes one export per account and about twenty minutes a year. The part most people miss: iCloud and Google are mirrors, not archives — delete a contact on your phone and every synced copy deletes itself too. A dated vCard file on your own disk is the only copy that answers to nobody.

Sync is a mirror, not an archive

Every account that holds your contacts — iCloud, Google, Exchange — promises that the list looks identical everywhere. That is the entire job of contact sync, and it does that job ruthlessly: change a card on one device and the change lands on all of them in seconds. Deletions are changes. Bad merges are changes. A misbehaving third-party app with contacts permission makes changes too.

So the architecture that protects you against a lost phone is exactly the architecture that cannot protect you against yourself. The classic failure stories all route through sync: someone prunes their list on a quiet Sunday and realizes on Tuesday they deleted the wrong “M. Schmidt” — from every device at once. Someone’s child gets the unlock code. Someone signs out of an account and watches half the address book vanish, because the contacts lived in the account, not the phone — the same trap our guide to Gmail-and-iPhone contact sync unpacks in detail.

Google at least keeps a 30-day undo history. Apple offers recovery for some scenarios. Neither replaces a file you control, with a date in its name, sitting somewhere no sync engine can touch.

3-2-1, translated for contacts

Photographers solved this problem two decades ago. Peter Krogh’s 3-2-1 rule (2009) says: keep three copies of anything that matters, on two different kinds of storage, with one copy off-site. The rule was written for terabytes of photos; your entire address book fits in a file smaller than one photo, which makes following it almost embarrassingly cheap.

Translated: copy one is the live data in your account. Copy two is the exported vCard on your computer. Copy three lives off-site — an encrypted cloud folder, a USB stick in a drawer at your parents’ place. Two media means not putting both exports on the same laptop that holds copy two. That’s the whole system. The only discipline it demands is the export itself, once a year.

Where the export lives on each platform

Vendors move these menus occasionally, so treat the paths below as the current location, not eternal truth — the export function itself is stable everywhere.

1. iCloud — via iCloud.com

   The full export lives on the web, not the phone. Sign in at iCloud.com → Contacts, select all (Ctrl/Cmd-A), open the gear icon in the corner, and choose Export vCard. One .vcf file containing every iCloud contact lands in your downloads. On iOS itself you can only share individual cards, which is why the browser route is the one to remember.

2. Google — contacts.google.com

   Open contacts.google.com, click Export in the sidebar, and pick vCard (do a second pass with CSV if you want an editable copy). Exporting from the web covers everything in the account, including contacts your phone hides in unused labels.

3. Android — local file export

   In the Google Contacts app: Fix & manage → Export to file, save the .vcf to the phone’s storage, then move it off the phone. Samsung and other manufacturer apps keep the same function under Settings → Import/Export contacts. This local route also works for contacts that never synced anywhere — the ones stored only “on device”.

4. Mac — Contacts archive or vCard

   In the macOS Contacts app, File → Export → Export vCard for a portable file, or File → Export → Contacts Archive for a full-fidelity Apple-only snapshot. Export the vCard — the archive format only restores into Apple’s own app, which is a bet on where you’ll be in five years.

vCard or CSV?

Export both if in doubt, but know what each is for. A vCard is the contact-exchange standard: it holds multiple numbers and emails per person, photos, addresses, and notes, and every contacts platform can import it. It is the format that restores cleanly.

CSV is a spreadsheet: one row per person, one column per field. Perfect when you want to bulk-edit job titles or sort by company — and reliably messy at everything else. Photos don’t fit in a CSV. Column names differ between Google’s and Outlook’s dialects. And opening a CSV in Excel is the classic way to turn every ü into garbage before you’ve changed a single row. Our practical vCard guide covers the format details and the encoding traps.

For people in the EU there’s a quiet legal footnote here: data portability is a right (GDPR, Art. 20), and the vCard export is precisely how contact platforms honor it. Using it once a year is just collecting what’s already yours.

The annual ritual — and the test restore

Pick a date you already remember — first weekend of spring, the day after your birthday — and put a recurring reminder on it. The session: export a vCard from each account that holds contacts, name the files by date and source, place them in your 3-2-1 spots, and then do the one step that separates a real backup from a feel-good file.

The test matters because exports fail silently. A truncated download, an encoding mishap, an export taken while sync was mid-conflict — the file looks fine at 48 KB and turns out to hold 60 contacts out of 800. You want to learn that in the five-minute test, not on the day the account is gone.

While the file is open in the spare account, give it ten seconds of judgment: if a third of what you see is duplicates and dead entries, the backup is faithfully preserving mess. A duplicate-merge session before the next annual export means next year’s archive is worth restoring.

Where you point the restore one day is a separate decision — back into the same platform, or into something you control more directly. That’s the question our walkthrough on moving contacts out of Google answers; it’s also the design reason Endearist keeps your data in a local file you can copy like any other, so the backup ritual is a file copy rather than a vendor request.