To find duplicate company names, compare a stable domain first, then use normalized company-name matching for records without a reliable website. Review the proposed groups before merging because two businesses can share a short or generic name.

This guide shows how to:

Step 1: Import Your Company Name List

Start by importing your company list into Datablist. Keep a domain or website column when you have one. A domain is usually a stronger company identifier than a name alone.

To reproduce the measured workflow below, download the 1,000-row deduplication sample. It contains 800 designed entities, including 50 pairs with company-name and website variations.

The imported 1,000-row deduplication sample
The imported 1,000-row deduplication sample

Review the imported properties and set Website to URL when applicable. The Company property can remain Text.

Step 2: Identify Duplicates Using Algorithms

Open Clean > Merge duplicates to detect matching company records.

Opening Merge duplicates from the Clean menu
Opening Merge duplicates from the Clean menu

When the list contains websites, match those first. Then run a separate company-name pass for rows without a reliable website or domain.

Match company websites

Turn off All Properties and select Website only.

The Website property selected for duplicate matching
The Website property selected for duplicate matching

Choose Smart with the URL processor. The processor ignores protocol differences and trailing slashes. Enable these optional settings when they fit your data:

  • Ignore Subdomain treats subdomains as the same registered domain.
  • Ignore Path compares the domain without page paths.
  • Ignore Query Params removes tracking and other query parameters before comparison.
Smart URL matching configured to ignore subdomains, paths, and query parameters
Smart URL matching configured to ignore subdomains, paths, and query parameters

Use these options carefully. Two subdomains or paths can represent separate accounts, branches, products, or locations. Keep them when those distinctions matter.

The Website pass returned 200 two-row groups from the 1,000-row sample. Fifty pairs contain designed URL variations, and 150 pairs already share the same Website value. Validation of the exported groups found no cross-entity match.

Website matching results with 1,000 records checked and 200 duplicate groups
Website matching results with 1,000 records checked and 200 duplicate groups

Open Why matched before processing a group. It shows the Website property, Smart algorithm, URL processor, enabled URL options, and match score.

Why matched showing the URL processor and enabled normalization settings
Why matched showing the URL processor and enabled normalization settings

Download the 200 Website duplicate groups to inspect the matched rows.

Match normalized company names

Select Company for a second pass.

The Company property selected for duplicate matching
The Company property selected for duplicate matching

Choose the comparison method:

  • Use Smart with the Company Name processor to remove common company terms before comparison.
  • Use Jaro-Winkler or Levenshtein for spelling variations. Start with a high threshold and keep lower-confidence groups in Needs review.
Smart matching configured with the Company Name processor
Smart matching configured with the Company Name processor

Run the duplicates check to detect matching records.

Understanding the Company Name Processor

The Company Name Processor is a special tool that normalizes company names before detecting duplicates. This is crucial because companies often have different variations of their names in your data.

What It Does:

  • Removes Legal Suffixes: LLC, Inc., Ltd., etc.
  • Ignores Geographic Terms: Europe, USA, UK, etc.
  • Eliminates Business Keywords: Partners, Group, Technologies, etc.

Example:

Original NameNormalized Name
Apple Inc.Apple
Apple USA LLCApple
Apple TechnologiesApple
Microsoft CorporationMicrosoft
Microsoft Ltd. UKMicrosoft

These values can become matching candidates. The Company Name processor is a paid feature, and the group still needs to represent the same business before you merge it.

Measured result on the 1,000-row sample

The Company Name pass returned 200 two-row groups from 1,000 checked records:

  • 50 pairs contain designed company-name variants such as Cedar 0715, Inc. and Cedar 0715 Group LLC.
  • 150 other designed duplicate pairs already share an identical company value.

All 200 groups map to the correct synthetic entities in this test. No group combines records from different entities. This is a result for the generated sample, not a general accuracy guarantee.

Company Name results with 200 duplicate groups in Needs review
Company Name results with 200 duplicate groups in Needs review

The groups show a 100% match score. They appear in Needs review because other properties conflict, not because the company-name match has low confidence.

Open Why matched to verify the property, algorithm, processor, and score used for a group.

Why matched showing Smart comparison with the Company Name processor
Why matched showing Smart comparison with the Company Name processor

Download the 200 exported duplicate groups to inspect the matched rows and DuplicateGroupId values.

Step 3: Merge Duplicate Company Records

If you only need a list of matches, use Download groups and stop before processing. Continue when you want to consolidate the records in Datablist.

Resolving Conflicts

A conflicting property indicates differing values for the same field across the identified duplicate records.

If duplicate records have different values in fields, you need to decide how to merge them.

Choose a rule for each conflicting property:

  • Combine preserves distinct text values with a delimiter.
  • Keep the selected record's value discards the other values.
  • Field survivorship rules can choose the newest, oldest, longest, shortest, highest, lowest, or most frequent value on paid plans.

Use the shortcut control to apply the same rule to several conflicting properties, then adjust individual fields where needed.

Merge and preserve data with conflict-resolution settings
Merge and preserve data with conflict-resolution settings

Choosing a Master Record

One record becomes the destination and keeps its Datablist ID.

You can select based on:

  • Most Complete: Keep the record with the most populated properties.
  • Last Updated: Keep the most recently modified record.
  • First Created: Keep the oldest record.
  • Highest Value or Lowest Value: Compare a selected property.
  • Matching Value: Keep the record containing a specified property value.

After configuring merging rules and master record selection, refresh the preview to visualize the outcome of the merge operation before committing changes.

Record to keep options with a property-based rule and preview
Record to keep options with a property-based rule and preview

The preview displays the values that will be deleted, combined, and the designated master record for each duplicate group.

Field-level survivorship rules for conflicting property values
Field-level survivorship rules for conflicting property values

For exceptions, open Review group and choose values manually.

Manual duplicate-group review with company records side by side
Manual duplicate-group review with company records side by side

Process the Ready groups. Groups still marked Needs review remain unchanged.

A completed merge with a downloadable change log
A completed merge with a downloadable change log

After merging, use Export in the collection header to download the clean list as CSV or Excel. The post-processing change log records deleted and updated IDs when you need an audit trail.

For the complete matching, review, and merge settings, read the Duplicate Finder documentation.