How to merge duplicate contacts on iPhone

Once you've found the duplicates in your iPhone contacts, the next question is which one to keep and what to do with the others. There are four reasonable strategies. Each has a use case where it's right and several where it's wrong.

Before you merge: back up

Whichever strategy you pick, make a .vcf backup first. iCloud sync isn't a backup — once you merge, the change syncs to all your devices instantly and you can't undo. A separate .vcf file gives you a rollback option. See how to back up your iPhone contacts without iCloud.

Strategy 1: Keep first

Pick the first occurrence, delete the others. Useful when you have a known-clean source (your manual entries) and a known-noisy source (an imported CSV from a colleague), and the imports are second-class.

• Use it when: the duplicates came in from a one-time import you didn't review, and your originals are correct.
• Don't use it when: the imported version actually has more recent data (a new mobile number).

Strategy 2: Keep most complete

Of the duplicate set, keep whichever record has the most populated fields, delete the others. Solid default for most cases. The contact with name, phone, email, organization, address, and notes wins over the contact with just name and phone.

• Use it when: you don't know which duplicate is the "right" one and you want to keep maximum information without manually inspecting.
• Don't use it when: the more-complete version has stale data (an old job title, an old email).

Strategy 3: Merge fields

Combine all the fields from every duplicate into a single contact. Two phone numbers? Both. Two emails? Both. The contact gets bigger and richer, but never loses information.

• Use it when: the duplicates exist because you have a personal mobile in one and a work landline in another, and you want both numbers under one card.
• Don't use it when: the duplicates are genuinely two different people with similar names — merging will create one Frankenstein contact.

Strategy 4: Delete all duplicates

Remove every contact that has a duplicate, keeping nothing. This is the nuclear option. Useful in one specific case: you imported a contact list you shouldn't have (a colleague's, a vendor's), and you want to scorch-earth remove anything that overlaps with your real address book.

• Use it when: you're cleaning up after a bad import and you want to start over.
• Don't use it when: any duplicate has data you might need.

How iOS handles merges

Apple's built-in merge in iOS 17+ does what's roughly equivalent to Strategy 3 (merge fields), but only for the duplicates iOS detects. Apple's official guide covers the basics. The downside: it doesn't catch format-only duplicates like +1-415-555-2671 vs (415) 555-2671.

How Pluck handles merges

Pluck presents all four strategies in the Remove Duplicates sheet. You pick the strategy that fits, and Pluck applies it to every duplicate group it found. Because Pluck normalizes phone numbers before grouping, it catches format duplicates iOS misses.

Pluck's merge runs on the in-memory contact list, not on your iOS address book, by default. That means you can experiment with different strategies (load contacts → merge → look at the result → reset) without changing anything on your device. If you like the result, you can either export it as a clean CSV/VCF or use the Clean Up tool to write the cleaned list back to your phone — with a confirmation dialog before any device write happens.

What to inspect before clicking Merge All

• The total number of contacts before and after. If the difference is bigger than expected, something's off.
• A handful of merge results manually. Pick five duplicate groups, see what the merge produces, then commit.
• Whether you have any contacts where two different humans share a phone number (rare but happens — shared family landlines, work hotlines). Strategy 3 will incorrectly merge them.