All posts

How to Re-import Verified Emails Into HubSpot Without Duplicates

··4 min read

Export contacts with their Record ID, verify the file, then re-import a slim file of Record ID, email and a verification status property. Because each row carries the Record ID, HubSpot updates the existing contact instead of creating a new one, even when the email was corrected. Then build a segment from the status and act on it.

This post is about the round trip back into HubSpot. For which HubSpot contacts to clean in the first place, see our guide to cleaning HubSpot contacts.

Why duplicates happen

HubSpot deduplicates contacts on import using Record ID or email address. That works well when nothing changes. Three situations break it:

  1. The email changed. You fixed jane@gmial.com to jane@gmail.com. With no Record ID in the row, HubSpot sees a new email and creates a new contact.
  2. Formatting differs. Stray spaces, a trailing dot or an invisible character in the exported file can make an address look different from the stored one.
  3. The file came from somewhere else. If the verified list is a merge of HubSpot and another source, rows without a Record ID are new as far as HubSpot is concerned.

The fix for all three is the same: keep the Record ID attached to every row from export to import.

Step 1: Export with Record ID

Create a view or segment of the contacts you want to check, then export it. Make sure Record ID and Email are in the export. Our HubSpot export guide covers the export itself.

Keep the original file untouched. Work on a copy.

Step 2: Tidy the file before verifying

  • Trim spaces and lowercase the email column.
  • Remove rows with an empty email.
  • Fix obvious typos with the email typo corrector. When you change an address, keep the Record ID on the same row.

Step 3: Verify, then reduce the file

Run the file through verification. The result will have more columns than you need. For the re-import, keep only:

Column Example Purpose
Record ID 51234 Matches the existing contact
Email jane@gmail.com Updated if you corrected it
Email verification status invalid Your new custom property
Email verified date 2026-11-18 Optional, for re-check scheduling

Leaving out names, owners, lifecycle stage and everything else means the import cannot overwrite something a rep edited after you exported. The CSV import formatter can drop and rename columns if your spreadsheet tool is awkward with large files.

Step 4: Create the status property

Before importing, create a contact property called something like Email verification status. A dropdown with fixed options works best, because segments filter on it cleanly:

  • valid
  • invalid
  • catch-all
  • unknown
  • disposable
  • role

Map your verifier's labels onto these. Our post on verification statuses explains what each label means.

Step 5: Import as an update

Start a contact import, choose the slim file and map:

  • Record ID to Record ID
  • Email to Email
  • the status column to your new property
  • the date column, if you have one, to a date property

Choose the option that updates existing records. When the import finishes, check the summary. The number of new contacts created should be zero. If it is not, open the import errors and the newly created records; they are the rows whose Record ID was missing or wrong.

Step 6: Act on the results

Build segments from the new property:

Status Suggested action
invalid Set as non-marketing contact, or delete if the record has no history
disposable Same as invalid
catch-all, unknown Keep, but exclude from large marketing sends unless engaged
role Keep for sales if relevant; exclude from marketing unless opted in
valid No change

Setting contacts as non-marketing is often better than deleting. The record, deals and notes stay, but no marketing email goes out and the contact stops counting toward marketing contact limits.

Keeping it clean afterwards

Add the verified date to your re-check routine. Contacts not checked in six months or more can be exported and run through the same loop. For new contacts, our post on verifying emails with a HubSpot workflow shows how to check addresses as they arrive.

Run the check

Export, verify, and bring the results back with the Record ID. Sign in with Google and your first 100 email checks are free, no card. Plans for larger exports are on the pricing page.

Common questions

Why does re-importing into HubSpot create duplicate contacts?

Because the file did not give HubSpot a way to recognise the existing record. HubSpot matches contacts on import by Record ID or email address. If a row has no Record ID and its email differs from the stored one, for example after a typo was corrected, HubSpot treats it as a new contact.

Should I delete invalid contacts from HubSpot after verification?

Not necessarily. Deleting removes the history, deals and notes on the record. Many teams set invalid contacts as non-marketing contacts, which stops marketing email to them and stops them counting toward marketing contact billing, and keep the record for sales history. Delete only contacts with no value at all.

Can I update the email address of an existing HubSpot contact by import?

Yes, if the row includes the contact's Record ID. HubSpot then updates that record, including its email, instead of creating a new one. Without the Record ID, a changed email is read as a new person.

What columns do I need to re-import verification results into HubSpot?

Record ID, Email and your verification status column. You can add a verified date if you want to track when each contact was last checked. Leave out every other column so the import cannot overwrite data that changed since the export.

Check your list before you send

Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.