You met someone through your personal email. Now you need to write to them from your work account, and they are not there — not because you forgot them, but because your work account has never heard of them. So you go and look them up in your personal account, copy the address across, and now there are two records for the same person.
That is not a mistake you made. It is what happens when your contacts live in more than one account, and it happens to almost everyone who has ever had a job while keeping a personal email.
Why the same person ends up in more than one address book
Each ecosystem syncs to itself. Google syncs to Google, iCloud syncs to iCloud, Outlook syncs to Outlook. The one courtesy they extend to each other is deliberately small: enough that you can see an email address from the other ecosystem, and not much more. Google and Microsoft have no commercial reason to make each other's world pleasant — you are the customer, and the other company is not.
Apple sits in the middle of this and syncs only to itself.
So here is what "working across two accounts" actually produces, over a few years:
Six records, one person. Each slightly out of date, each with a different phone number, a different spelling of the company, two of them with mobile numbers you changed months ago. Add a third ecosystem and the pattern simply repeats.
You pay a small tax for this every day, and it is easier to notice once you have named it:
- You're in the wrong mailbox. You met them through your personal address. Now you need to write from the business one — and they are not there.
- You don't know who's calling. A client saved in Microsoft 365 rings your phone. Your phone reads Google. All you see is a number.
- You updated it once, in one place. Everywhere else still has the old number. You find out when the call doesn't connect.
None of these are urgent enough to fix properly, which is exactly why they keep happening.
Why you can't just merge them
This is the part worth being blunt about, because the obvious fix does not exist.
Google cannot merge contacts from different accounts. Their own help documentation says so. Two Google accounts you own, two accounts in different profiles, a personal account and a work account — Google will not merge the contacts across them, and will not sync one to the other either. Adding the other account to your phone shows you both sets side by side. It does not combine them. You have seen this page, or you have given up looking for it.
Microsoft's answer is aimed at administrators, not at you. The supported route for "this person belongs in the company address book" is to add them to the global address list or a shared contact folder. That is a decision made by whoever runs your employer's tenant, for their reasons, and it puts your personal contact into a system your company controls.
Apple syncs to Apple. Contacts you put in iCloud reach your Apple devices and stop there.
So the honest summary is: no vendor will do this for you, because it is not in any single vendor's interest. The same person existing in two accounts is Google's problem only if Google cares about you leaving, and it does not.
What you can do about it
There are three honest options, and they are not equally good.
Pick one account as your address book and treat the rest as read-only. Put new contacts there, and let the others drift. This is free, it works today, and it is what a lot of people end up doing by accident. The cost is real: you are now maintaining discipline by hand, and every time you save someone from the wrong mailbox you are back to square one.
Bridge two accounts with a tool built for exactly that pairing. If you live in Outlook desktop and one other account, there are mature tools — gSyncit, Outlook CalDav Synchronizer, Sync2 — that copy contacts between two specific sources. They are good at that job. They are also desktop-only or one-directional, they need babysitting, and none of them reconcile the same person appearing three times rather than twice.
Use a reconciler: something that reads all your accounts, finds the same person in more than one, and writes the resolved record back. This is the option that actually solves it, and it is the reason this site exists. It is also the option that asks the most trust, which is a fair thing to be careful about.
If you are in option 3, the thing to look at is not the feature list. It is what happens when it is wrong. You want to see the matches before they are written, you want to choose per field rather than accept a whole merged record, you want to be able to say "these two are not the same person" and never be asked again, and you want to be able to put your address book back the way it was.
What to look for in a reconciler
Whatever you end up using, these are the questions that separate a tool that works from one that makes things worse:
- Can I see what it thinks matches, before it writes? "We find the duplicates. You make the call."
- Can I merge field by field? Three phone numbers is a correct answer to "which number survives?". Picking one is a data loss.
- Can I undo it? Not "delete the duplicate" — undo the merge you approved, back to a point in time, across every account.
- Can I start read-only, and does read-only mean read-only?
- Can I get my contacts out? As vCard, whenever I want, without asking anyone.
- What is the encryption, precisely? A key unique to my account is a different claim from end-to-end encryption, and you should be able to tell which one you are getting.
The short version
The same person is in four address books because each ecosystem syncs only to itself, and because no company benefits from reconciling a competitor's. You cannot merge them from inside Google, Microsoft or Apple. Someone outside has to do it, which is why the question worth asking is not "what does it sync" but "what happens when it gets it wrong".
If you want to see what is actually scattered across your accounts before deciding anything, the features page is the honest summary of how this works.