---
title: "Salesforce and ZoomInfo integration: what syncs, and what it needs"
description: "Salesforce 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/salesforce-integrations/salesforce-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)

# Salesforce and ZoomInfo

Featured

Enrichment on creation and on a schedule, and a sandbox that charges you to test.

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

## What you have to buy first

ZoomInfo Sales with Enrich, the AppExchange package, and a Salesforce edition with API access

## What moves

Contacts, Companies, Lists, one way, in.

This is the deepest enrichment integration in the directory and the one with the most ways to spend money you did not plan to. The capability is real: Instant Enrich fills a lead, contact or account as it is created, Scheduled Enrich keeps the back catalogue current, and you control matching, accuracy thresholds and field-level overwrite behaviour. What decides whether the project goes well is three documented details nobody mentions in a demo: a sandbox run charges credits exactly like production, the Person Has Moved setting rewrites employers unless you turn it off, and Instant Enrich spends two Salesforce API calls on every record it touches. That last allocation is shared with every other integration in the org, which is why this one usually gets discovered from somewhere else.

## 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 leads, contacts and accounts | One way, in | Instant Enrich appends ZoomInfo data as the record is created, optionally filtered by a SOQL query so only the right teams' records are enriched. |
| Existing records | One way, in | Scheduled Enrich jobs run on a cadence over all records, a list view, or criteria you define. Jobs begin at 12:00 AM Eastern on the scheduled day. |
| Intent and Scoops | One way, in | Written to a ZoomInfo custom object rather than onto the standard record. |
| Buying committee contacts | One way, in | Creates and enriches new contacts on matched accounts, charged as credits and reported separately on the dashboard. |
| Anything back to ZoomInfo | One way, out | Nothing on this integration. Enrich is a one-way pipe into Salesforce. |

Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.

## Which field lands where

Mapping here is explicit and per field, which is unusually controllable. The thing to understand is not where a field lands but whether it is allowed to overwrite what is already there.

| In Salesforce | In ZoomInfo | What to know about the match |
| --- | --- | --- |
| A ZoomInfo data point | `Any Salesforce field, custom included` | Chosen row by row, so nothing lands anywhere you did not pick. |
| Update Option | `Overwrite, or complete only if missing` | Set per mapping. This single column is the difference between enrichment that reps trust and enrichment they work around. |
| Intent and Scoops | `A ZoomInfo custom object` | Deliberately not written onto the standard record, so your reporting has to reach into the custom object to use them. |
| Buying committee contacts | `New contacts on the matched account` | Created rather than matched, and chargeable. A hard limit of up to 10 contacts per account is available and worth setting. |
| Anything at all | `Back to ZoomInfo` | Nothing. Enrich is a one-way pipe into Salesforce, so your corrections stay yours and never improve the source. |

### What does not cross

Three 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.

- Any record below your accuracy threshold. It is marked No Match with the reason given, which is a feature rather than a gap.
- A contact with no account relationship, usefully. Salesforce treats an account-less contact as private to its creator, so a created contact that lands without an account is invisible to the rest of the team.
- Anything flowing back. There is no return path, so a field a rep corrects is corrected only in Salesforce.

Every row above travels as a file: five field mappings and three 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.

Work down the Update Option column before go-live rather than the field list: the mapping decides what arrives, and that column decides whether it is welcome.

## What each enrichment mode costs you

ZoomInfo quotes its editions rather than publishing them, so the grid that decides this project is not licence against licence. It is which enrichment mode you run against which environment, because both sides meter you and only one of them is obvious. Pick one on each side and the grid marks the answer.

| Enrich mode | Production | Sandbox |
| --- | --- | --- |
| Instant Enrich, on create | Two API calls per record | Credits charged anyway |
| Scheduled Enrich, 200 per batch | Most Bulk API calls | Credits charged anyway |
| Scheduled Enrich, 10K per batch | Fewest Bulk API calls | Credits charged anyway |

- **Two API calls per record** — ZoomInfo documents two Salesforce API calls for every record Instant Enrich touches as it is created. At form-fill volumes that is the line item people forget when they size their API allowance.
- **Most Bulk API calls** — The smallest batch size makes the most Bulk API calls for the same number of records. Choose it only if something in your org genuinely cannot take a larger transaction.
- **Fewest Bulk API calls** — The largest batch size makes the fewest calls and is the default choice unless you have a reason. The records enriched and the credits charged are identical either way.
- **Credits charged anyway** — A sandbox run consumes credits exactly as production does. There is no free rehearsal, so test with ten records rather than with a copy of the database.

Counted off that grid, of six pairings: one gives you two API calls per record, one gives you most Bulk API calls, one gives you fewest Bulk API calls, three give you credits charged anyway. The two meters do not move together, which is the trap: tuning the batch size down to be gentle on one system spends more of the other, and neither shows up on the invoice you were watching.

## How to connect Salesforce 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 Salesforce admin who can install a package, and a ZoomInfo admin with the Admin Portal. Plus one dedicated Salesforce user that nobody logs in as.
- **How long it takes** — An hour to connect. The field mapping and the accuracy threshold are the decisions, and they deserve a meeting.

Salesforce AppExchange: ZoomInfo, GTM Intelligence Platform

Click Get It Now and choose Production or Sandbox. ZoomInfo documents that running Enrich in a sandbox still consumes credits, so a sandbox trial is a real purchase rather than a free rehearsal.

Salesforce: Users

ZoomInfo asks you to connect as a user dedicated to Enrich. That user's permissions become the integration's permissions, and a named person's account takes the integration down with them when they leave.

ZoomInfo Admin Portal: Integrations, Connect Enrich

Under Scheduled Enrich, click Connect on the Salesforce tile, choose the environment and click Grant Access. The authorisation opens in a popup, so a popup blocker makes this look like a failed connection rather than a blocked window.

Admin Portal: Manage, New Job

A job takes a single Object Type of Accounts, Contacts or Leads. Name it, decide whether you want email alerts, and set the recurrence; jobs start at midnight, so a daily job is an overnight job.

The job: Credit Usage Limits

The default is No limit, which enriches every record in the run and charges for all of it. Limiting credits per job run is the setting that turns a misconfigured filter into a small mistake instead of a month of budget.

The job: Batch Size

The options are 10K, 1K, 500 and 200 records per Bulk API call. A larger batch means fewer calls; reducing it increases Salesforce API consumption, which matters because that allowance is shared with every other integration in the org.

The job: Accuracy Score for Enrichment

Records matched below the threshold are not enriched and are marked No Match with the reason Below selected Accuracy Score. That is a better outcome than a confident guess, and it is also the number somebody will use to judge the integration later.

The job: field mapping

Each row pairs a ZoomInfo field with a Salesforce field, custom fields included, and each has an Update Option of overwrite or complete only if missing. Default to complete if missing on anything a human types into.

Two of those eight are the whole project: the credit limit, which caps the downside, and the overwrite option, which decides whether reps keep trusting the record.

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/salesforce-zoominfo.md) and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/salesforce-zoominfo/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-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 sandbox is not free** — ZoomInfo states that running Enrich in a Salesforce sandbox incurs bulk credit charges in the same way as production, and recommends testing in small batches. Teams used to rehearsing data projects against a full sandbox copy should not do that here. Size your test as a sample, and get your implementation specialist involved before any job points at the whole database.
- **Person Has Moved rewrites employers by default** — The setting is enabled unless you turn it off, so a contact who changed jobs is enriched to their new organisation inside your CRM. Turn it off and the company fields are still enriched as though no move happened, with the enrich status set to Company Match Only. Either choice is defensible; not making the choice means your CRM quietly disagrees with your historical reporting about who worked where.
- **Instant Enrich costs two API calls a record** — ZoomInfo documents two Salesforce API calls per record enriched: one to read the existing field values so the update option can be honoured, and one to write. Salesforce allocates 100,000 requests plus 1,000 per Salesforce licence per 24 hours on Enterprise and on Professional with API access, shared across every integration in the org, so a busy inbound week is measurable against that number rather than invisible.
- **A smaller batch size costs more API calls** — Scheduled Enrich queries through the Bulk API in batches of 10,000 by default, and you can reduce that to 1,000, 500 or 200. ZoomInfo is explicit that reducing it increases Salesforce API consumption. The instinct to be gentle on the org by shrinking batches therefore does the opposite, and the right lever for caution is the credit limit per job run, not the batch size.

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 7 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.

### The connection window never appeared

WhyA popup blocker. ZoomInfo opens the Salesforce authorisation in a popup and says so.

Disable the blocker for the Admin Portal and reconnect. Nothing is wrong with the credentials.

### Credits went in a single run

WhyCredit Usage Limits defaults to No limit, so the job enriched every record it matched.

Set a per-run credit limit before the next schedule, and test any new filter against ten records first.

### Created contacts are invisible to everybody except one user

WhyA Salesforce contact with no account relationship is private to its creator, which is Salesforce behaviour rather than ZoomInfo behaviour.

Make sure created contacts attach to an account. Practitioners use a placeholder account everyone can see, or route to the Lead object instead.

### Records come back as No Match in bulk

WhyThey matched but fell below the accuracy threshold, and the reason field says so.

Read the reason before lowering the threshold. A lower score buys coverage with confidence, and that trade should be a decision rather than a reflex.

### Reps say the data is wrong and they fixed it last week

WhyAn Update Option set to overwrite on a field people type into, or Person Has Moved rewriting an employer.

Switch those mappings to complete only if missing, and check the Person Has Moved setting, which is on unless somebody turned it off.

### Other integrations in the org started failing

WhySalesforce API consumption. Instant Enrich costs two calls per record and a small batch size multiplies scheduled calls, all drawn from one shared daily allowance.

Raise the batch size, narrow the job filters, and check the org's API usage rather than ZoomInfo's job log, because the failure appears somewhere else entirely.

### A feature in the guide is missing from your org

WhySome capabilities need the ZoomInfo Sales native application at version 1.33 or higher.

Upgrade the AppExchange package before raising a support ticket about a missing screen.

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 records arrive with an email and nothing you can route on
- Thousands of accounts hold no headcount, industry or location
- You need a defensible account list rather than a rep's guess

### Do not bother when

- Your Salesforce edition has no API access and no budget for it
- Nobody has decided which fields enrichment is allowed to own
- 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 2018 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.

### A created contact with no account is invisible to the team

> You can create a contact without an account relationship, but the issue is I believe (off hand) that when there is no account assigned, the contact is seen as private to the creating user and not visible to others (outside of view all and modify all).

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1d0537i/how_do_i_let_zoominfo_create_contacts_in/) · May 2024 · 5 points

Salesforce behaviour rather than ZoomInfo behaviour, and it is the one that makes a successful enrichment run look like a failed one. The reply underneath suggests a placeholder account everyone can access, or using the Lead object instead.

### One person reports a contract term worth checking in your own

> You do not own the contacts from them and they will actively try to sue you if you keep the contacts after your contracts expires and you don't renew.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1iyu4g5/is_it_possible_to_have_zoom_info_automatically/) · February 2025 · 4 points

One practitioner's account of their own agreement, not a published term, and this directory is not going to assert it as one. It is worth raising because it is checkable: data ownership after termination is a clause in your contract, and the time to read it is before you write that data across every record in the CRM.

### What you can do is partly a conversation, not a setting

> I feel like you need to have an actual conversation with your account manager about what the business needs. Everything you described is doable with zoominfo but you have to let them know you need this

[r/sales](https://www.reddit.com/r/sales/comments/1nfa931/best_zoominfo_alternatives_for_enriching/) · September 2025 · 4 points

Consistent with a vendor that quotes rather than publishes. It also means a capability gap you hit on this page may be a commercial question rather than a technical one, which is a different meeting and a different budget.

### The install is not where the months go

> My company is on an older instance of SFDC, but they are saying that it will take "months" to integrate ZoomInfo with SFDC. I'm calling BS.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/7zjkhz/is_it_hard_to_integrate_zoominfo_with_sfdc/) · February 2018 · 5 points

Mostly right, and the instinct is still correct eight years later: the package install is an afternoon. What takes a quarter is agreeing the field mapping, the overwrite rules and the accuracy threshold, which is organisational work wearing a technical costume.

### People reach for enrichment because the alternative is two months of typing

> My new company just assigned me around 400 new accounts however none of them have any up to date contacts listed. It would take me at least 2 months to manually enter all these contacts.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/mnjgl5/new_account_executive_trying_to_import_contacts/) · April 2021 · 4 points

A clean statement of the value, and the reason the credit limit matters: the same impulse that makes 400 accounts worth enriching makes 40,000 look tempting at two in the morning.

What the threads add up to

Two topics dominate and neither is the integration itself. One is Salesforce's own object model getting in the way of contacts ZoomInfo creates. The other is commercial: what the data costs, what you are allowed to keep, and whether the account manager has to be in the room for you to get what you are paying for. The mechanics, by contrast, barely come up, which fits a package install that works.

Nothing in the threads suggests the integration fails. The complaints are about what it writes, what it costs and what you are allowed to keep, which is where the settings above are pointed.

## The longer answer

The configuration that decides whether this project is remembered fondly is field mapping, and ZoomInfo's own recommendation is the right one: set every standard Salesforce field to Complete if missing, which is the default, and reserve Overwrite for custom fields created specifically for ZoomInfo. That single rule prevents the argument that otherwise arrives in month three, when a rep finds a title they corrected has been replaced by a machine. Give the external source its own properties, then let a Salesforce admin decide with a flow or a formula what gets promoted into the fields people trust.

The accuracy threshold is the second control worth understanding before the first job, because it changes what a failure looks like. Set a minimum accuracy score and matched records that fall below it are not enriched and are marked No Match with the reason "Below selected Accuracy Score". That is a much better outcome than a confident guess, and it is also a number that will appear in a dashboard someone uses to judge the integration. Agree what the threshold is and why, so the match rate conversation happens once rather than every month.

None of this is unique to ZoomInfo, which is the useful thing to take from the page. Every enrichment integration in the [data layer](https://www.reversecontact.com/integrations-hub/stack/data) raises the same three questions: which fields may it own, how confident must it be before it writes, and what happens when the person has moved on. The difference here is that ZoomInfo exposes all three as settings and documents what the defaults do, which is more than most. If the Salesforce edition or the credit model is the obstacle rather than the data, the same job can be assembled through [the Salesforce data layer](https://www.reversecontact.com/integrations-hub/workflows/salesforce-data-layer) build, with a different cost shape and considerably more work.

## 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 ZoomInfo**Enrichment the moment a record is created, with the two-way half sold one edition up. One way, in](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-integration)[**HubSpot and Salesforce**Two CRMs, one connector, and an edition requirement on both sides. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration)[**Salesforce and LinkedIn**The original CRM Sync target, with the same Advanced Plus gate. Two-way sync](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-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: Enrich for Salesforce integration guide (PDF)](https://tech-docs-library.zoominfo.com/enrich-for-salesforce-integration-guide.pdf)
- [Salesforce developer limits and allocations quick reference (PDF)](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf)

## Salesforce and ZoomInfo, asked and answered

### What do I need to run ZoomInfo Enrich on Salesforce?

Enrich is a feature of ZoomInfo Sales, so the edition is the purchase and the connector is free. On the Salesforce side you install the ZoomInfo native application from the AppExchange, which ships the managed ZoomInfo Contact ID and Company ID fields that mapping depends on, and you grant the connecting user API Enabled, Apex REST Services, Customize Application, View Setup and Configuration, read and write on Account, Contact and Lead, and field-level security on every field you intend to map.

### What is the difference between Instant Enrich and Scheduled Enrich?

Instant Enrich fills a lead, contact or account at the moment it is created in Salesforce, which is the half that changes how routing works. Scheduled Enrich runs jobs on a cadence over records that already exist, so the back catalogue does not stay stale while new rows get the good treatment. They are configured separately and most teams need both, for different reasons.

### Does testing in a Salesforce sandbox cost credits?

Yes, and this is the most expensive surprise on the pair. ZoomInfo documents that using Enrich in a sandbox incurs bulk credit charges exactly as production does, and recommends testing in small batches. A full-volume rehearsal against a sandbox copy of your database is therefore a real invoice, not a dry run. Plan the test as a sample and talk to your implementation specialist before pointing a job at everything.

### Will enrichment change a contact's employer?

By default, yes. The Person Has Moved setting is enabled unless you disable it, and when ZoomInfo sees that somebody has changed organisations it enriches the record to the new one. Disable it and the person's record keeps the old company while the company fields are still enriched as though they had not moved, with the status set to Company Match Only. Neither behaviour is wrong, but one of them silently rewrites who your contacts work for, so decide deliberately before the first job runs.

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
