---
title: "HubSpot and ZoomInfo integration: what syncs, and what it needs"
description: "HubSpot and ZoomInfo: what moves, in which direction, which plan carries it, and the limits that bite. Verified October 2026."
url: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-integration
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# HubSpot and ZoomInfo

Featured

Enrichment the moment a record is created, with the two-way half sold one edition up.

Checked by **Reverse Contact** · Verified 2026-10-11 · No paid placement

## What you have to buy first

ZoomInfo Advanced for the native sync, Elite for two-way sync and intent fields

## What moves

Contacts, Companies, Lists, one way, in.

Inbound Enrich is the part worth buying. A record appears in HubSpot from a form, an import or a rep typing it, and it comes back filled in, with field mapping you control so it does not flatten what someone already entered. The parts teams assume are included, two-way sync and intent fields, sit on Elite. Price this on the edition rather than on the integration, because the integration costs nothing and the edition is most of your bill.

## What actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

| What | Direction | What that means in practice |
| --- | --- | --- |
| New contacts | One way, in | Enriched on creation with title, department, seniority and contact fields, subject to your mapping. |
| New companies | One way, in | Firmographics written to company properties on creation. |
| Existing records | One way, in | Scheduled bulk enrichment keeps the back catalogue current rather than only new rows. |
| Account lists | One way, in | With Copilot and Account Fit Score, high-fit accounts can push into HubSpot lists on a daily schedule. |
| Everything back to ZoomInfo | Both ways | Elite only. On Advanced this integration is a one-way enrichment pipe. |

One of those five rows moves in both directions. The four that do not are New contacts, New companies, Existing records and Account lists, and those are the rows that decide how you design around this rather than the ones in the brochure.

## Which field lands where

Mapping is explicit and per field, with its own behaviour on each. The part that surprises people is that company mapping is configured in the same screen as contact mapping and fails independently of it.

| In HubSpot | In ZoomInfo | What to know about the match |
| --- | --- | --- |
| A ZoomInfo contact field | `The HubSpot contact property you choose` | With an export behaviour set per field, which is where overwrite is decided. |
| A ZoomInfo company field | `The HubSpot company property you choose` | Configured alongside contacts and reported in the wild as populating less reliably. Test companies separately. |
| A record ZoomInfo matches to an existing one | `A duplicate flag at export time` | The rep then chooses from whatever options the admin left available, including creating the duplicate anyway. |
| Your HubSpot data | `ZoomInfo, for analysis` | HubSpot Import is enabled by default and lets ZoomInfo import and analyse information about your team, prospects and customers. |

### What does not cross

A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

- Anything, if the connecting account cannot see it. Permissions on the service account cap the whole integration.
- Intent and two-way sync, below the ZoomInfo edition that carries them. Those are a contract question rather than a configuration one.

Every row above travels as a file: four field mappings and two documented exclusions, each one's note, and the two vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

The last row in the first table is the one to raise internally: it is the only mapping on this page that moves your data outward rather than theirs inward, and it is on unless you turn it off.

## Which edition carries this, and whose

ZoomInfo lists Free, Basic, Professional and Enterprise as supported HubSpot plans, so the columns below are identical on purpose: HubSpot gates nothing here. The gate is entirely ZoomInfo's, and ZoomInfo quotes rather than publishes, which is why the rows are the expensive axis. Pick one on each side and the grid marks the answer.

| ZoomInfo edition | Free or Starter | Professional | Enterprise |
| --- | --- | --- | --- |
| Below Advanced | No native sync | No native sync | No native sync |
| Advanced | One-way enrichment | One-way enrichment | One-way enrichment |
| Elite | Plus two-way sync and intent | Plus two-way sync and intent | Plus two-way sync and intent |

- **No native sync** — The native integration is not available. Whatever HubSpot plan you hold makes no difference to this row.
- **One-way enrichment** — Inbound Enrich as records are created, scheduled enrichment over the back catalogue, and export from ZoomInfo into HubSpot. One direction.
- **Plus two-way sync and intent** — The same, plus two-way sync and intent fields, which are the features teams most often assume are included.

Counted off that grid, of nine pairings: three give you no native sync, three give you one-way enrichment, three give you plus two-way sync and intent. Reading this grid horizontally is the point: moving along a row buys you nothing, so an upgrade conversation with HubSpot will not fix a capability gap here, and the only lever is a renegotiation with ZoomInfo.

## How to connect HubSpot to ZoomInfo

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

- **Who has to do it** — A ZoomInfo admin with the Admin Portal, and a HubSpot Super Admin or an admin carrying the CRM object permissions below.
- **How long it takes** — An afternoon, and one decision at the start that is awkward to change later.

ZoomInfo Admin Portal

ZoomInfo offers a service account connection, which is the default and its preferred option, or individual user account connections. With a service account every export and every HubSpot filtering job runs through one account, which is why ZoomInfo recommends it: nobody has to troubleshoot a departed rep's connection.

HubSpot: Settings, Users and Teams, Edit permissions

Under CRM objects, contacts need View, Edit and Delete. ZoomInfo gives a minimum of "contacts they own" and recommends "all contacts", and the same pattern applies to companies. A service account on the minimum will quietly export less than you asked for.

ZoomInfo Admin Portal: Integrations, HubSpot

Connect as a HubSpot Super Admin, or as an admin user holding the permissions above. Everything after this inherits that account's reach.

Integration settings: HubSpot Import

ZoomInfo documents this as enabled by default, letting it import and analyse information about your team and your prospects and customers from HubSpot. Whether that is fine is a question for whoever owns your data agreements, and the default answers it for them unless somebody looks.

Integration settings: Export Mapping

Each ZoomInfo field is paired with a HubSpot field and given a behaviour for export. This is where enrichment either respects what a rep typed or flattens it, and it is the step people skim.

Admin Portal: duplication settings

The admin sets the default behaviour when an export hits a duplicate. Reps are then shown the flag during export and can update the existing record, create a duplicate, or take whichever other options you left open. Leaving all of them open means the CRM's duplicate policy is decided one rep at a time.

Admin Portal: user enablement

Only after mapping and duplicate settings are agreed. Enabling export first and configuring afterwards means the first week of exports was the test run, in production.

Two of those seven are the ones to get right: the connection model, which decides who can fix it later, and the duplicate policy, which decides what the CRM looks like in six months.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at [this pair as a skill](https://www.reversecontact.com/integrations-hub/skills/hubspot-zoominfo.md) and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/hubspot-zoominfo/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-zoominfo.md

## What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

- **The edition is the integration** — Native HubSpot sync starts at ZoomInfo Advanced. Two-way sync and intent fields are Elite. There is no configuration that moves a feature down a tier, so the evaluation question is which edition, not which integration.
- **Enrichment is a write, and writes overwrite** — Field mapping is the whole configuration here. Point ZoomInfo at a property a rep maintains and it will win. Map to dedicated ZoomInfo properties and let your workflows decide what gets promoted to the fields people trust.
- **Watch what it does to source reporting** — Anything that writes to a record on creation sits close to the properties original-source attribution depends on. Keep enrichment away from source fields unless you have decided, deliberately, that it should own them.
- **It needs admin on both sides** — Setting up the native integration requires admin access in HubSpot and in ZoomInfo. On the ZoomInfo side that is usually the person who owns the contract, not the person who uses it.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

## The 6 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

### Contact fields populate and company fields do not

WhyCompany mapping is configured in the same place and behaves independently, and practitioners report exactly this asymmetry with mappings that look correct in the Admin Portal.

Check the connecting account's permissions on companies specifically, not just on contacts, then re-test with a single company export.

### Exports reach fewer records than expected

WhyThe connecting account is on the minimum permission of records they own rather than all records.

Raise the permission to the recommended level on both contacts and companies. ZoomInfo documents both the minimum and the recommendation, and the gap between them is silent.

### Duplicates are piling up after exports

WhyThe admin left the create-a-duplicate option available, and reps in a hurry take it.

Restrict the duplicate options in the Admin Portal so updating the existing record is the path of least resistance.

### The integration broke when somebody left the company

WhyIndividual user account connections tie the integration to people.

Move to the service account connection, which ZoomInfo describes as the default and preferred option for exactly this reason.

### Nobody authorised ZoomInfo to read the CRM

WhyHubSpot Import is enabled by default and allows ZoomInfo to import and analyse information from HubSpot about your team and your prospects and customers.

Decide it deliberately and record who decided. This is a data-sharing setting rather than a performance one, so the person to ask is not the CRM admin.

### Reps complain the data overwrote their notes

WhyExport behaviour on those field mappings.

Change the behaviour per field. The mapping screen allows it and the default is not always what a rep would choose.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The [same symptom on another pair](https://www.reversecontact.com/integrations-hub/errors) is often the same cause, so the directory indexes all of them by the message rather than by the integration.

## When this is the right integration

### Set it up when

- Inbound forms return an email and nothing else you can route on
- Your CRM has thousands of records with no headcount or industry
- Someone needs a defensible account list rather than a rep's guess

### Do not bother when

- You are on a ZoomInfo edition below Advanced
- Your properties are maintained by reps and you cannot decide what wins
- Coverage outside North America is the reason you are enriching

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

## What practitioners say about it

Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

### Company fields are the ones that quietly do not arrive

> In zoominfo's admin portal where the integration with hubspot lives, all the company fields are set up and mapped correctly, but they are not being populated in hubspot's company profile.

[r/hubspot](https://www.reddit.com/r/hubspot/comments/1jzw8gx/zoominfo_company_fields_not_mapping_to_hubspot/) · April 2025 · 3 points

A mapping that looks right in the Admin Portal and produces nothing in HubSpot. The first thing to check is the connecting account's permission on companies, because ZoomInfo documents a minimum of records the user owns and a recommendation of all records, and contacts can be fine while companies are not.

### The workaround people reach for is a custom property

> How about creating a custom property that can store the info? Something like a dropdown select or multiple choice depending if they are allowed to be part of multiple buckets

[r/hubspot](https://www.reddit.com/r/hubspot/comments/1ow12ri/ughh_zoom_info_to_hubspot/) · November 2025 · 3 points

Good instinct, and it is the same advice this directory gives on every enrichment pair: give the vendor its own properties rather than letting it write into the ones people type in. The mapping screen supports exactly that.

### Every connector is configuration that does not travel

> I am guessing the configuration for all these 3rd party tools is different between Hubspot and Salesforce. Unless the connectors/plugins for both of these CRMs are super rigid and have no settings, its likely this is going to be a dumpster fire.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1b8bcwg/tech_stack_migration_from_hubspot_to_sfdc/) · March 2024 · 7 points

Said about a CRM migration with ZoomInfo in the stack, and it is right. The field mapping and duplicate policy on this page are the kind of thing nobody writes down, which is what makes a CRM change expensive long after the records have moved.

### The stack this sits in is the familiar one

> Everything goes into salesforce. Hubspot gives you marketing data. Joe fills out a form saying his company has 50 employees and he is interested in product a and c. That flows into salesforce as a lead.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1b811h8/salesforce_hubspot_zoominfo/) · March 2024 · 4 points

A reminder that this integration is usually one of three or four writing to the same records. Whatever you decide about overwrite behaviour here, something else is also writing, and the two policies have to agree.

### People are still asking which integration to struggle with

> Curious what integration headaches HubSpot users are dealing with that the native features just cannot solve

[r/hubspot](https://www.reddit.com/r/hubspot/comments/1w0vt79/what_one_hubspot_integration_youre_currently/) · August 2026 · 3 points

Worth noting what does not appear in the answers: this pair. The complaints about ZoomInfo are commercial rather than technical, which is consistent with everything else on this page.

What the threads add up to

Thin and specific. There is no great debate about this pair, which fits a package that mostly works; what surfaces instead is one recurring configuration failure and a general wariness about how many third-party connectors a CRM ends up carrying. The most useful thread in the set is a single unanswered question about company fields.

The absence of noise is itself the finding. When this integration disappoints it is because of a setting somebody skipped, and all four of those settings are in the list above.

## The longer answer

Inbound Enrich is the clearest example in this directory of an integration that changes how a team works rather than what it sees. A form that collects an email and a company name is a routing problem: nobody can assign it, score it or decide whether it matters. The same record enriched at creation carries headcount, industry and seniority, and every routing rule you wanted to write becomes writable.

The trap is treating that as free. The integration is free; getting to the edition that carries it is not, and the number only comes back as a quote. That makes this pair harder to evaluate than it looks, because you cannot model the cost per enriched record the way you can with a metered API. What you can do is count the records that would be enriched in a month and ask for the quote against that number.

The other thing worth deciding early is what enrichment is allowed to own. The safest pattern is to write every enriched value to its own property, never to the ones reps type into, and then use a workflow to promote a value only where the rep field is empty. It takes an afternoon longer to set up and it removes the argument that otherwise arrives in month three.

## If this is not the one

The integrations people compare this against, or set up alongside it.

Split a stack into layers and this pair sits on two of them: the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm), which 33 of the 68 integrations here touch, and the [data layer](https://www.reversecontact.com/integrations-hub/stack/data), which 26 do.

[**HubSpot and LinkedIn**Two-way, genuinely useful, and only on the Sales Navigator edition nobody quotes you first. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-linkedin-integration)[**HubSpot and Reverse Contact**A whole record from an email or a domain, by four routes, and only the in-CRM one needs Data Hub. One way, in](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-reverse-contact-integration)[**HubSpot and ClickUp**The rare pair where each vendor built the half that runs inside the other. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clickup-integration)

## [Reverse Contact](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-10-11
- **Sources** — 2 vendor documents
- **Paid placement** — None

### Read from

- [ZoomInfo University: integrations and implementations](https://university.zoominfo.com/page/integrations-implementations)
- [ZoomInfo: HubSpot integration guide (PDF)](https://tech-docs-library.zoominfo.com/hubspot-integration-guide.pdf)

## HubSpot and ZoomInfo, asked and answered

### Which ZoomInfo plan do I need for the HubSpot integration?

Native HubSpot sync starts at ZoomInfo Advanced. Two-way sync and intent fields are an Elite feature. The integration itself costs nothing; the edition that carries it is most of your bill, and ZoomInfo quotes rather than publishes those numbers, so price the edition rather than the connector.

### Does ZoomInfo enrich HubSpot records automatically?

Yes. Inbound Enrich fires when a contact or company is created in HubSpot from a form, an import or a rep typing it, and fills the fields you have mapped. Scheduled bulk enrichment covers records that already exist, so the back catalogue does not stay stale while new rows get the good treatment.

### Will it overwrite what my reps have entered?

It will if you map it that way, and the defaults often do. Point ZoomInfo at its own dedicated properties rather than at the fields people type into, then use a HubSpot workflow to promote a value only where the rep field is empty. That costs an afternoon and removes the entire class of problem.

### Does it affect HubSpot lead attribution?

It can. Anything writing to a record on creation is operating close to the properties original-source attribution depends on. Keep enrichment away from source fields unless you have decided deliberately that it should own them, and check your first-touch reporting after the first week rather than after the first quarter.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant
