Blog
CRM Organization

Should you deduplicate or enrich CRM data first?

8
min read
A list of records being checked before enrichment

Table of contents

Talk to sales
Try for free
View as Markdown

TL;DR

  • Merge confirmed duplicates before enrichment; verify uncertain identities before merging.
  • Deduplicating first avoids enriching one customer twice and getting conflicting values on each record.
  • Enriched fields like website domains can reveal duplicates that earlier matching missed.
  • Enrichment tools can create new records for people or companies already in the CRM.
  • Dedupely finds and merges duplicates before and after enrichment, with rules for which value wins.

Enrichment fills the gaps in your CRM records. A tool adds job titles, company sizes, industries, websites and phone numbers, so reps and marketers have more to work with.

Deduplication makes sure each person or company has one record. Both improve your data, and teams planning a data project often ask which one should come first.

The answer is both, in a specific order: deduplicate, enrich, then deduplicate again. In this post, you'll see why duplicates make enrichment less useful and why enrichment reveals and creates new duplicates. You'll also see which values should win when enriched records merge.

What deduplication and enrichment each do

Deduplication

Deduplication finds records that represent the same person or company and merges them into one. What counts as a duplicate is case by case. Each team decides which fields have to match and which values the merged record keeps.

Data enrichment

Enrichment adds data to existing records from an outside source. It usually starts from something the record has, like an email, a name or a website, and looks up more from there.

If missing details prevent you from confirming identity, enrich that limited group first or ask the record owner to verify it. Merge confirmed duplicates before broad enrichment, then run a second search with the added fields.

Both depend on the records being right. Enrichment looks up whatever records you give it, and deduplication can only match on the fields the records contain.

Why deduplicate before you enrich

Enriching first means enriching every duplicate. The problems that causes show up later, when the duplicates finally get merged.

You enrich the same customer more than once

If one person has three records, enrichment looks them up three times. When an enrichment tool charges by record or by credit, duplicates add to the cost without adding information.

Deduplicating first means each lookup goes to a different person or company. The enriched data then sits on the record your team uses.

Duplicates get conflicting values

Enrichment doesn't always return the same answer for each duplicate. One record has a personal email and gets nothing, while another has a work email and gets a full profile. Two records for one company can get different industries or sizes from different lookups.

When those records merge later, you have to decide which enriched value is right. Merging first avoids much of that decision.

Enrichment spreads across the wrong records

Workflows, scores and segments can start running as soon as enriched fields arrive. If those fields land on duplicates, sequences and segments pick up records that should have been merged.

Why deduplicate again after you enrich

The first pass catches the duplicates you can see. Enrichment changes what you can see, so a second pass catches what the first one couldn't.

Enriched fields reveal hidden duplicates

Before enrichment, two company records might share nothing but a similar name. After enrichment, both have the same website domain, and the match becomes obvious.

The same happens with people. Enrichment can add a work email or phone number to a record with only a personal email, linking it to an existing record. Matching on the fields enrichment fills in finds them, and which fields to match on depends on what your records now hold.

Enrichment creates new records

Some enrichment tools add records as well as fields. A tool can add a company from a contact's email domain, or add contacts at a target account. If it doesn't find the record that already exists, it creates a second one.

This can create duplicate companies, as the guide to finding duplicate companies by domain explains.

Enrichment changes how names look

Enrichment can add a company's full legal name, with a suffix like LLC or GmbH. A record typed as "Fernhill" and one enriched as "Fernhill Logistics LLC" no longer match on an exact name. After enrichment, match names while ignoring company suffixes like LLC and GmbH.

The order: deduplicate, enrich, deduplicate again

Step What you do Why
1. Deduplicate Merge the obvious duplicates, usually exact matches on email for people and domain for companies Each record you enrich stands for one person or company
2. Enrich Enrich the merged records, and decide whether enrichment overwrites existing values or only fills blanks New data lands on the record your team uses
3. Deduplicate again Match on the fields enrichment added, like website domain, work email and phone, and review the new matches Catches duplicates the new data reveals or creates

In many setups, enrichment keeps running as new records arrive. Then the second pass becomes a regular check, and how often to deduplicate depends on how many records your sources add.

Which value wins when enriched records merge

Enrichment adds a new question to every merge: should the enriched value or the value your team entered win? The answer depends on the field and on your team.

Fields your team owns

Some fields carry decisions your team made, like owner, lifecycle stage or a custom account tier. Enrichment rarely has a better answer for these, so many teams keep the value already in the CRM.

Fields enrichment knows better

Firmographic fields like industry, company size or headquarters often come from enrichment in the first place. For these, many teams keep the most recent value. Others keep the most complete one.

Fields where blanks matter

A blank shouldn't overwrite a value. If one duplicate was enriched and the other wasn't, the merged record should keep the enriched value.

If you've already enriched your duplicates

Many teams find this out after the fact, and it's fixable. Merge the obvious duplicates now, and decide field by field which enriched values to keep.

Then look at how your enrichment tool finds existing records before it creates new ones. If it matches on a field your records often lack, it can keep creating duplicates. The second pass then becomes part of your routine.

How Dedupely handles both deduplication passes

With Dedupely, you build duplicate searches for the first pass, starting with exact matches on email or domain. After enrichment, you scan again with searches on the fields enrichment added, like a company's core domain. You set rules for which value wins on each field and preview each merge, so enriched and team-entered values land where you want.

Run your first deduplication pass before you enrich

Enrichment works best on records you can trust

Deduplication and enrichment improve each other when they run in the right order. Deduplicating first means each lookup goes to one person or company, and the enriched data lands where your team works.

Enrichment then adds fields that reveal duplicates you couldn't see, and sometimes creates new ones. A second pass catches both, with clear choices about which values win.

Frequently asked questions

Should you deduplicate or enrich CRM data first?

Merge confirmed duplicates before broad enrichment, then search again using the added details. If identity is unclear, verify or enrich that limited group before merging. The second pass can reveal candidates such as companies with a shared website, but those still need confirmation.

Can data enrichment create duplicates?

Yes: some enrichment tools add records as well as fields, like a company from a contact's email domain or contacts at an account. If the tool doesn't find the existing record, it creates a second one. Enriched legal names with suffixes can also hide matches.

Why deduplicate after enrichment?

Because enrichment adds fields that can link records you couldn't match before. Two companies with similar names may get the same website domain, and a contact with only a personal email may get a work email. Matching on those new fields finds duplicates the first pass missed.

Which value should win when enriched records merge?

It depends on the field: fields your team owns, like owner or lifecycle stage, usually keep the CRM's value. Firmographic fields like industry or company size often keep the most recent or most complete value. In every case, a blank shouldn't overwrite an existing value.

Does enriching duplicates cost more?

It can, when an enrichment tool charges by record or credit. Each duplicate is looked up separately, so one customer with three records can be enriched three times. Deduplicating first means each lookup goes to a different person or company, and the data lands on the record your team uses.

Portrait of Gaby Salinas

Behind the article

Gaby Salinas

Marketing Assistant at Dedupely

Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.

As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.

Connect with Gaby on LinkedIn

Contact us

We’d be happy to help you get this set up.

Write us a message

We probably know the answer to your question already

Email copied to your clipboard!

Book a Zoom

Whether you’re getting started or getting intense.
Get in touch!

Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.

"I do recommend! A++ Pretty easy to use. Adequate reporting. SUPERB CUSTOMER SUCCESS!"
Alina T

Alina T

Sales Operations Specialist, FieldBee

51–100 employees

Running CRM cleanup for clients? See the Partner Program

Skip to content