TL;DR
- A merge record shows the original records, the winning values and the merged result.
- Sales, security and leadership often ask about merges weeks or months later.
- Original values support recovery, but do not replace a backup of linked data.
- Merges made by hand or by integrations often leave no record outside the CRM.
- Dedupely records every merge it makes, with original records, winning values and the result.
A merge takes a few seconds. The questions about it can come months later. A rep can't find an account, a report shows fewer customers, or a security reviewer asks who changed customer data.
Without a record of the merge, the answer depends on someone's memory. With one, it takes a minute to see which records went in, which values won and who made the call.
In this post, you'll see who asks about merges, what a useful merge record shows and which merges tend to leave no trace. You'll also see how long to keep the record and how to use it to improve your rules.
What a merge record is
A merge record is a log entry for each merge. It keeps the records that went in, the values that won in each field and the record that came out. It also notes who or what started the merge, and when.
A backup is different: it's a copy of your data taken before a merge. Our guide on backing up your CRM before a large merge covers it. A merge record covers every merge, even the ones nobody backed up for.
Who asks about merges, and why
Different people ask different questions about the same merge. A good record answers all of them. Consultants have one more reason, proving the work to a client, which our post on CRM deduplication for consultants and agencies covers.
Reps and sales managers
Reps notice merges first, because they work the records every day. The usual questions are "Where did this account go?" and "Why is this contact owned by someone else now?"
Ownership questions can turn into commission disputes. Our post on duplicates from a sales manager's point of view shows how fast they escalate. A merge record shows which owner each record had before the merge and which one won.
Leadership and reporting
After a large cleanup, record counts drop and some reports shift. Leadership wants to know whether the drop is the cleanup or something else.
A merge record lets you show the number of merges per object and period. That turns "the numbers changed" into "we merged this many duplicate sets on these dates."
Security and compliance
Security teams treat a merge as a change to customer data. They often ask whether there's a log of who changed what, and whether it can be exported.
Our post on what security teams ask about a deduplication tool covers the wider review. The merge record is the part that shows what happened after the tool was approved.
Recovery
In many CRMs, a merge cannot be undone. HubSpot does not support unmerging and creates a new record ID by default. Accounts in its Primary ID Preservation public beta keep the primary ID instead. Neither behavior replaces keeping the original data and checking the result.
If a merge is wrong, original values help identify what changed and support a recovery plan. Re-entering those fields may not restore record IDs, activities or downstream links. Keep the appropriate backup as well as the merge log.
As of October 2026, from HubSpot's knowledge base: Merge records.
What a useful merge record shows
A record that only says "these IDs were merged" tells you a merge happened. To answer the questions above, it needs more.
| What the record keeps | The question it answers |
|---|---|
| The original records, with all their field values | What did each record look like before the merge? |
| The record ID of each original record | Which record in an old report or spreadsheet does this match? |
| The winning value in each field | Why does this contact have this owner or this phone number? |
| The merged result and a link to it | Where is that record now? |
| Who or what started the merge, and when | Was this a person, an automatic rule or an integration? |
| Which search or criteria found the match | Which rule should we fix if this merge was wrong? |
The last row is often missing. Knowing which criteria found a wrong match is what lets you fix the rule, so the same mistake doesn't repeat.
Merges that often leave no record
Not every merge goes through the same place. Some leave little or nothing behind outside the CRM itself.
- Merges made by hand in the CRM: several people merging one pair at a time, each with their own idea of a duplicate.
- Integrations: a connected tool that merges records may keep its own log, or none, outside the CRM.
- Custom scripts: a script that merges records may log it somewhere only its builder knows.
Check the native trail before choosing a separate log. HubSpot's Merged record IDs property shows the merged IDs; its Details view shows who performed the merge and when. For merges made in the duplicate-management tool, HubSpot also offers an export of pre-merge property values and timestamps for up to 90 days. Check whether that scope and retention cover your team's needs.
As of October 2026, from HubSpot's knowledge base: Merge records.
The fewer places merges happen, the easier the trail is to follow. Decide where merges are made, and who can make them.
How long to keep it and who should see it
Keep the record for as long as questions about merges can come up. A practical minimum is your reporting, commission and audit periods.
Export a copy after each large cleanup and store it where your team keeps other audit files. Name it with the date and the object, so it's easy to find later.
Limit who can merge, and let a wider group read the record. Reps and managers can then check a merge themselves before raising it with the CRM owner.
Use the record to improve your rules
A merge record is also feedback. Once a month, open a sample of recent merges and ask whether you'd have made each one by hand.
If several wrong merges come from the same criteria, tighten that search or send its matches to review. What counts as a duplicate is case by case, and the record shows where your team's definition and your rules disagree.
When you're certain two records aren't duplicates, reject the match so it doesn't come back. Reject only when you're certain, because a rejected match stays out of your searches.
How Dedupely keeps a record of every merge
Dedupely records every merge it makes: the original records, the winning values, the result and a link to it in your CRM. You can filter that history by object, search term and date, and export it as a CSV with the original values. Admins also get a log of who merged what and when, including background merges.
Every merge should be explainable
A merge changes records many people depend on, and questions about it rarely come right away. A record of every merge lets you answer reps, leadership and security reviewers with facts instead of memory.
Keep the original records, the winning values, the result, and who or what made each merge. Then use the same record to check your rules, so each cleanup leaves fewer questions than the last.
Frequently asked questions
What is a merge history in a CRM?
A merge history is a log of every merge made in the CRM. For each merge, it keeps the original records and their values, the value that won in each field and the merged result. A useful history also shows who or what started the merge, when it ran and which criteria found the match.
Can you see who merged two records in a CRM?
It depends on the CRM and merge method. HubSpot shows merged IDs, the merge actor and timestamp, and offers up to 90 days of pre-merge values for merges made in the duplicate-management tool via export. Check the available fields, retention and coverage. A separate log can help when you need a consistent trail across merge methods.
Can you undo a merge in a CRM?
Many CRMs, including HubSpot, do not support unmerging. Use the original values, backup and merge log to plan recovery with the CRM owner or vendor. Recreating fields alone may not restore the original IDs, activities or integrations. Check recovery limits before a bulk merge.
How long should you keep a record of CRM merges?
As long as questions about merges can come up. A practical minimum is your reporting, commission and audit periods. Export a copy after each large cleanup, name it with the date and object, and store it with your other audit files.
What should a CRM merge log include?
The original records with their IDs and field values, the winning value in each field, and the merged result with a link to it. It should also show who or what started each merge, when it ran and which criteria found the match. That last detail tells you which rule to fix.
Or sign up with Google
HubSpot user 
