# Same name, different address: how to keep records apart > Records with the same name but different addresses can be two people or two locations. How to decide, and how to keep them out of your merges. - URL: https://dedupe.ly/blog/duplicates/same-name-different-address-duplicates - Section: blog - Published: 2026-11-03 - Site index: https://dedupe.ly/llms.txt - Any page: append `.md` to its URL for this plain-text form --- Skip to content [New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication) [Blog](https://dedupe.ly/blog) [Duplicates](https://dedupe.ly/blog/duplicates) ## Same name, different address: how to keep records apart By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated November 3, 2026 # min read TL;DR - Same name and different address can mean two people, two locations or one person who moved. - For companies, different addresses often mean separate branches that should stay separate. - For people, a newer address on one record usually means the same person moved. - Keep records with different addresses out of automatic merges and review them. - In Dedupely, an address filter keeps these pairs out of a search you merge from. A name match is one of the most common ways to find duplicates. It's also one of the easiest ways to merge the wrong records. When two records share a name but list different addresses, they can be the same person who moved, two people with the same name, or two branches of the same company. The address is the field that tells you which. This post covers how to read it, how to keep different-address pairs out of your merges and when to merge them anyway. ### What a different address usually means Read the address alongside the record type. - **Two companies, same name, different cities.** Often two branches, two franchise locations or two unrelated businesses with a common name. Many teams keep these separate. - **Two contacts, same name, different cities.** Either two people or one person who moved. The dates and email settle it. - **Same city, slightly different street.** Often the same address written two ways ("Suite 200" vs "Ste. 200"), so probably the same record. - **One address filled in, one blank.** The blank tells you nothing. Decide on other fields. ### When to keep them apart Keep records separate when the address is the only thing that tells them apart and it points to two places that both matter. For companies, that's usually a decision about structure. If each location buys separately, has its own contacts or its own deals, two records reflect how you sell. Merging them puts all of it under one address. [How to keep global accounts straight in your CRM](https://dedupe.ly/blog/crm-organization/global-accounts-regional-offices-subsidiaries) covers how to decide between one record per location and one per company. For people, keep them apart when other fields disagree too: different emails, different phones, different employers. ### When to merge them anyway Merge when the evidence says it's one person or one company that moved. Signs: - The same email or phone on both records. - One record is older and has gone quiet, while the newer one is active. - The old address matches where the company used to be, and the new one where it is now. When you merge, make sure the current address wins, and that its street, city and postal code come from the same record. Mixing the street from one record with the city from the other creates an address that doesn't exist. Example Say a team matches contacts on first and last name, and several pairs have the same name in different states. Adding a filter on the address field, so the search only includes records with a blank address, keeps every pair with a filled-in address out of that merge. The team reviews those pairs on a separate search. ### How to keep different-address pairs out of your merges You have two options, and many teams use both. #### Match on the address too Add the address, or the city and postal code, to the search. Then only records with the same name and the same location pair up. This is the safest search to merge from, but it misses people who moved. #### Filter instead of matching Match on name, and add a filter on the address field so the search only includes records with no address. Records that are missing data still come through, while pairs with two filled-in addresses stay out, so two locations never pair up in that search. Whatever you leave out, review it by hand on a separate search. Those are the pairs most likely to be judgment calls. | Situation | What to do | | --- | --- | | Same name, same address | Merge with confidence | | Same name, one address blank | Merge after checking email or phone | | Same name, different address, same email or phone | Probably one person or company that moved; review, then merge | | Same name, different address, nothing else shared | Keep apart, or review by hand | ### How to keep records with different addresses apart in Dedupely In Dedupely, filters work on any synced field, so you can match on name and filter on the address field to control which pairs appear. A filter's "Applies to" setting lets you require that all, one or more, or only one record in a match meets the condition. A filter can't use "is blank" on a field the search already matches on, so filter on the address only when you aren't matching on it. When you do merge, a suggested Merge Rule can take all address parts from the same record, so the street, city and postal code stay together. Pairs that turn out to be two places can be rejected, and they stay out of future searches. [Find duplicates without merging locations](https://v2.app.dedupe.ly/signup) ### Let the address make the call A shared name gets two records into the same match. The address decides what to do with them. Same address, merge. Different address, look for a shared email or phone before you merge, and keep separate locations separate when they sell separately. Build one strict search to merge from and one looser search to review, and the different-address pairs never merge without someone looking. ### Frequently asked questions #### Should I merge contacts with the same name but different addresses? Only if another field, like email or phone, shows they're the same person. Without that, they're as likely to be two people as one person who moved. #### Are two companies with the same name in different cities duplicates? Sometimes. They can be one company that moved, two branches or two unrelated businesses. If each location buys separately, many teams keep one record per location. #### How do I keep different addresses from merging automatically? Either match on the address too, or match on name and filter the search to records with no address. Review the pairs you left out on a separate search. #### What if one record has an address and the other doesn't? A blank address doesn't tell you anything. Decide on email, phone and activity. If those agree, merge and keep the filled-in address. #### How do I keep the right address when I merge? Make the current address win, and take every part of it, street, city, region and postal code, from the same record. Otherwise the merged record can end up with an address that doesn't exist. Behind the article ### Gaby Salinas Marketing Assistant at Dedupely Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start. As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes. [Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns) ### Contact us We’d be happy to help you get this set up. #### Write us a message We probably know the answer to your question already help@dedupe.ly Email copied to your clipboard! [Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler) ### Discover Related Blog Posts Stay updated with our latest articles and insights. - [CRM Organization How to keep global accounts straight in your CRM Global accounts start with a business decision: are regional offices independent customers or one global company? Then match, merge or keep them apart. Gaby Salinas October 29, 2026](https://dedupe.ly/blog/crm-organization/global-accounts-regional-offices-subsidiaries) - [CRM Organization Match CRM customers across branches and locations Clinics, franchises, branches and regional offices often duplicate customers and locations in one CRM. How to decide what's a duplicate and clean it. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/crm-deduplication-multi-location-businesses) - [Team Collaboration How to set up a review process for uncertain matches Uncertain duplicate matches need a clear owner, a split that fits your team and a routine. See how teams set up review before anything merges. Gaby Salinas October 24, 2026](https://dedupe.ly/blog/team-collaboration/review-process-uncertain-duplicate-matches) ### Get started for free 20 free trial merges and as much free support as you need to get your duplicates under control. [Try for free](https://v2.app.dedupe.ly/signup)[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales) [Or sign up with Google](https://v2.app.dedupe.ly/signup/google) Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)