ZoomInfo With HubSpot vs Salesforce: How the Integrations Differ
TL;DR: Quick Answer
ZoomInfo connects to Salesforce and HubSpot through the same Admin Portal integration, with the same field mapping and update rules, but the Salesforce side is heavier. Salesforce adds an AppExchange package with ZoomInfo custom objects, a lead object, Salesforce duplicate rules and API limits. HubSpot exports companies and contacts and stores extras like intent in custom properties.
- Salesforce lead assignment rules only fire on exports of 25 new records or fewer; in HubSpot, routing lives in workflows.
- ZoomInfo's Scoops, Intent and ZoomInfo custom objects in Salesforce have no automatic home in HubSpot. Decide what to keep before you migrate.
- Carry ZoomInfo Contact and Company IDs across in a migration. ZoomInfo uses them for matching and charging.
This page is for teams that run ZoomInfo with Salesforce today and are moving to HubSpot, or that run both CRMs and need to know where the ZoomInfo setup differs. You will get a verified side-by-side of the two integrations, what carries over in a Salesforce to HubSpot migration, and a checklist for the ZoomInfo side of the cutover. The HubSpot integration on its own is covered in our ZoomInfo HubSpot integration guide.
What is the same in both integrations?
More than most people expect. Both are configured in the ZoomInfo Admin Portal under Integrations, then Connections, and both work the same way at the core:
- Connection model. A service account connection is the default, with optional individual user connections. ZoomInfo users are mapped to CRM users so exported records get the right owner.
- Field mapping. Each mapped field is set to "Complete if missing" (the default) or "Overwrite field", and a Test Mapping button exports and deletes a test record.
- Export caps. Admins choose which objects users may export and set a per-export maximum of up to 100,000 records.
- Import. On by default for both. ZoomInfo reads CRM records the connected user can see to power Advanced Search filters and recommendations.
- Intent fields. Without a custom object, both store intent as five data points per topic (signal score, audience strength, signal location, ID and issue date), so six topics means 30 custom fields.
- Workflows and enrichment. ZoomInfo Workflows and the Enrich product (Instant and Scheduled) work with both CRMs.
So the skills transfer. The differences are in objects, routing and what lives inside the CRM itself.
ZoomInfo with Salesforce vs HubSpot, side by side
Every row below comes from ZoomInfo's own integration guides for each CRM.
| Area | Salesforce | HubSpot |
|---|---|---|
| Export objects | Accounts, contacts and leads | Companies and contacts |
| Package inside the CRM | Optional Native App from AppExchange; required before configuring Enrich | None for the platform integration |
| ZoomInfo custom objects | ZoomInfo, Scoops and Intent objects as related lists | None; use custom properties |
| ZoomInfo ID fields | Managed fields installed by the package | Custom properties you create and map |
| Duplicate checks | ZoomInfo standard checks, or your Salesforce duplicate rules | Company by domain; contact by email, then name plus exact company name |
| Assignment | Lead assignment rules only on small exports | Owner from user mapping; routing in HubSpot workflows |
| Plan requirements | Salesforce REST API; Professional edition must buy it | Free, Basic, Professional and Enterprise listed as supported |
| Connecting user | Integration user with read, setup and report permissions | Super Admin, or an admin with the listed permissions |
How do objects and custom objects differ?
Salesforce gives ZoomInfo more places to put data. People in ZoomInfo can be exported as Salesforce contacts or leads, and the Native App adds three custom objects:
- ZoomInfo object: every field available in the default mapping, shown as a related list on accounts, contacts and leads. ZoomInfo's guide says this gives users the full data for records you already purchased without spending more credits.
- Scoops object: scoops on account records.
- Intent object: intent on account records.
HubSpot has none of these. ZoomInfo's HubSpot guide lists companies and contacts as the export objects, and anything beyond standard fields goes into custom properties you create first. Our ZoomInfo to HubSpot field mapping template shows which properties to create.
The practical effect: in Salesforce, reps often browse ZoomInfo data in a related list without anyone mapping it. In HubSpot, if a field matters, someone has to decide it matters and map it. We think that is healthier, because unmapped data rarely gets used anyway.
Moving from Salesforce and worried about losing ZoomInfo data?
We will look at your Salesforce ZoomInfo setup and show you what to rebuild in HubSpot and what to let go. Book a free 30-minute fit check.
Routing, duplicates and API limits
This is where Salesforce admins get surprised.
Assignment rules
ZoomInfo's Salesforce guide says lead assignment rules fire when 25 or fewer new records are exported. At 26 or more they do not, and account exports over 25 use the Salesforce Bulk API, which also skips assignment rules. In HubSpot there is no equivalent rule to trip over: the owner comes from user mapping, and anything smarter is a HubSpot workflow. Our page on lead scoring and routing with ZoomInfo data covers that build.
Duplicates
Salesforce offers two modes: ZoomInfo's standard checking, or your own Salesforce duplicate rules, which needs Author Apex permission. HubSpot uses ZoomInfo's fixed logic: domain for companies, then email, then first name, last name and exact company name for contacts. That makes clean domains in HubSpot non-negotiable, which is why we do HubSpot data cleanup before connecting ZoomInfo.
API consumption
In Salesforce, exports of 199 records or fewer use the REST API, and 200 or more need Bulk API access. HubSpot's guide points instead to HubSpot's own API limits for the hourly incremental import, and suggests checking your daily allowance with HubSpot support.
How do the enrich options compare?
Both CRMs get the same two ZoomInfo Enrich applications: Instant Enrich, which appends data as records are created, and Scheduled Enrich, which runs jobs on a cadence. The settings differ a little.
| Setting | Salesforce | HubSpot |
|---|---|---|
| Scheduled job objects | Accounts, contacts or leads | Companies or contacts |
| Credit cap per run | Yes | Yes |
| Enrich only records already under management, at no charge | Yes, as a job option | Confirm in your Enrich settings |
| Minimum accuracy score for contacts | Yes | Yes |
| Batch size | 10,000, 1,000, 500 or 200 per call | Not listed; a criteria-based company job is capped at 10,000 companies |
HubSpot also has a separate route: the ZoomInfo Inbound Enrich app on the HubSpot Marketplace, which enriches new contacts as they arrive and needs its own subscription. Which enrich product suits which records is covered in our ZoomInfo enrichment in HubSpot guide.
What carries over when you migrate to HubSpot?
Your ZoomInfo contract, credits, users, saved searches and intent topics live in ZoomInfo, so they carry over untouched. What does not carry over is anything that lived inside Salesforce or pointed at it.
| Item | Carries over? | What to do |
|---|---|---|
| ZoomInfo values in standard fields | Yes, if your migration maps the fields | Map them like any other field |
| ZoomInfo Contact and Company IDs | Only if you migrate them | Create HubSpot properties and migrate the values |
| Salesforce leads | Not as leads | Usually contacts with a lifecycle stage; decide before cutover |
| ZoomInfo, Scoops and Intent custom objects | No | Keep the few fields you use as properties; let the rest go |
| Export mapping and update rules | No | Rebuild against HubSpot properties |
| Workflows exporting to Salesforce | No | Point each one at HubSpot |
| Scheduled Enrich jobs | No | Recreate for companies and contacts |
| Assignment rules | No | Rebuild as HubSpot workflows |
The IDs are the item teams skip and regret. ZoomInfo's Enrich guide describes the Contact and Company IDs as important for matching and charging, so losing them means rematching every record. For the CRM migration itself, our Salesforce to HubSpot migration service handles objects, history and automation, and our HubSpot vs Salesforce comparison covers the decision.
Migration checklist for the ZoomInfo side
Run this alongside the CRM migration plan, not after it.
- Inventory. Export the Salesforce mapping, update rules, Workflows, Scheduled Enrich jobs and intent topics.
- Pick what survives. List the ZoomInfo fields reps and reports actually use. Everything else stays behind.
- Create HubSpot properties. ZoomInfo Contact ID, Company ID, the intent fields you keep, and Workflow Name.
- Migrate IDs with records. Check a sample of 50 after the load.
- Decide on leads. Map Salesforce lead status to HubSpot lifecycle stage and lead status.
- Pause Salesforce automation. Turn off Workflows and Scheduled Enrich jobs that write to Salesforce at cutover so nothing writes to the old CRM.
- Connect HubSpot. Use a Super Admin service account and map every ZoomInfo user to a HubSpot user. Our step-by-step setup guide covers it.
- Rebuild mapping and test. Use Test Mapping, then export ten real records.
- Repoint Workflows and enrichment. Start each with a low credit cap.
- Retire Salesforce last. Disconnect the Salesforce integration only after a week of clean HubSpot exports.
For the full pre and post go-live list, use our ZoomInfo HubSpot integration checklist. If you want both platforms handled in one project, our ZoomInfo consulting team runs the ZoomInfo side while the HubSpot migration runs.
Conclusion
ZoomInfo treats Salesforce and HubSpot as close cousins: the same Admin Portal, mapping rules, Workflows and Enrich products. The differences sit in the CRM: Salesforce has leads, a managed package with ZoomInfo custom objects, configurable duplicate rules and assignment rule thresholds; HubSpot keeps it to companies, contacts and properties.
In a migration the ZoomInfo contract carries over and the configuration does not. Inventory it, keep the IDs, choose the few fields that matter, and rebuild routing in HubSpot workflows.
Planning a Salesforce to HubSpot move with ZoomInfo in the stack?
We handle both platforms and can map the ZoomInfo side into your migration plan. Book a free 30-minute fit check.
Frequently Asked Questions
Is the ZoomInfo integration different for HubSpot and Salesforce?
The core is the same: both are set up in the ZoomInfo Admin Portal with the same mapping and update rules. Salesforce adds a lead object, an optional AppExchange package with ZoomInfo custom objects, configurable duplicate rules and assignment rule limits.
Can ZoomInfo export leads to HubSpot?
ZoomInfo's HubSpot guide lists companies and contacts as export objects. Teams usually use a contact with a lifecycle stage where Salesforce would use a lead.
Do ZoomInfo custom objects move from Salesforce to HubSpot?
No. The ZoomInfo, Scoops and Intent objects come from ZoomInfo's Salesforce package. In HubSpot you keep the fields you need as custom properties.
Why do ZoomInfo exports to Salesforce skip lead assignment rules?
ZoomInfo's guide says lead assignment rules only fire when 25 or fewer new records are exported, and larger account exports use the Bulk API, which skips them. Plan owner assignment for big exports separately.
Do I lose ZoomInfo credits when I switch CRMs?
No. Credits belong to your ZoomInfo contract, not the CRM. Migrate ZoomInfo Contact and Company IDs so records match cleanly in HubSpot.
Can I connect ZoomInfo to Salesforce and HubSpot at the same time?
The Admin Portal lists each CRM as its own connection, so you can connect HubSpot before disconnecting Salesforce. Confirm with your ZoomInfo admin which CRM users export to during the overlap.
Sources & References
- ZoomInfo: Salesforce Integration Guide (PDF)
- ZoomInfo: HubSpot Integration Guide (PDF)
- ZoomInfo: Enrich for Salesforce Integration Guide (PDF)
- ZoomInfo: Enrich for HubSpot Integration Guide (PDF)
Related Reading from Quantum
- ZoomInfo HubSpot Integration Checklist
- ZoomInfo Workflows vs HubSpot Workflows
- HubSpot vs Salesforce: Best B2B CRM in 2026
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
Moving from Salesforce to HubSpot with ZoomInfo in your stack?
Tell us how ZoomInfo is set up in your Salesforce org today and we will reply with what to rebuild in HubSpot and what to leave behind. If your setup moves over cleanly, we will say that.


