Merging Duplicate Records, Platform by Platform

Every CRM dedupes on one key, usually email, and every CRM therefore accumulates duplicates the moment somebody uses a second address. Here is how to clear them.

The pattern every platform shares

Three rules hold almost everywhere, whatever the product calls things.

Deduplication happens on one key. Usually email for people and domain for companies. Anything with a different key is a new record, which is why your duplicates are the awkward ones rather than the obvious ones.
Merges are permanent. HubSpot, Salesforce, Pipedrive and Zoho all say so plainly. Dynamics is the exception, deactivating rather than deleting.
The primary record wins. Its values survive and blanks are filled from the other, so choosing the primary matters more than the order you opened them in.

Which means the discipline is identical everywhere: export before a bulk cleanup, fix the source that created the duplicates, then work the list.

Why this matters for support

A duplicate contact is not just untidy data. It splits one customer into two, and everything downstream splits with them.

Their support history lives in two places, so an agent answering a ticket cannot see the conversation from last month. Emails from the second address open tickets that never associate with the first. Reporting counts one customer as two.

So duplicate records and duplicate tickets are the same problem at two levels. Cleaning the records makes ticket deduplication sharper, and merging tickets stops the split causing damage today.

Fix the ticket half automatically

Cleaning CRM records is a project. Duplicate tickets arrive daily, and Ticket Merger merges them as they land on Zendesk and Freshdesk.

Start free trial

14-day free trial. No credit card required.