# How do I know which duplicate record is the real one? | Dedupely > When a contact exists several times, each record holds part of the history. How to pick the right one today, and how merging puts calls and notes on one. - URL: https://dedupe.ly/blog/which-duplicate-record-is-the-real-one - Section: blog - Published: 2026-10-30 - Site index: https://dedupe.ly/llms.txt - Any page: append `.md` to its URL for this plain-text form --- [Blog](https://dedupe.ly/blog) Duplicates ## How do I know which duplicate record is the real one? By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated October 30, 2026 # min read TL;DR - When a contact exists several times, each record usually holds part of that person's history. - Calls and notes often land on whichever duplicate a rep or tool opened first. - Until duplicates are merged, the record with the open deal and latest activity is safest. - Merging moves activities to one surviving record, except where a CRM's API doesn't allow it. - Dedupely finds duplicate records and merges them into the record you choose to keep. Often, none of them is the whole record. Each duplicate holds part of the person's history, so the call, note or email you need may sit on a record you didn't open. Merging them into one record, with the activity moved over, is what ends the guessing. Until then, you search for a contact and get three results with the same name. One has an old email, one has your last call, and one has the open deal. You pick one, log your work there, and the next rep picks another. In this post, you'll see why activity ends up on the wrong record and why new reps have it hardest. You'll also see how to choose a record today, and how merging fixes it for good. ### What it looks like from the rep's seat People describe the problem in simple words. One business owner searching for a client put it this way: "I see five [of them], I want to see one." The other signs follow from that: - You logged a call yesterday, and today it isn't on the record you opened. - An email you sent shows an empty history on the contact. - A calling or meeting tool logs to one record, and you work from another. - An opportunity sits on one of several records for the same company. - A search for one customer returns more than a hundred records, and nobody knows which one to quote. Example A small business books clients through a scheduling link. An automation is supposed to find the existing contact, but each booking creates a new contact and a new lead instead. When the owner goes to open a deal, there are several records for the same client to choose from. ### Why calls and notes land on the wrong record Every activity in a CRM attaches to one record. When a person exists several times, the history splits across them, and nothing tells you which part is where. #### People log to the record they opened A rep searches by name, clicks the first result and logs the call there. A colleague clicks a different result the next day. Both did their job, and the history is now in two places. #### Tools log to the record they matched Email, calling and meeting tools attach activity by matching an email address or phone number. When two records share that value, a tool may pick one, or create a new record when it finds none. When the records hold different emails, each tool may log to a different one. #### Older records keep older data A person who changed email or phone may have an older record with the outdated value. Tools match the current value, so new activity goes to the newer record. The history from before the change stays behind on the old one. ### Why new reps have it hardest An experienced rep often knows which record is "the one" from memory. A new rep has no memory to go on, only what the CRM shows. So new reps pick by guesswork, often the first search result or the record with the most recent date. When they can't tell, some create a fresh record to be safe, which adds one more duplicate. Others ask a colleague every time, which slows both people down. If you onboard reps into a CRM with duplicates, tell them how to choose a record, as below. It won't fix the duplicates, but it keeps their first weeks of activity in one place. ### How to choose the right record until the duplicates are merged When you can't merge, a consistent choice is better than a random one. These checks, in this order, work for most teams. | Check | Why it helps | | --- | --- | | Search by email or phone, not by name | Names repeat across different people; email and phone are tied to one person more often | | Look for the open deal or opportunity | The record a deal sits on is the one your pipeline and reports read | | Compare the most recent activity | The record your team works today is usually the one with the latest call or email | | Check the owner | An active owner usually means the record is the one in use | | Check the created date | The oldest record often holds the longest history, and other systems may point to it | Whichever record you choose, report the others to your admin. A short list of real duplicates helps them find the source and fix it. Pro tip Don't delete the record you think is wrong. A delete removes its activity along with it, while a merge moves that activity to the record you keep. ### How merging puts the history back together Merging is the fix, because it ends the choice. The duplicates become one record, and their activity moves onto it. #### Activities and associations move to the surviving record A merge moves notes, calls, tasks and associated companies, deals and contacts onto the record you keep. Some CRMs can't move certain activity types through their API, so check what your CRM moves before a large merge. The difference between merging and deleting is covered in [should you merge duplicates or delete them](https://dedupe.ly/blog/merge-or-delete-duplicates). #### Choose which record survives Every merge keeps one record. Common choices are the oldest record, the newest, the most recently updated or the one with the most fields filled in. If other systems point to record IDs, check how your CRM handles them: in some CRMs, the merged record gets a new ID. #### Decide which values win The surviving record also needs the right email, phone, owner and stage. Decide per field which value wins, and make sure a blank field never replaces a filled one. More on those choices in [merging CRM records without losing data](https://dedupe.ly/blog/merge-crm-records-without-losing-data). Customer-facing teams feel this most when a customer's history is split before a renewal. That side is covered in [how duplicates split customer histories in customer success](https://dedupe.ly/blog/duplicates-customer-success). ### How Dedupely puts each person's activity on one record Dedupely Intelligence finds duplicate contacts, companies and leads without any match settings, and its scans run automatically. You choose which record survives, like the oldest or the most complete one, set rules for which value wins and preview each merge. When you merge, activities and associations move to the surviving record, except where your CRM's API doesn't allow them to be moved. [Find the duplicates splitting your activity history](https://v2.app.dedupe.ly/signup) ### One person, one record, one history When reps can't tell which record is the real one, it's usually because each duplicate holds a piece of the history. Every call logged on a different record makes the next choice harder, especially for new reps. A consistent way to choose a record limits the damage until the duplicates are merged. Merging ends it, with the activity moved onto one record and the right values kept. ### Frequently asked questions #### Why does the same contact appear several times in my CRM? Because forms, imports, integrations and reps created new records instead of finding the existing one. Small differences, like a second email address or a phone number in another format, are enough for a new record. Each duplicate then collects its own calls, notes and emails. #### Why are my logged calls missing from a contact? Often because they're on a duplicate of that contact. You or a tool logged them to another record for the same person, usually one with a matching email or phone. Search by email or phone to find the other records, and ask your admin to merge them. #### Which duplicate record should I log activity on? Choose the record with the open deal and the most recent activity, and check that it has an active owner. Search by email or phone rather than name to see every duplicate. Report the others to your admin so they can be merged. #### Does merging duplicates keep the activity history? Usually, yes: a merge moves notes, calls, tasks and associated records onto the record that survives. Some CRMs can't move certain activity types through their API, so check what your CRM moves before merging. Deleting a duplicate removes its activity instead. #### Which record should survive a merge? It depends on your data: many teams keep the oldest record, while others keep the newest or the most complete one. If other systems point to record IDs, check how your CRM handles IDs on a merge first. Whichever record you keep, decide per field which values win, like email, phone and owner. 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. [Team Collaboration How duplicates split customer histories in customer success Duplicate records split a customer's history, so CS teams lose context before calls and renewals. Where they come from and how to merge them safely. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/duplicates-customer-success) [Duplicates Should you merge duplicates or delete them? Merge duplicates that carry history, associations or attribution. Delete only junk, test and spam records. A simple rule for each case. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/merge-or-delete-duplicates) [Duplicates Merge CRM records without losing data Field-level merge rules let you control how each value is kept or replaced during a CRM merge. More accurate merges, fewer reviews, and logic you can scale. Gaby Salinas February 12, 2026](https://dedupe.ly/blog/merge-crm-records-without-losing-data) ### Get started for free 20 free trial merges and as much free support as you need to get your duplicates under control. [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)[Try for free](https://v2.app.dedupe.ly/signup) [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) Skip to content