TL;DR
- Deleting a duplicate can also remove its activity, associations and attribution.
- Merging moves each duplicate's history onto one surviving record.
- Deleting makes sense for junk, test and spam records with nothing worth keeping.
- If a record's value is unclear, merging is the safer choice.
- Dedupely merges duplicates and keeps their activities and associations on the surviving record.
When people search for how to "remove duplicates" from a CRM, they usually mean one of two things. Some want the extra records gone. Others want one clean record per customer, with nothing lost.
Deleting and merging both reduce the number of records, so they can look like two routes to the same result. They aren't. A deleted record takes its emails, calls, deals and source with it, while a merge moves them to the record you keep.
In this post, you'll see what each option does to your data and when deleting is the right call. You'll also get a simple rule for each case, plus the checks to run before you delete anything.
What deleting a duplicate removes
A duplicate record is rarely empty. Even a thin one can carry pieces of a customer's story that exist nowhere else.
Activity history
Calls, emails, notes, tasks and meetings are often logged on whichever record a rep found first. If that record is deleted, its activity can go with it, and the next rep starts without context.
Associations
A duplicate contact can be the one linked to an open deal, a support ticket or a company. Deleting it can leave the deal without a contact, or the ticket without a customer.
Attribution and source
The first record for a person often holds the original source: the campaign, form or event that brought them in. If you delete the older duplicate, reports can credit the wrong channel.
Preferences and consent
One duplicate may hold an email opt-out or a consent status that the other lacks. Deleting the record that holds it can lead to emailing someone who asked you to stop.
Restoring a deleted record doesn't always bring everything back. In one CRM, deleted records can be restored for up to 90 days, though some associated data is lost when a contact is restored. In another, deleted records stay in a Recycle Bin for 15 days.
As of October 2026, from HubSpot's knowledge base: Restore deleted records, and Salesforce Help: Recycle Bin.
What merging keeps
A merge combines the duplicates into one surviving record. Depending on the CRM and the tool, the activity, associations and history of each duplicate move to that record.
The decisions in a merge are which record survives and which value wins for each field. Our guide on how to merge CRM records without losing data covers those choices.
Merging still deserves care. Many CRM merges can't be undone, and two records that only look alike shouldn't be merged at all.
What counts as a duplicate is case by case: what one team considers a duplicate, another may not. Our post on related records that look like duplicates covers the common exceptions.
When deleting is the right call
Some records have nothing worth keeping. Merging them only moves junk onto a good record.
Test records
Records created to test a form, an import or an integration, like test@test.com or "John Doe," usually belong in the trash. Check first that nothing real was attached to them by mistake.
Spam and bot submissions
Form spam creates contacts with nonsense names, fake emails or links in their fields. These aren't duplicates of anyone, so merging them makes no sense. Our post on why web forms create duplicate contacts covers how to spot them.
Empty shells
Some records hold a name and nothing else: no email, no activity, no associations and no source worth keeping. Deleting one of these loses nothing, though merging it wouldn't hurt either.
A simple rule for each case
Use this as a starting point, then adjust it to how your team defines a duplicate.
| Situation | What to do | Why |
|---|---|---|
| Two records for one person or company, both with activity | Merge | Each record holds part of the history |
| A duplicate linked to deals, tickets or a company | Merge | Deleting it can break those links |
| A duplicate with the original source or campaign | Merge, keeping the source value | Attribution stays with the customer |
| A duplicate holding an opt-out or consent status | Merge, keeping the stricter preference | Avoids emailing someone who opted out |
| Test records and example data | Delete, after checking for real links | Nothing real to keep |
| Spam and bot submissions | Delete | Not a real person |
| Records that only look alike, like branches or family members | Neither: keep both | They aren't duplicates |
| You can't tell what a record holds | Review first; merge only after confirming identity and contents | An uncertain match can combine different people, and many merges cannot be undone |
Why deleted duplicates can come back
Deleting a duplicate doesn't change what created it. If a form, import or integration made the record, the next submission or sync can create it again.
A merged record often catches those returns better. If the surviving record keeps the emails a tool matches on, the tool can find it. Then it updates that record instead of creating a new one.
So whichever you choose, look at where the duplicates came from. Our post on deduplication across imports, migrations and syncs covers the usual sources.
Checks before you delete anything
- Look at what's attached: activity, deals, tickets, company links and notes.
- Check the source fields: the first record for a person often holds the original campaign or form.
- Check preferences: opt-outs and consent status must survive on some record.
- Export first: keep the records' original values before a bulk delete, as you would before a large merge.
- Know your restore window: find out how long your CRM keeps deleted records and what a restore brings back.
How Dedupely merges duplicates without losing their history
Dedupely lets you choose surviving values and preview each merge. Check which activities and associations your CRM connector preserves, and retain an export before a large cleanup. Review held-back placeholder matches and uncertain identities before making changes; a merge is not a substitute for that review.
Merge what has history, delete what doesn't
Deleting and merging both shrink your CRM, but only merging keeps what each duplicate knew about the customer. Activity, associations, attribution and preferences stay on one record instead of disappearing.
Deleting still has its place for test records, spam and empty shells. When you're unsure what a record holds, merging is the safer default, because a merged record keeps every option open.
Frequently asked questions
Should I delete or merge duplicate contacts?
Merge duplicates that have activity, associations, a source or a preference worth keeping. Merging moves that history to one surviving record. Delete only records with nothing to keep, like test records, spam submissions or empty shells, and check what's attached to them before you delete.
What happens when you delete a duplicate record in a CRM?
The record and what's attached to it can be lost: activity, links to deals or tickets, the original source and any opt-out it held. Many CRMs keep deleted records for a limited time, but a restore doesn't always bring every association back.
How do I remove duplicates from my CRM without losing data?
Merge them instead of deleting them. Start with the obvious duplicates, such as records with the same email, and decide which record survives and which values win. Keep an export of the original values before a large merge, since many CRM merges can't be undone.
Does merging duplicates reduce my CRM contact count?
Yes. A merge leaves one record where there were two or more, so the count drops the same way it would with deleting. The difference is that the surviving record keeps the activity and associations of the records merged into it.
Can deleted duplicates come back?
Yes, if the source that created them is still running. A form, import or integration can create the same record again on the next submission or sync. Look at where duplicates come from, and make sure the surviving record holds the emails and phone numbers tools match on.
Or sign up with Google
