Deduplicate and Suppress Business Contacts Before a CRM Import

Deduplication and suppression answer different questions. Deduplication asks whether two records describe the same object. Suppression asks whether a record must be excluded from a particular use. A clean import needs both decisions, in that order of meaning even if your process checks suppression first.

Download the illustrative deduplication CSV and keep an unchanged source copy. The file demonstrates review decisions with fictional records; it is not a tested integration with a particular CRM.

Define the object you are deduplicating

A business-location dataset can contain several legitimate offices for one company. If your CRM has an account and location structure, group confirmed offices under the account while preserving the locations. If it only supports company records, decide how to retain address details before importing.

A shared website or phone is evidence for review, not an automatic deletion rule. Franchises, central booking services and multi-office businesses can share contact channels. Conversely, two slightly different business titles may describe the same location.

Write the account/location rule in your import notes. Otherwise one teammate may merge by domain while another imports every address as a separate company.

Create comparison fields without destroying originals

Keep the original business name, website, phone and address. Add normalized helper columns in the working sheet:

• Website hostname with consistent case and obvious formatting differences removed.

• Phone comparison value using a consistent country-aware format where the country is known.

• Address comparison value with consistent whitespace and a documented abbreviation policy.

• Email comparison value with surrounding whitespace removed; avoid changing mailbox spelling or punctuation based on guesses.

Do not treat a missing value as a shared identity. Two blank websites are not a match. Do not strip country information from phone numbers and assume the remaining digits identify the same business.

Use match tiers rather than one aggressive rule

Strong duplicate candidate: same confirmed location, compatible business identity and matching contact or website evidence. Review and keep one canonical record with the source references retained.

Possible related locations: same domain or central phone, but different addresses. Research the organizational relationship and preserve locations until it is understood.

Ambiguous match: similar names with incomplete or conflicting details. Hold for review rather than silently merging.

In the downloadable example, two fictional Cedar Plumbing rows have similar names and the same apparent address, so they need duplicate review. Fictional Harbor Roofing North and South have distinct addresses and a shared inbox, so both locations are preserved while repeated contact to the same inbox is avoided. Those decisions should not be reduced to “remove repeated email.”

Apply suppression as an independent control

Check your established suppression list before outreach or campaign import. Preserve the reason, date and relevant scope of the restriction. An opt-out associated with an address must not disappear because a refreshed source spells the business name differently.

If several locations share a suppressed central inbox, review that shared contact route before treating each branch as another opportunity. Do not use alternate formatting or a newly discovered address to circumvent a person's objection.

Suppression records need not become campaign contacts. Keep the minimum information required for reliable matching in the appropriate controlled system, with ownership for corrections and updates.

Reconcile the proposed import

Count raw rows, duplicate rows removed, legitimate locations retained, ambiguous records held and records excluded for suppression. Use a single final disposition per input row when you need the totals to reconcile; keep overlapping issues as notes.

Record both imported locations and unique accounts if those totals differ. A lower row count after cleanup does not by itself indicate lost market coverage; it may reflect confirmed duplicate removal. Equally, deleting branches indiscriminately can hide useful location information.

Test a small import and document the mapping

Map the actual CSV headers to the destination fields and inspect a small batch. Preserve ZIP codes and phones as text where appropriate. Confirm that additional emails remain associated with the right business rather than generating new companies.

Check record ownership, grouping, suppression behavior and the destination's rejected-row report before a full import. This guide does not claim an automated CRM integration; the checks apply to your chosen import process.

Retain the mapping and decision log for the next batch. The broader business database guide explains how source dates, ownership and role research keep the cleaned list useful after the first import.