Article

How to Merge Verification Results Back into a CRM: Step-by-Step

By Unlimited Verifier Team ·

Flow diagram showing a CRM keys-only export being verified and merged back into record status fields by email verification results.

Summary

To merge verification results into a CRM, export a keys-only file with record IDs and emails, verify it, then re-import with update-existing-records so each contact gets a status. Write verdicts to dedicated status fields and never overwrite the email address itself.

To merge verification results back into a CRM, export a keys-only file containing the CRM record ID and email, verify it, and re-import the verdicts with "update existing records" so each contact gets a status. Write Valid, Risky or Invalid into dedicated status fields, and never overwrite the email address itself.

Verification is the easy part. Many merges fail at the join: rows that never receive a status, duplicate records that inherit nothing, or a re-import that quietly brings back addresses you had already removed. This guide covers each stage, with the arithmetic for a 48,000-contact database. For the wider process, see our pillar on the bulk email list verification workflow.

Quick answer

What does merging verification results back into a CRM involve?

Merging means attaching each verdict from a verification run to the matching contact record, so that sequences, campaigns and lead routing can read it. Verification produces a separate file with one row per address. Your CRM is the system of record, holding contacts, deals and opt-out history. This matters most for email verification for ecommerce and SaaS teams, where the CRM drives most outbound sending.

A cleaned list sitting in a spreadsheet changes nothing. Reps keep emailing addresses that bounced last quarter because the CRM still marks them as ready. The failure usually sits in the link between verdict and record, not in the verification itself.

A verdict is also a point-in-time claim. An address marked Valid in March can bounce by September, so the merge must record when the check ran, not only what it returned.

Bottom line: A verification result only protects you once it changes what your CRM allows people to do.

Should you match on record ID or email address?

Match on the CRM record ID whenever one exists, and use normalized email only as a fallback. Email is the natural key, but it is also the field most likely to be dirty: trailing spaces, uppercase variants, two records for one person, or a contact who changed employers and kept the old address.

Normalize before matching by trimming whitespace, including non-breaking spaces pasted from web forms, and lowercasing the address. RFC 5321 allows the local part to be case-sensitive, but major mailbox providers treat addresses case-insensitively in practice, so lowercasing is the sensible default for matching.

One address can map to several records, such as a contact and a lead for the same person. Every matching record needs the verdict, so an email-keyed merge must fan out to all matches rather than stop at the first.

Duplicates can also disagree on consent. One record may carry an opt-out while another is Valid. Let the verdict fan out, but never let it clear an opt-out. Where records conflict, the send-eligible rule should use the stricter status.

Bottom line: Join on record ID, fall back to normalized email, push each verdict to every duplicate, and never let a verdict override an opt-out.

How do you prepare the export so the merge doesn't break?

Export only the record ID and email columns, format the ID as text, save as UTF-8 CSV, and count rows before you upload. A full CRM export carries fields such as owner, notes and phone numbers. Those fields can be corrupted on re-import, slow verification, and make the audit harder.

Watch for two Excel traps. It drops leading zeros from IDs (so 00123 becomes 123), and it converts long numeric IDs into scientific notation. Format the column as text before you open or save the file. RFC 4180 sets the CSV quoting rules that most tools follow, which helps when a name field contains commas.

Run three counts before uploading: total rows, unique IDs, and blank emails. Blank emails will end up with no verdict, so you should know their number in advance. A keys-only file is small. At roughly 40 bytes per row (our estimate, not a standard), 48,000 rows comes to about 2MB, well within the 10MB limit. If you are new to the process, how to upload a CSV to an email verifier covers the mechanics, and how to clean a messy CSV of emails before upload covers the formatting problems that cause most mismatches.

Bottom line: A keys-only export with text IDs and known counts makes every later step checkable.

Which merge method should you use?

For a first merge, use the CRM's built-in import with "update existing records", as long as your CRM has a unique field to match on. Move to an API upsert once the process repeats often enough to justify a script.

Method Match key Overwrite risk Best fit Main limitation
Spreadsheet lookup (XLOOKUP or VLOOKUP), then manual re-import Record ID or email Medium: a misaligned paste updates the wrong contacts Small one-off cleans, up to a few thousand rows Hard to audit; Excel formatting can corrupt IDs
CRM's built-in import with "update existing records" Email, or a unique field you map Medium to high if a column maps to the wrong property Teams without developers; periodic merges Needs careful mapping; keeps no verification history on its own
CRM API or data loader upsert on a custom external ID Custom external ID field Low once tested Large databases and repeat merges that need an audit trail Needs a developer and a sandbox for testing
Verification API at sign-up and import Email at capture Low Ongoing hygiene for new contacts Covers new addresses, not the existing base

CRM behaviour varies. HubSpot treats email as the unique identifier for contacts, so an email-based update behaves differently from a record-ID update. Salesforce upserts match on an external ID field that you mark as unique on the object. Menu names change between releases, so check your admin documentation before running anything.

Unlimited Verifier has no native CRM or Zapier integrations. In practice, you either export a CSV, verify it and re-import, or call the email verification API from your own script. For a broader comparison of options, see our guide to the best email verification tools and how to choose an email verifier.

Bottom line: Use the CRM's own import for the first merge, and the API once the process becomes routine.

What status fields should you add to the CRM?

Add five dedicated fields so the verdict has a home that never touches the contact's address or other data.

Field Type Example values Purpose
Email status Dropdown Valid, Risky, Invalid, Not checked The single field that sending rules read
Email checked on Date Date of the verification run Finds records due for re-checking
Verification reason Text or dropdown catch-all, disposable, role-based, no mailbox Explains why a record is Risky or Invalid
Source batch Text "cleanup-batch-1" Audit trail showing which file produced the verdict
Send eligible Formula or checkbox True only when status is Valid and the contact is not opted out One boolean for workflows to filter on

Keeping the verdict separate means a future re-verification overwrites only the verdict. It cannot damage contact data, and the batch field tells you which run wrote each value.

Set Email status to "Not checked" on every existing record before the merge. Any record that fails to match then stays excluded rather than slipping through as sendable. This fail-closed default protects you more than any other setting in the process.

Make Send eligible a formula or workflow rule rather than a box someone ticks by hand. A rule means a suppressed or opted-out contact cannot become eligible through a manual edit.

Bottom line: Default everything to "Not checked", and let one derived field control sending.

How do you map each verdict to a CRM action?

Map Valid to sendable, Risky to held, Invalid to suppressed but retained, and any blank result to not sendable.

Verdict CRM status Send eligible Action
Valid Valid Yes Include in campaigns and sequences
Risky Risky No Hold. Test catch-all addresses separately before any send
Invalid Invalid No Suppress from all email. Keep the record
No result Not checked No Investigate the mismatch. Treat as unverified

Why keep Invalid records instead of deleting them? Deletion erases the memory that an address already failed. The same address can return through a web form, a purchased list or an integration, and without the record your CRM cannot recognise it. Keeping it with an Invalid flag lets future imports deduplicate against it. Deletion also weakens your opt-out trail. The FTC's CAN-SPAM compliance guide says opt-out requests must be honoured within 10 business days, and you need records to prove you did. For what to do with the invalid rows themselves, see what to do with invalid emails after cleaning.

Why hold Risky records? Catch-all domains accept mail for any local part, so a verifier cannot confirm the individual mailbox. Disposable and role-based addresses such as info@ carry different risks. Unlimited Verifier flags catch-all, disposable and role-based addresses, so use those flags as your reason codes. For the catch-all rows specifically, Catch-all email verification explains how those results are handled.

Verification improves list quality but does not prove consent. The email verification compliance and hygiene side still depends on how each contact opted in.

Bottom line: Only Valid records should be sendable, and Invalid records should be remembered, not removed.

How do you merge results into a CRM, step by step?

  1. Snapshot the CRM. Take a full backup export so you can roll back if the mapping is wrong.
  2. Export a keys-only file. Include record ID and email, normalize both, and save as UTF-8 CSV.
  3. Verify the file and download results the same day. Confirm that the row count matches your input.
  4. Join results to the export on record ID, or on normalized email for records without an ID. Check that every row finds a match.
  5. Create the status fields and default them to "Not checked".
  6. Write the verdicts using "update existing records", mapping only the status fields. Never map the email field.
  7. Reconcile. Count rows by status, confirm zero blanks, and spot-check 25 records by hand.

Step 1 gives you a rollback. Step 5 keeps unmatched records excluded. Step 7 turns the merge into evidence you can show a colleague or an auditor.

Bottom line: Each step produces a check, so the merge can be proven rather than assumed.

How do you test your first merge before running the full file?

Run a 20-row test first, so mapping mistakes surface before they reach the full database.

  1. Export from the CRM. Filter the contacts view to records with an email, then export only Record ID and Email as CSV.
  2. Open the file and format the ID column as text. Delete blank rows, and confirm IDs keep their leading zeros.
  3. Build a 20-row test file. Include one address with trailing spaces, one with uppercase letters, and one email that appears on two records.
  4. Sign up for an account. The Free plan allows up to 150 emails per list, so the test file fits easily.
  5. Upload and verify a list. Confirm that the email column was detected.
  6. Download the results the same day. Free-plan results are kept for 24 hours. How to read an email verification results file explains each column.
  7. Check whether the ID column carried through to the results. If it did not, match on normalized email and note the change in your merge log.
  8. Join in a spreadsheet. Confirm that the trailing-space and uppercase rows matched, and that the duplicate received the verdict on both records. For a single contact you want to double-check, the free single-address checker gives a quick second look.
  9. Create the status fields from the table above, and default existing records to "Not checked".
  10. Run the test import with "update existing records", mapping Record ID to the ID field and the verdict to Email status. Check all 20 records in the CRM before you run the full file.

Once the test is clean, repeat the steps with the full export. The test costs minutes and prevents most of the errors described below.

Bottom line: A 20-row dry run catches the join and mapping errors that are expensive to fix at 48,000 rows.

What does a 48,000-contact merge look like in practice?

The scenario below is illustrative. The plan limits and arithmetic are real, but the verdict percentages are hypothetical.

The starting point. A B2B company has 48,000 contact rows in its CRM. After trimming and lowercasing, 1,140 rows repeat an address already in the file.

48,000 − 1,140 = 46,860 unique emails

Choosing a plan. On the Free plan, each list holds up to 150 emails, and you can run 25 lists a month.

25 lists × 150 emails = 3,750 emails per month 46,860 ÷ 3,750 = 12.5, so 13 months

That is impractical. On Pro, each list holds up to 25,000 emails, so the addresses split into two lists:

25,000 + 21,860 = 46,860

Keep the ID column in both files. Pro costs $29 for one month, or $25 a month billed annually ($300 a year). A one-off clean therefore costs $29 at most, which is the relevant figure for email verification pricing decisions at this scale. If your list is 100,000 rows or more, how long verifying 100k emails takes covers the timing.

Hypothetical results:

Verdict Unique emails Share
Valid 40,100 85.6%
Risky 4,300 9.2%
Invalid 2,460 5.2%

40,100 + 4,300 + 2,460 = 46,860

If you choose to run deep verification on the 4,300 Risky addresses, that uses 4,300 of your 25,000 monthly deep verifications and leaves 20,700. Standard verification is unlimited on every plan, so the 46,860 standard checks add no per-email cost.

The merge. Each unique verdict fans out to every row sharing that email. The 1,140 repeat rows inherit their address's status, so all 48,000 rows receive a verdict. The Valid row count in the CRM will therefore exceed 40,100, because duplicates copy the status.

Reconciliation. The expected number of rows with a blank status is zero. If you find 37, look for whitespace or a typo in the key before you suspect the verifier.

Ongoing checks. Suppose the company adds 3,000 sign-ups a month and checks each through the API. That uses 3,000 of the 100,000 API emails included on Pro, or 3%. For a bulk re-check of the 46,860 addresses from a script, you need five requests of up to 10,000 each: four full requests and one of 6,860.

Bottom line: The plan limit, the duplicate fan-out and the blank-row check each change the result, so run the arithmetic before you export.

How do you keep the CRM clean after the first merge?

A one-time merge decays. People change jobs and new forms add new errors, so the process has to run continuously.

For the wider maintenance routine, see email list maintenance best practices. If a large share of your base fails, what to do if 30 percent of your list is invalid explains how to triage it.

Bottom line: Verification at capture, at import and on a schedule keeps merged data accurate between full cleans.

What are the most common mistakes when merging results?

Bottom line: Many failed merges trace back to the join and the defaults, not to the verification step itself.

How we compared (and limitations)

This guide is based on public documentation: CRM import references from HubSpot and Salesforce, the cited RFCs, and the FTC's CAN-SPAM guidance. The steps have not been checked against live CRM accounts, and CRM menus and import rules change between releases, so validate the walkthrough in your own environment with the 20-row test.

The worked example uses hypothetical verdicts to illustrate the arithmetic. The 99.5% accuracy figure is Unlimited Verifier's stated figure for deep verification, not an independent benchmark. Unlimited Verifier has no native CRM integrations, so the workflows here rely on CSV export and import or the REST API.

Bottom line: Treat this as a process design with worked numbers, and confirm the CRM-specific details before running a full merge.

Merge join check on a 48,000-contact database

Step Count
Contacts exported (keys only) 48,000
Matched by record ID 47,640
Matched by normalized email (fallback) 260
Unmatched, held as not sendable 100

Action: investigate the 100 unmatched rows before any campaign runs. Every row in scope should end with a status value.

Frequently asked questions

What is the best key for merging verification results into a CRM?

The CRM record ID is the best key because it identifies one specific contact reliably. Use a trimmed, lowercased email only when no reliable ID exists. Email alone can fail with duplicates, typos, or changed addresses.

Should verification results overwrite the email field?

No. Write verdicts to separate status fields such as status, checked date, reason, and batch ID. Overwriting the email address can destroy the original value and break audit trails.

What should happen to contacts with no verification result?

Treat any row without a result as not sendable until it is checked. This prevents unverified contacts from slipping into campaigns because a join silently failed.

How do I handle duplicate records for one email address?

Fan the verdict out to every matching record so each duplicate gets a status. Do not let a Valid verdict clear an existing opt-out on any duplicate.

Can a verification result clear an opt-out?

No. Verification indicates deliverability, not consent. Keep opt-out and suppression flags independent, and never let a verdict override them.

Why should I record the date of each check?

A verdict is a point-in-time claim. An address marked Valid months ago may now bounce, so the checked date lets you re-verify stale statuses before sending.

Should I test the merge before running the full database?

Yes. Run a 20-row test first, confirm the status fields populate correctly, then check that every CRM row in scope has a status after the full import.

How long are verification results available for download?

Retention depends on your plan, so check the provider's current documentation. Download results the same day to avoid losing them before merging.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.