Almost nothing in your address book was typed by anybody. It accumulated. An address got saved automatically the first time you wrote to someone. A phone kept a copy of its own. An import in 2019 was handed the wrong instruction. A client started writing from home in March. So the job in front of you is a series of decisions about which records are allowed to become one record. It’s worth being careful with, because the tools that do the collapsing have unusually poor reverse gears.
- Duplicate is three different situations wearing one word. One of the three is safe to merge on sight.
- Google suggests merges and offers to accept all of them in one click. The newer Outlook hides duplicates rather than combining them, and classic Outlook leaves both jobs to you.
- Google’s undo for contacts rolls the whole address book back to a moment in time. Its own page says the contacts you added since that moment go with it.
- The dead address in your To line usually comes from somewhere other than your address book. Microsoft documents a separate list that refills itself from your sent mail.
- Working out who is who is one job. Rewriting the address book is another. A tool can do the first and leave the second alone, and that difference is most of this page.
Where the three of them came from
Nobody sat down and made these. Four ordinary mechanisms did. Knowing which one produced a given pair tells you what to do about it.
Your provider saves people you write to, whether or not you asked. Google puts it plainly. “If you email someone but you haven’t added them as a contact, Google Contacts automatically saves their email address in your ‘Other contacts’ group”, and “Their email address will show up the next time you email them” (Google Contacts Help, checked September 6, 2026). More broadly, “People you’ve interacted with in Google services are automatically saved to ‘Other contacts’” (Google Account Help, checked September 6, 2026). A large share of what you’re about to sort through was written by the act of sending mail. That’s why so much of it is half a name and an address.
Your phone kept its own copy. Some of what you see on a handset stayed on the handset. Google says “Some contacts on your phone or tablet may not be saved as Google contacts”. Those “can only be managed on that device”. And “Changes you make to these contacts don’t sync across Google services or to other signed-in devices” (Google Contacts Help, checked September 6, 2026). One copy syncs, one copy stays put, and both show the same face. That’s a duplicate factory, and it runs for years before anybody notices.
An import was given an instruction somebody has forgotten. This is the big one, and it was a single dialog box. Microsoft’s contacts import offers three ways to handle a name that exists on both sides. Replace duplicates with items imported, where “If a contact is already in Outlook and your contacts file, Outlook discards the info it has for that contact and uses the info from your contacts file.” Do not import duplicate items, where “Outlook keeps the info it has for that contact and discards the info from your contacts file.” And allow duplicates to be created, where “Outlook creates duplicate contacts, one with the original Outlook info and one with the info imported from your contacts file” (Microsoft Support, checked September 6, 2026).
Look at what the person in 2019 was choosing between. Two of those options throw information away on the spot, in bulk, and out of sight. The third keeps everything and defers the problem. They picked the careful one. Your duplicates are the interest on a good decision. Hold that in mind before you go at the list with a broom.
And people have more than one address. That one is just life. A client has a work address, a personal one, and a phone that sends from a third. That’s one person with three genuine routes to them, and every one of those routes still delivers. This is the case that all the automatic machinery leaves alone, and the rest of this page is mostly about it.
All four of those happen at the account, whatever app you read mail in, and changing apps leaves them exactly as they are. The address book sits on the account rather than inside a program, which the first part of this series sets out along with what else survives a change of client.
What the mess is actually costing you
Worth pricing before you spend a Saturday. For some people the honest answer is nothing.
You write to the address they stopped using. The message arrives, because old addresses usually still exist and still accept mail. It lands somewhere nobody reads. You find out when the client calls to ask why you never replied, and the record on your side shows you replied.
Anything you mark on a person only holds for the record you marked. This is the expensive one for a small firm, and the quietest. The flag saying this person is never to be missed sits on one of three records. Mail from the other two arrives unflagged. Those two are usually the ones that matter. They’re the addresses a person writes from when they’re away from their desk and something has gone wrong.
Their history looks like a third of itself. Ask what you’ve said to somebody over two years, and a split identity gives you one of the three answers. It arrives looking like all of it. An answer that looks whole is worse than one that looks short, because you act on it.
If those three have cost you nothing you can name, keep your weekend. A full pass over four thousand contacts can wait. The part worth doing is the twenty or thirty people whose mail actually decides your week. Doing only those is a complete answer, and you’re finished when they’re done.
Three situations wearing one word
Sort your duplicates into these before touching anything. They need opposite treatment, and only the first is safe on autopilot.
Two records, same person, the same details on both. Genuinely redundant, usually the product of an import or a phone. One of them is doing no work. Collapsing these is free.
One person, several addresses. Each address is real. Each one delivers. One of them may be the only way to reach that person next year. These should become one person, and the merge has to keep every address rather than choose a winner. A merge that picks the best-looking address and drops the others has quietly deleted a route to a client.
Two people who look like one. A father and a son on the family account. Two people with the same first name at the same firm. A person and the shared inbox they answer from, which is an address rather than a person. Leave these as two. The mistake is easy to avoid, and what makes it dangerous is that it’s invisible afterward. A wrongly merged record looks exactly as settled and confident as the correct ones next to it. It goes on quietly attaching one person’s mail to the other’s history until something forces you to look.
That asymmetry is what you run this whole job on. A merge you skipped leaves you with two records, which is where you already were. A merge you should have skipped leaves you with one record that’s wrong and looks right. The second costs far more than the first, so spend your caution there.
What Google and Microsoft do on their own
Both providers ship something for this. The two things work differently, and the difference is worth understanding before you use either.
Google offers a suggestion list. “If you have duplicate listings for the same person in Google Contacts, you can merge them”, through a Merge and fix view. The bulk option is stated in Google’s own words. “To accept all duplicate contact suggestions, click Merge all” (Google Contacts Help, checked September 6, 2026). One limit shapes how you plan. “You can’t merge contacts that are saved in different Google Accounts” (same page, checked September 6, 2026). If your working life is split across a personal account and a firm account, that’s two jobs, and each one stops at its own account.
Microsoft’s newer products handle this on their own, and the verb is the interesting part. Its page on the subject explains where duplicates come from. “If you’ve imported contacts from multiple sources, such as an external source like iCloud or Gmail, or inherited someone else’s contact list”. Then it describes the handling. “With new Outlook, your contact list is continuously cleaned up and duplicates are automatically hidden after searching for exact and proper subset duplicates”. The same sentence is given for Outlook on the web. Classic Outlook is the exception. “With classic Outlook you’ll get a choice whether to create a new contact record (a duplicate) or merge the duplicate contacts. Classic Outlook doesn’t have an automated process to hide or remove duplicates” (Microsoft Support, checked September 6, 2026).
The word is hidden. Both records stay where they were, whole, and a record that is an exact copy of another, or wholly contained within it, simply stops being shown to you. That’s the conservative version of the same operation, and it comes with one consequence worth predicting. Hiding reaches the pairs where one record holds everything the other holds. Your client with a work address and a personal one sits outside that. So does the father and the son.
So both companies stop in exactly the same place, and they stop there for a good reason. Deciding that Bob Chen and Robert Chen are one man takes something that lives outside both records. What the automatic pass takes off your hands is every pair that was never a judgment. What it leaves you is every pair that was.
The undo is a time machine rather than an unmerge
Read this section before you click anything. It’s also the reason this page sits inside a series about switching email apps rather than in a list of tips.
Google’s merge page says “You can separate a contact that you merged”, and sends you to its instructions for undoing changes to contacts. Read those instructions and you find out what the separation actually is. “You can undo all the changes you made to your contacts during the past 30 days, all at once”. One warning comes attached, and it decides everything. “When you restore contacts to a certain time, such as one week ago, any contacts added after that time won’t show up” (Google Contacts Help, checked September 6, 2026).
There is no unmerge. What there is is a rollback of your entire address book to a moment, and it takes everything else with it. The twelve correct merges you made in the same sitting. The edits you made in the weeks since. Every person you’ve met since that moment. It’s a genuine safety net and a blunt one, and it’s blunt in two separate ways.
It’s all or nothing. The one merge you regret comes back only by returning the whole list to a time before it. The price of fixing one mistake is everything correct that happened afterward.
It has a horizon of thirty days, and bad merges usually surface later than that. You notice a wrong merge in March. A message from one of the two people lands filed under the other’s name, the history looks wrong, and you can’t work out why. By then the instrument has expired.
The deletion path has the same shape and the same clock. Contacts you delete “are moved to Trash, where they’ll stay for 30 days before they’re deleted permanently”. After that, “Contacts deleted permanently from your Trash cannot be recovered” (same page, checked September 6, 2026).
Set that beside Microsoft’s choice to hide rather than combine, and the design reasoning shows. Hiding leaves both records in place, whole. If the guess was wrong, the cost is that you saw one entry instead of two for a while.
There’s a general point in this worth carrying out of the series. A label written into your mailbox by another app is a low-stakes thing, and the previous part spends its length on why. A label goes on, a label comes off, and the message underneath stays as it was either way. A merge is a different kind of write. It’s the one common operation in this whole area that consumes what it acts on.
An order that makes this cheap to get wrong
Six things, and the first one is most of the value.
- Export the list to a file before you touch anything. Both providers will hand you your contacts as a file you can keep on a disk you own, and it takes about five minutes. That file is the one rollback in this entire subject with no clock on it, and it sits outside the account you’re about to edit. Everything else on this list gets easier once it exists.
- Do the work on the account, not on a handset. A phone’s own address book holds records that live only there. Changes you make to them stay on that phone. Fixing the copy that one device can see is the most common way to spend an evening on this and have nothing to show for it.
- Take the automatic pass, then read the rest yourself. Google’s suggestions and Microsoft’s hiding both earn their keep on the exact and near-exact pairs. Merge all is a reasonable click on forty suggestions you’ve scrolled through and recognized. On nine hundred it hands the decision to a name-matching rule, once, in bulk, against an undo that’s all or nothing.
- Merge the ones you’d bet money on and leave the rest alone. Reaching the bottom of the list wins you nothing. Two records for one person costs you very little. One record holding two people costs you a phone call you’d rather not make.
- Do it in one sitting and write the date down. The rollback is a single point in time covering everything. Spread a cleanup over four weekends, and undoing the first weekend erases the fourth. One session, one date, one thing to return to.
- Be careful what you grant write access to. An application whose purpose is deduplicating contacts needs permission to rewrite your whole address book. Its mistakes land in the same store, with the same thirty-day, all-or-nothing reverse. Use one if it helps you. Take the export in step one first, and read what the permission screen names before you agree to it, which is the same discipline as connecting anything else to the account.
All of that is easy and all of it is boring, which is the usual signature of the parts that save you something.
Why the dead address still comes up first
Here’s the complaint that actually sends people looking for this page. You type three letters, and the client’s 2019 address appears at the top of the suggestions, above the one they’ve used every day since. Cleaning your contacts leaves that exactly where it is.
Something else is answering. Microsoft names it. “The AutoComplete list, also known as the nickname cache, is generated automatically when you send email messages from Outlook. The list contains SMTP addresses, LegacyExchangeDN entries, and display names for people you sent mail to previously” (Microsoft Learn, checked September 6, 2026). It’s a record of what you’ve sent, held apart from your contacts. Clearing an entry out of it stays inside that list too. Removing one “prevents the name entry from appearing in the AutoComplete list again but doesn’t remove it from your account” (same page, checked September 6, 2026).
Two further details on that page explain most of the frustration people carry about this. The list refills itself. “If you send a contact a new email after you remove their name from the AutoComplete list, their information will be restored to the list” (same page, checked September 6, 2026). And there can be more than one of them, disagreeing, because “The AutoComplete list for Outlook is specific to Outlook. It isn’t shared with Outlook on the web, which maintains its own AutoComplete list” (same page, checked September 6, 2026). Google’s equivalent is the automatic saving described at the top of this page, where writing to an address is itself the thing that files it and brings it back next time.
So the suggestion list is a history of your own behavior rather than a statement about who anyone is. It rebuilds from that history however carefully you curate the address book beside it. That sets a real bar for any product claiming to help here. Putting the right address in front of you at the moment you need it means working out who the person is, rather than replaying what you typed in 2019.
What Point does with the three of them
Point authorizes against the Google or Microsoft account holding your mail, and the people in it arrive already resolved, with the duplicates merged on the way in. The three records you’ve been reading this page about are one name on one screen. That’s how it looks on the first afternoon, rather than at the end of a project.
The part worth being precise about is where that merging happens. The previous part inventories the four things a connected app writes into a Gmail or Microsoft 365 mailbox. A label or category on a triaged message. The filing when a thread is put away. The reply when you send one. And the event when a meeting is agreed. That’s the whole list, and an edit to your contacts sits outside it. Your Google Contacts and your Outlook People list hold what they held before the connection, duplicates and all.
That’s a deliberate choice, and the four sections above are the whole of the reason for it. A merge written into the address book is the one operation in this subject that resists being cleanly taken back. So the resolution lives in Point’s own view of who you deal with, and the store it was read from is left as it was. A wrong resolution is a wrong view. You correct the view in place, and your address book stays where it is, thirty-day rollback untouched.
What that buys you shows up in two ordinary places. The mark you put on someone goes on the person. It holds across every address they write from, including the one they haven’t used yet. Marking the people who matter is the half hour where that list gets made, and VIP mail that never gets buried is what the mark does to what you see afterward. And a conversation that starts as an email and gets answered somewhere else stays one conversation, for the same underlying reason. There’s one person for it to belong to.
Three limits belong in the same breath.
A resolved view leaves your address book as it found it. If what you need is a tidy export to hand to a CRM, a bookkeeper or whoever is setting up your next system, that’s a cleanup in Google Contacts or Outlook, and you do it there. The two jobs are easy to confuse and worth separating before you start, because only one of them has the thirty-day problem in it.
A resolution can be wrong. Two people at one firm with the same first name are as hard a case here as anywhere else, and you’ll find out the way everybody finds out, with a message sitting under a name you didn’t expect.
What Point takes on by itself is a setting you hold. There’s one for each sort of work, three positions on it, and the cautious middle one holding everywhere until you move it. The autonomy dial is what each position permits and where it stops. The whole of what there is to hand over is on the benefits page.
The list you did not edit
So the result of all this is a slightly odd one, and it’s the shape of the whole series in miniature.
Whatever your address book looks like when you’re finished, it looks that way because you made it look that way. The connection left it as it found it. The version where one client is one person rather than three is a view built on top. The record underneath is the record you’ve always had. It sits on the account your provider runs, exactly as portable and exactly as messy as it was on Monday.
That’s the safest answer available to a job whose only undo is a blunt one. Read from a slightly different angle, it’s also a bill you’ve yet to be shown. The useful version of your contact list is over here. Your actual contact list is over there. Six parts of this series have argued that everything stayed where it was, and this is the part where that stops being reassurance and starts being a question with a number attached.
Which is the last thing left to settle, and the one nobody asks before they sign up. On the morning you decide to stop, what exactly is yours to walk out with.