The two cards look redundant. Both say “Alex Morgan.” One has a work email, the other a mobile number. Combining them would make the contact list tidier.
It could also give one person another person’s history.
Contact cleanup starts with an identity decision, followed by a storage decision. Are the cards actually about the same person? And are they duplicate records in one account, or separate records that belong to different accounts?
Apple’s Contacts app treats those situations differently. Same-account cards can be merged; cards from different accounts can be linked into a combined view while remaining separate in their original accounts. [1] [2]
That distinction is more useful than a blanket instruction to merge every duplicate the app detects.
Five cards worth pausing over
The examples below are invented. They illustrate decisions a contact manager cannot safely settle from a display name alone.
| What you see | What you know | Sensible next step |
|---|---|---|
| Two Maya Patel cards in one account | Same verified email; one has a newer phone number she supplied | Review the values, preserve a backup, then consider merging |
| Two Alex Morgan cards | Different employers and emails; no evidence they are one person | Keep separate until identity is established |
| A personal and a work card for Sam | Sam confirmed both; cards belong to different accounts | Consider linking the display rather than moving account ownership |
| “Priya — old work” and “Priya” | A verified message confirms her new address | Preserve the old address as historical context where appropriate; review labels |
| A family card with a shared phone number | Several people use the number | Do not equate a shared number with one identity |
The decision sheet includes these cases and a blank review record. Its purpose is to slow down ambiguous combinations, not to encourage collecting more personal information to resolve them.
Make a restorable copy first
Before altering a substantial contact book, use an appropriate backup or export and verify where it was saved. Apple documents a Contacts Archive for the full collection and vCard export for selected contacts. Those serve different purposes; choose deliberately rather than assuming every file is an interchangeable backup. [3]
Keep that file somewhere private. A contact archive can contain more than phone numbers. If you are working with an employer’s account, use its approved process and tools.
Then try one unambiguous case. A successful preview is not the same as knowing what will happen to every record, and a large batch is a poor place to learn how your current setup handles conflicting fields.
Merge within an account
Apple’s documented Mac workflow offers Card → Look for Duplicates, as well as Card → Merge Selected Cards for cards you choose. A merge preserves unique information in the resulting card. [1]
“Unique” is not the same as “current.” A preserved phone number may be obsolete. Review labels and the information you intend to use before making the next call or sending the next message.
Where the same field has contradictory values, investigate the source. A recent value you typed from memory can be less reliable than an older value the person confirmed. Recency helps, but it is not the only evidence.
If you cannot establish which record is correct, keep the uncertainty visible. Tidiness is not worth silently assigning somebody the wrong employer or correspondence.
Link across accounts
Apple documents linking selected cards when one person has records in different accounts. The underlying cards remain while Contacts presents the combined information. [2]
This can reduce visual duplication without making a personal account the new home of work-controlled data. It does not, by itself, resolve organization policy, permission to export, or how another app interprets the cards.
Check the source account before editing a field. Your goal may be to improve what you see locally, while a change to a synced record can affect what is stored in that account. Read the control being used rather than assuming that “one card on screen” means one storage location.
The precise labels can vary with the selected macOS guide and your account configuration. The linking source cited here is Apple’s macOS 26 documentation; we did not operate a real contact book as part of this article.
Review the import choices
When importing contacts, Apple offers choices about old and new records. An “apply to all” option saves clicks; it does not examine the relationship behind each match for you. [4]
Use a small sample when evaluating a new destination. Check a person with several addresses, a dated note and a group membership. Confirm that the result remains understandable. Our personal CRM export test provides a sample designed for that inspection.
Contact cleanup can improve the inputs to relationship tools, but it should not rewrite history. An old conversation may correctly show someone’s former name, address or organization. You can preserve that source while keeping a current contact record clear.
Kluro brings conversations together around people and lets you return to the original exchange. The Contacts source page explains the connection. Carry out the merge or link in Apple Contacts, with the account and identity checks above.
Afterward, open a few reviewed records from the account you intend to use. Check the address and the relevant note before relying on them. Leave an ambiguous pair separate and record what still needs confirmation.
Sources
- Merge contact cards in Contacts on Mac — Apple Support. Living documentation. Reviewed 29 September 2026.
- Link contacts in Contacts on Mac — Apple Support. Living documentation. Reviewed 29 September 2026.
- Export or archive contacts in Contacts on Mac — Apple Support. Living documentation. Reviewed 29 September 2026.
- Resolve duplicates while importing contacts — Apple Support. Living documentation. Reviewed 29 September 2026.