Quantum Business Solutions Quantum Business Solutions
Article

Clean Up HubSpot Before Connecting ZoomInfo: A Data Prep Checklist

Shawn Peterson Shawn Peterson·Nov 22, 2026, 10:21:06 AM
Quantum Business Solutions card: cleaning up HubSpot data before connecting ZoomInfo

TL;DR: Quick Answer

Before you connect ZoomInfo, fix the HubSpot data that ZoomInfo uses to match: company domains, duplicate companies and contacts, personal emails, record owners and the dropdown fields ZoomInfo will write into. ZoomInfo checks companies by domain and contacts by email, so gaps there turn into duplicates and wasted credits on day one.

  • Fix company domains and merge duplicate companies first, then contacts. Order matters.
  • Map every ZoomInfo user to an active HubSpot user, or new records land on the wrong owner.
  • Convert free-text fields to dropdowns and give ZoomInfo its own properties before any value is written.

This checklist is for the HubSpot admin or RevOps lead who has a ZoomInfo contract signed and a connection date on the calendar. It is not a general hygiene program. It covers the narrow set of fixes that decide whether ZoomInfo enriches the right records or quietly creates a second copy of your database, in the order we run them in client portals.

What breaks when you connect ZoomInfo to a messy HubSpot?

Matching breaks first, and everything downstream inherits the damage. When ZoomInfo cannot find the existing record, a rep's export creates a new one, enrichment writes to the copy nobody owns, and your reports count the same account twice.

Here is what each common problem turns into once the connection is live:

Problem in HubSpotWhat happens after you connect ZoomInfo
Companies with no domainExports cannot find them, so reps create duplicate companies
Two companies sharing one domainZoomInfo and HubSpot each pick one, and data splits across both
Contacts on gmail.com or yahoo.comWeak or no match, credits spent with little to show
Owners who left the companyEnriched records sit with inactive users and nobody works them
Free-text Industry, State or Employees fieldsZoomInfo values fail to land or mix with three spellings of the same thing
Junk lifecycle stagesYou enrich customers, vendors and test records you never meant to pay for

The pillar ZoomInfo HubSpot integration guide explains the whole connection. This page is only the prep.

How does ZoomInfo decide a record already exists?

ZoomInfo's own HubSpot integration guide spells out the rules, and they tell you exactly what to clean. When a user exports to HubSpot, ZoomInfo checks for an existing company by company domain. For contacts it checks email address first, then first name plus last name plus exact company name.

Enrich uses a similar idea. Its default match inputs for companies are the HubSpot Company name and Company Domain Name fields, and admins can add more fields but cannot remove those two. So a company with a blank domain and a slightly different name is close to invisible.

Two more behaviors matter for prep:

  • Contacts are not associated to companies on export. ZoomInfo's guide says exported contacts arrive as independent records. HubSpot's automatic company association does that job, and it also runs on email domain.
  • Duplicates collapse to one profile. When HubSpot holds several records for one account, ZoomInfo matches only one of them to its profile, so the others never get the benefit.

Put simply: domain and email are the keys. Clean those and most of the integration's problems never appear.

The data prep checklist, in order

Run these steps in sequence. Merging contacts before companies, for example, means merging twice.

  1. Back up and scope. Export companies and contacts with record IDs, and agree which records ZoomInfo should ever touch.
  2. Fix company domains. Fill blanks, split shared domains, standardize subdomains.
  3. Merge duplicate companies, then contacts.
  4. Separate personal emails. Flag them and keep them out of enrichment.
  5. Fix owners. Reassign records owned by inactive users and line up user emails across both tools.
  6. Clean lifecycle stages. Make sure customers, partners, vendors and junk are labeled so you can exclude them.
  7. Convert colliding fields. Turn free text into dropdowns and create ZoomInfo's own properties.
  8. Turn on company association and set opt-out domains.
  9. Build the enrich-ready list and check it against the ready test below.

Step 1 is not optional. HubSpot's duplicate tool warns that merged records cannot be reverted, so the export is your undo button.

Steps 1 to 3: domains, companies, contacts

Fix domains first. Build a company list where Company Domain Name is unknown and sort by number of associated contacts. Fill the domains that matter by hand or with a corrected import keyed on Record ID. Then look for shared domains: HubSpot's import tool flags "Multiple companies with this domain," and its automatic association links contacts to only one of the matching companies without letting you choose.

Decide on subdomains on purpose. HubSpot treats example.com and info.example.com as two companies. For most B2B portals, the parent domain should sit on the main company record and regional sites should be child companies, not stray duplicates.

Then merge companies. Use the duplicates tool: from the companies index, open the three-dot menu and choose Manage duplicates, or go to Data Management > Data Quality. HubSpot compares company domain, name, country, phone and industry. Reviewing pairs one at a time needs a Professional or Enterprise subscription. Bulk merging and custom rules need Data Hub Professional or Enterprise.

Then merge contacts. HubSpot dedupes contacts on email automatically, so contact duplicates are usually the same person under two addresses. Merge them after companies so associations follow the surviving company.

In our experience, the companies-without-domain list is the single best predictor of how messy the first month of ZoomInfo exports will be. We like it near zero for any account a rep actively works before we connect.

Not sure how many duplicates you are carrying?

We can look at your HubSpot company and contact data and tell you what to fix before ZoomInfo touches it. Book a free 30-minute fit check.

Steps 4 to 6: personal emails, owners and lifecycle stages

Personal emails. Build a contact list where Email contains gmail.com, yahoo.com, outlook.com, hotmail.com, icloud.com and aol.com, plus any regional providers in your market. ZoomInfo's own Enrich material notes that matching relies on business email and company domain, so personal addresses often will not resolve. Keep these contacts out of Scheduled Enrich lists and decide whether they belong in the CRM at all.

Owners. Two fixes. First, reassign every record owned by a deactivated user. Second, check that each ZoomInfo user's email matches their HubSpot user email. ZoomInfo's guide says that when the emails match, new exported records are owned by the rep who exported them. When they do not, the owner becomes the admin who made the connection, which is how one admin ends up owning thousands of contacts.

Lifecycle stages. Enrichment costs credits, so you want clean labels to exclude from it. At minimum, current customers, partners, vendors, competitors and test records should be identifiable by lifecycle stage or a type property. If your stages are a mess, fix the definitions first using our HubSpot lifecycle stages guide.

StepHubSpot toolDone when
Personal emailsContact list with Email contains filtersEvery freemail contact is flagged and excluded from enrichment lists
Inactive ownersContacts and companies filtered by owner, bulk editNo active record is owned by a deactivated user
User email matchUsers & Teams, compared with ZoomInfo usersEvery ZoomInfo seat has one matching HubSpot user
Lifecycle stagesLifecycle stage and Type properties, listsCustomers, vendors, partners and junk can be excluded with one filter

Which fields will ZoomInfo values collide with?

Any field where your team typed free text and ZoomInfo will write a clean value. The usual suspects are Industry, State/Region, Country/Region, Number of Employees, Annual Revenue and Job Title. The fix is the same each time: decide which system owns the field, and give ZoomInfo its own property where you want to keep both.

  • Dropdowns need exact internal values. ZoomInfo's guide says values written to a dropdown or radio property must match valid internal values, and they are case sensitive. HubSpot does not let you edit an internal value after it is saved, so set them right the first time.
  • HubSpot's Industry field is fixed. It ships with about 150 options you cannot delete. ZoomInfo's industry labels will not line up one to one, which is why we map ZoomInfo industry into its own property.
  • Number fields reject ranges. Number of Employees is numeric in HubSpot. A text range in that field breaks reports and filters.
  • Create the ZoomInfo ID properties now. ZoomInfo asks for single-line text properties named ZoomInfo Contact ID (on contacts) and ZoomInfo Company ID (on contacts and companies), ideally in a property group called ZoomInfo Properties.

Check HubSpot's own enrichment too. If Breeze enrichment is on under Settings > Data Management > Data Enrichment, each mapped property has an overwrite rule, and a rule set to overwrite existing values can replace what ZoomInfo wrote. Pick one owner per field. The full field-by-field plan lives in our ZoomInfo to HubSpot field mapping template.

Last, turn on Create and associate companies with contacts under Settings > Data Management > Objects > Companies. For freemail contacts HubSpot falls back to the Website URL property, and you can opt out up to 1,000 domains, such as your own or a client's shared hosting domain.

How do you know HubSpot is ready?

Use a short ready test before anyone clicks Connect. These are our planning numbers, not ZoomInfo requirements, and they apply to records your team actually works.

CheckOur planning target
Worked companies with a domain95% or more
Domains shared by two or more companiesZero, or each one documented as a parent and child
Open duplicate pairs in the duplicates toolReviewed, merged or rejected
Records owned by deactivated usersZero
ZoomInfo users without a matching HubSpot userZero
ZoomInfo ID properties and property groupCreated before the first export

Then spot check five companies by hand with Actions > View property history on the record. You are looking for fields that change every week from imports or other integrations, because ZoomInfo will join that fight.

From here, the step-by-step setup guide covers the connection itself, and the full ZoomInfo HubSpot integration checklist tracks every phase through go-live.

Conclusion

ZoomInfo matches on domain and email, so those are the two fields that decide whether your integration enriches HubSpot or duplicates it. Fix domains, merge companies, then contacts, separate personal emails and line up owners before you connect, and the first month looks like progress instead of cleanup.

This prep is narrower than ongoing hygiene. Once the connection is live, the broader HubSpot data hygiene checklist and a regular integration health check keep it that way. If you would rather hand the cleanup and the ongoing data work to a team that does it daily, that is what our ZoomInfo as a Service program covers.

Want a second set of eyes on your HubSpot data first?

We will review your domains, duplicates and owners and tell you whether you are ready to connect ZoomInfo. Book a free 30-minute fit check.

Frequently Asked Questions

Should I clean HubSpot before connecting ZoomInfo?

Yes. ZoomInfo checks for existing companies by domain and contacts by email, so missing domains and duplicate records turn into new duplicates and wasted credits once reps start exporting.

How does ZoomInfo check for duplicates when exporting to HubSpot?

According to ZoomInfo's HubSpot integration guide, companies are matched on company domain. Contacts are matched on email address first, then on first name, last name and exact company name.

What HubSpot subscription do I need to merge duplicates?

Reviewing and merging duplicate pairs in HubSpot's duplicates tool needs a Professional or Enterprise subscription. Bulk merging and custom duplicate rules need Data Hub Professional or Enterprise.

Should contacts with Gmail addresses be enriched by ZoomInfo?

Usually not. Matching relies on business email and company domain, so personal addresses often fail to match. Flag them in a list and keep them out of your enrichment jobs.

Why are ZoomInfo exports owned by the admin instead of the rep?

With the service account connection, ZoomInfo assigns new records to the exporting rep only when the rep's ZoomInfo email matches their HubSpot user email. Otherwise the owner becomes the admin who made the connection.

Does ZoomInfo associate exported contacts with their companies in HubSpot?

No. ZoomInfo's guide says exported contacts arrive as independent records. Turn on HubSpot's setting to automatically create and associate companies with contacts to handle it.

How long does HubSpot data prep for ZoomInfo take?

It depends on database size and how many companies lack domains. In our experience the domain and duplicate work takes most of the time, and owners and fields are usually a day or two.

Sources & References

Related Reading from Quantum

Ready to put any of this into practice? See how ZoomInfo as a Service works →

About the Author — Shawn Peterson

CEO · Quantum Business Solutions · HubSpot Platinum Solutions Partner

Shawn has spent 20+ years architecting revenue operations for B2B organizations across office equipment, MSP and IT services. Quantum is a HubSpot Platinum Solutions Partner and a ZoomInfo Diamond partner that builds HubSpot, runs outbound email and calling programs, and helps companies get found in search and AI answers. Connect on LinkedIn →

No call required

Is your HubSpot data ready for ZoomInfo?

Tell us roughly how many companies and contacts you have and what worries you about the data, and we will reply with the three fixes we would make first. If you are ready to connect, we will say that.