Clean duplicate contacts before a coaching review by detecting the match, verifying it, and merging the split buyer history onto one record.
Key takeaways for how to clean duplicate contacts in crm for sales coaching
- Detection rule setup: Microsoft notes that if you want the rule to consider only active records while detecting duplicates, select the Exclude inactive matching records check box, according to Microsoft.
- Preview verification: Close states that this first (preview) step downloads a CSV of matched leads/opportunities and does not modify any records, allowing you to verify matches before any deletion or merge is requested, according to Close.
- Permission requirements: HubSpot specifies that data quality tools access and Edit permissions set to All Contacts or All companies or Super Admin permissions are required to use the duplicates manager tool, according to HubSpot.
- Post-merge audit: HubSpot explains that you can review merged record details in bulk by exporting them, with data up to 90 days ago, according to HubSpot.
- Merge history: HubSpot states that for all objects, you can use the Merged [record] IDs property to view previously merged records, according to HubSpot.
Why clean data matters for sales coaching accuracy
Duplicate rows can creep into your data when you or others enter data manually or import data in bulk, according to Microsoft.
When you run coaching call reviews and 1:1s, you rely on the buyer history attached to a specific contact record. If that history is split across two duplicate rows, the conversation context you reference may be incomplete or attached to the wrong entity. This accumulation happens quietly over time. A rep might type a name slightly differently during a quick note entry, or a bulk import might fail to match existing records due to formatting differences.
For a front-line manager, this fragmentation creates a specific risk during coaching. When you pull up a call recording or a timestamped note to discuss with a rep, you need the full context of that buyer’s journey. If the system treats two entries as separate people, the activity log on the primary record will be missing the interactions logged on the duplicate. You end up coaching from a partial view of the buyer relationship.
How duplicate detection works across major crms
Different platforms use distinct mechanisms to flag potential duplicates, and understanding these specific behaviors is critical before you begin cleaning your data. Microsoft explains that to determine whether a record is a potential duplicate, Power Apps uses duplicate detection rules according to Microsoft. This process relies on a specific technical comparison rather than simple visual matching. Microsoft states that duplicate detection works by comparing generated match codes of existing records with each new record being created according to Microsoft. This match code approach means the system evaluates data integrity at the moment of creation, requiring you to understand how your specific rules generate these codes to interpret the results correctly.
HubSpot approaches the problem with a different cadence and focus. HubSpot notes that it automatically compares record property values daily to surface potential duplicates, so your team works from accurate, up-to-date data according to HubSpot. This daily comparison cycle means that duplicates are found by a daily comparison against existing property values. HubSpot warns that a warning will appear if your rule matches more than 10% of all records in your account and the average group size is greater than three according to HubSpot.
When setting up your detection rules, pay close attention to these threshold warnings. If your rule triggers this specific alert, it indicates that your matching criteria are too broad for your current data volume. You should adjust your rule parameters to narrow the scope before proceeding with any merge actions. Do not assume that the match code logic used by one platform applies to another; each system has its own specific method for identifying potential duplicates. Your goal is to configure these rules so they surface true duplicates without overwhelming your team with false positives. Review the specific documentation for your platform to understand how its detection engine evaluates your data.
A filled reference table of detection, import, and merge behaviors
The following table lists detection, import, and merge behaviors documented by three publishers. Each row ties the behavior to the named source and includes the supporting wording.
| Publisher | Detection, import, or merge behavior | Source Quote |
|---|---|---|
| Close | Users choose how duplicates are resolved by selecting a merge rule. | "Choose your merge rule: Decide how you’d like duplicates resolved (see the options below)." |
| Close | A preview step downloads a CSV of matched records without modifying any data, allowing verification before deletion or merge. | "This first (preview) step downloads a CSV of matched leads/opportunities and does not modify any records, allowing you to verify matches before any deletion or merge is requested." |
| Pipedrive | The system adds new phone numbers to existing records and updates organization names during import to avoid creating duplicate entries. | "Instead, it adds the new Phone number to row 1’s record, as well as updates row 3's organization - name with “The Wall”." |
| Pipedrive | The system recognizes identical person and organization names in subsequent rows and prevents creating duplicate records. | "It then realizes the person - name and organization - name are the same in row 2 as they were in row 1 and therefore does not create 2 Jon Snows." |
| HubSpot | You can review merged record details in bulk by exporting them, with data available up to 90 days ago. | Review merged record details in bulk by exporting them, with data up to 90 days ago. |
| HubSpot | Users can view previously merged records for all objects using the Merged [record] IDs property. | "For all objects, you can use the Merged [record] IDs property to view previously merged records." |
According to Close, the platform provides a mechanism to decide how duplicates are resolved. According to Close, the initial step downloads a CSV of matched leads and opportunities without modifying records. According to Pipedrive, the system adds new phone numbers to existing records and updates organization names. According to Pipedrive, the system prevents creating duplicate records when person and organization names match. According to HubSpot, merged record details can be reviewed in bulk by exporting them with data up to 90 days ago. According to HubSpot, the Merged [record] IDs property allows viewing previously merged records for all objects.
Step by step process to verify and merge records
Follow these six checks to verify and merge records safely.
1. Detection rule setup Configure your detection rules to target the correct data types. Microsoft Dataverse provides duplicate detection for active rows, such as accounts and contacts, according to Microsoft. When you create a new record, the duplicate detection rule discovers if you already have a similar row and displays a dialog box, according to Microsoft.
2. Active record filter Restrict your search scope to relevant data. If you want the rule to consider only active records while detecting duplicates, select the Exclude inactive matching records check box, according to Microsoft. You should also select this check box if your duplicate detection rule criteria are based on a status field, according to Microsoft.
3. Preview verification Review potential matches before taking action. In HubSpot, you can learn how to review duplicate records and take action on duplicate pairs, according to HubSpot.
4. Merge conflict resolution Define how conflicting data is handled. In HubSpot, you can set up to 20 property overrides for each merge rule, according to HubSpot.
5. Permission requirements Verify that your team has the necessary access rights. Data quality tools access and Edit permissions set to All Contacts or All companies or Super Admin permissions are required to use the duplicates manager tool, according to HubSpot.
6. Post merge audit Track the results of your merges. In HubSpot, you can export merge history to audit your actions, according to HubSpot.
Common pitfalls when merging sales contact data
A major risk in cleaning contact data is assuming that every CRM applies the same merge logic to email and phone fields. Each vendor builds its own rules for how property values combine when two records join. You cannot treat one publisher's behavior as the universal standard for all firms. If you ignore the specific warnings generated by your platform, you may merge records that do not actually belong together.
HubSpot provides a specific guardrail against overly broad matching rules. According to HubSpot, a warning will appear if your rule matches more than 10% of all records in your account and the average group size is greater than three. This threshold signals that your detection criteria are too loose. If you proceed with a merge under these conditions, you risk combining distinct buyers into a single, inaccurate profile.
Always confirm where you can safely execute these actions before starting a bulk cleanup.
Another common mistake is believing that a single support ticket can resolve all data quality issues automatically. Data hygiene is an ongoing operational task, not a one-time fix. While vendor support can help with technical errors, they cannot manually verify every duplicate pair in your database. You must take ownership of the verification process.
Notes after a merge
HubSpot documents that you can review duplicate records, take action on duplicate pairs, manage custom rules, and export merge history, according to HubSpot.
When you finish a merge, note the date and any field conflicts you resolved. This record helps you confirm that your team’s coaching notes reference the correct buyer history.
Illustrative example of two contact rows
Two rows name the same buyer. The first holds three notes and the second holds one email. You keep the first row and place the email on it before the coaching talk.
Export a list of potential duplicate contacts from your crm and manually verify the top matches before initiating any merge.
FAQ: How to clean duplicate contacts in crm for sales coaching
How do I verify matches before deleting duplicate records?
Close provides a preview step that downloads a CSV of matched leads and opportunities without modifying any records, allowing you to verify matches before any deletion or merge is requested, according to Close. This preview ensures you can inspect the data before taking action.
Can I merge records in bulk without manual review?
HubSpot allows reviewing merged record details in bulk by exporting them, with data up to 90 days ago, according to HubSpot. You should verify the exported details to confirm accuracy.
How does import-time duplicate avoidance handle unique phone numbers?
During an import, Pipedrive adds the new phone number to the existing record, according to Pipedrive. Specifically, it adds the new Phone number to row 1’s record. This behavior helps maintain a single record with multiple contact details.
Where can I view the history of previously merged records?
For all objects, you can use the Merged [record] IDs property to view previously merged records, according to HubSpot. This property provides a way to track which records were combined. Use this feature to audit your merge decisions.