Skip to main content
D2 GROUP

Insight / B2B Sale Research

How to deduplicate target companies without losing real buying entities

Resolve which records describe the same legal company, which represent separate operating sites, and which belong to a larger group before the sales team reviews a target list.

Content owner: D2 GROUP. The company and record examples are fictional research exercises, not customer data, verified client cases or published deduplication results.

Direct answer

Deduplication is an entity decision, not just a matching-name rule

B2B account deduplication checks whether two records refer to one business entity, two subsidiaries, separate buying sites or merely similar trade names. Keep a reviewable evidence trail: original identifiers, legal names, location, web domains, parent relationship, source and checked-at date. Merge only records that can be tied to the same entity under a documented rule; otherwise mark the relationship uncertain. A correctly deduplicated company is still a discovery candidate until ICP, buyer and direct work-email QA pass.

Legal company name

The registered entity may differ from the website brand. Verify jurisdiction and the identifier when a suitable registry or issuer is available; an unverified tax number is not a matching key.

Trading names and aliases

A former name, transliteration or product brand can point to the same company. Preserve aliases for CRM search but keep a single approved primary entity when the evidence supports a merge.

Parent and subsidiary

A group parent may own several local companies that contract separately. Shared logos and domains do not by themselves mean their procurement and sales ownership should be merged.

Site and location

A manufacturer can operate multiple factories. The site may be a distinct research unit even when the same legal person owns it; distinguish account entity from site-specific opportunity context.

Practical workflow

Five-step duplicate review before CRM handoff

Document the reason for each decision, not only the resulting row count.

  1. 01

    Define the canonical account key

    Agree whether the client's CRM treats the contracting legal entity or the operating site as the primary account. Record the rule, market and approved owner before matching records.

  2. 02

    Collect candidate identity clues

    Compare source URLs, official name, current registered identifier if permitted, website domain, operating addresses, business scope and group structure. Treat common names or shared office buildings as weak clues.

  3. 03

    Classify the relationship

    Choose SAME_ENTITY, DISTINCT_ENTITY, PARENT_CHILD, SITE_OF_ENTITY or UNKNOWN. Keep the exact source/check dates and why the relationship is supported. Do not make a silent merge on a similarity score.

  4. 04

    Apply client exclusions and owner checks

    Before adding the result to outreach, check existing customer and do-not-target rules across the resolved identity, including aliases and relevant child entities only where the approved exclusion policy requires it.

  5. 05

    Preserve reversibility at handoff

    Keep original source identifiers, the canonical record, aliases, merge decision, reviewer, exception status and affected sales owner. Ask for a recheck if later evidence reveals a separate contracting entity.

Review checklist

Can a reviewer reproduce this identity decision?

Use this before changing an existing CRM target record.

  • Canonical account unit and market are agreed before applying merge rules.
  • Legal-entity identifiers and operating-site identities are not silently conflated.
  • Aliases and former names remain searchable after an approved merge.
  • Parent-child relationships have an attributable source and checked date.
  • Uncertain matches remain UNKNOWN rather than being deleted or auto-merged.
  • Existing-customer and contact restrictions are checked against the resolved identity.

Illustrative examples

Three fictional deduplication decisions

These illustrative records use imaginary entities and no real customer information. They show QA reasoning, not an automated matching accuracy claim.

Two spellings, one entity

Fictional Greenfield Components Ltd and Greenfield Component Co appear in different directories. A suitable current entity record confirms the same legal identifier and facility. Merge the two company rows under one canonical entity, preserve both aliases and their source/check dates, then run the normal company-fit checks.

One parent, two distinct buyers

Fictional Northline Group owns Northline Logistics VN and Northline Equipment SG. Their sites have different business models and contracting companies. Tag PARENT_CHILD, retain both records and assign company-specific ICP decisions. A shared corporate logo does not justify collapsing their separate buyer mapping.

Similar name, insufficient evidence

Fictional Horizon Trading appears in two countries with nearly identical names. Neither entity identifier nor operating relationship has been verified. Mark UNKNOWN, retain both as unresolved candidates and request a source check before merging or contacting anyone.

Interpretation limits

Avoid three damaging shortcuts

A shorter database is not automatically a more accurate market.

Domain equals legal entity

One website can describe multiple incorporated firms; one firm can use more than one domain. Check the contracting company instead of making the domain a universal match rule.

No match means no customer conflict

An existing customer could be recorded under a former trading name or subsidiary. Check the client's approved suppression scope rather than searching only exact spelling.

Merged account means ready for sales

Deduplication resolves entity identity; it does not validate ICP fit, a current named buyer, a direct work email or purchase intent. Preserve the next required research gate.

Use insights without assuming a sale

Turn a research question into a checkable account brief.

The evidence can inform your approach but does not establish customer demand. Inspect the dossier standard, compare research hours or discuss a relevant ICP.

For this topic: Bring the observable event, your target market, the company-fit rule and what your team needs to verify next. An enquiry is voluntary, not a marketing subscription; the current website prepares an email for you to send yourself.

FAQ

Questions sales teams ask

Should every subsidiary be merged into the parent company?+

No. Use the client's canonical account definition and confirm legal and commercial responsibilities. Parent-child is a relationship; it is not proof of one purchasing entity.

Can a shared email domain prove duplicate companies?+

No. Domains and employee addresses are clues, not final evidence of corporate identity or procurement ownership.

What if company registration information is unavailable?+

Keep the candidate relationship UNKNOWN, cite the evidence that is available and request additional checks before a material merge or exclusion.

How does deduplication affect dossier acceptance?+

It improves the account foundation and exclusion review. Final ACCEPT still requires the contracted company-fit, buyer and direct work-email checks.

Discuss the account research your team needs

Share your ICP, target geography and current sales research challenge. D2 can explain the evidence and acceptance criteria for a suitable scope.

Discuss your research brief