Deduplication is not simply deleting every repeated name. Two people can share a name, while one person can appear under different names, companies or state licenses. Choose a matching rule that fits your campaign and preserve enough history to explain each merge.
Use separate person, email and company checks. A single matching field cannot safely resolve every duplicate.
For a national starting point, explore our USA real estate email list and choose the audience and market for your brief.
Define what should be unique
A person-focused campaign may need one preferred contact route per professional. A company-focused campaign may need one decision-maker per firm. A location-based project may legitimately keep several branches of the same brand.
Write the rule before reviewing the file. Otherwise the same repeated company can be treated as useful coverage in one comparison and an error in another. Request stable IDs where available, but confirm how those IDs were assigned.
Normalize cautiously before matching
Trim accidental whitespace and compare email domains without case differences. Standardize state codes and preserve ZIP codes as text. Keep original values in separate columns so normalization can be reversed.
Do not remove characters or rewrite mailbox names based on provider-specific assumptions. Do not merge all people at a shared office inbox into one person. If a transformation may change identity, review it instead of applying it silently.
Separate exact matches from possible matches
Exact repeated source IDs or identical rows are different from similar names at nearby offices. Keep an uncertain-match queue with the evidence used. A name plus a brokerage can support review but may still confuse relatives, team members or a changed employer.
When sources conflict, retain both values and their dates until a preferred value is supported. A newer timestamp is useful only if you know what was checked at that time.
Preserve campaign exclusions across updates
A refreshed file should not reintroduce a contact your organization has already excluded. Match against prior CRM records and suppression data using your established process, then log additions, changes and removals.
Ask the provider how national totals treat professionals licensed in multiple states. Sum unique records across the selected states rather than assuming the sum of state-file rows equals unique national people.
- Keep original and normalized values.
- Record the merge reason and chosen survivor.
- Review ambiguous matches separately.
- Reapply existing exclusions after every update.
Define how repeated records should work.
For agent selections, explain whether you need one row per person, one per office relationship or one per distinct email address.
Explore agent selections