Ticket Merger

How to Merge Duplicate Records, Platform by Platform

How to merge duplicate records depends on the platform, but the shape never changes: every CRM dedupes on one key, usually email, so duplicates arrive the moment somebody uses a second address.

Start free trial

How to merge duplicate records, by platform

The real steps, what survives the merge, and whether you can undo it.

Merge duplicates in HubSpotcontacts, companies, dealsMerge contacts in HubSpotMerge companies in HubSpotMerge duplicates in Salesforceduplicate rulesMerge duplicates in PipedriveMerge duplicates in Zoho CRMfind and mergeMerge duplicates in Dynamics 365detection jobsMerge duplicates in MarketoMerge users in ZendeskMerge requesters in Freshservice

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 can't 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.

FAQ

How to merge duplicate records: common questions

What does CRM deduplication involve beyond merging?

Merging is the last step. CRM deduplication is really about the match key: pick email for people and domain for companies, enforce it at every entry point, then merge duplicate contacts that slipped through before anybody built a report on them.

How do you merge duplicate records without losing data?

Pick the survivor deliberately, because its field values usually win. Export both records first, check which one carries the activity history you need, then merge and verify the associations landed.

Which CRMs can merge duplicate records in bulk?

Salesforce and Zoho CRM have real bulk tooling. HubSpot, Pipedrive and Dynamics merge two records at a time, so volume means the API or a dedupe app from their marketplace.

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.

Keep reading

HubSpot Deduplication: A Practical Guide
How HubSpot deduplication works on its own, where it stops, and a working process for cleaning contacts, companies, deals and tickets without breaking reporting.
Duplicate Ticket Detection for Support Teams
Duplicate tickets inflate your volume, split your replies and hide SLA breaches. Here's how automatic duplicate ticket detection finds them the moment they arrive.
How to Merge Tickets in Any Helpdesk
How to merge tickets in Zendesk, Freshdesk, HubSpot, Zoho Desk, ConnectWise, Help Scout, ServiceNow, Jira and more, with the real limits of each platform.