Apollo and Salesforce

Six hours to configure it, then it turns itself on whether or not you finished.

What you have to buy first

Apollo Basic or above, a Salesforce edition with API access, and a Salesforce admin

What moves

Contacts, Companies, Deals, Activities, two-way sync.

The deepest engagement-to-CRM sync in the directory, and the one with the most self-starting behaviour. Apollo pushes contacts, accounts, deals and activity into Salesforce in real time once enabled, with per-object settings and field mapping you control. Three documented behaviours decide whether the first month is calm: the configuration window is six hours and then syncing enables itself, push settings govern only net new contacts because updates to existing ones push regardless, and pushing any contact creates its account whether or not you asked, because Salesforce requires one.

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.

WhatDirectionWhat that means in practice
Contacts and leads One way, out Net new contacts push on save, with field mapping you configure. Updates to existing contacts push automatically whatever the push settings say.
Accounts One way, out Created or updated whenever a contact is pushed, even with Push accounts off, because Salesforce requires every contact to link to an account.
Deals Both ways Full bidirectional, or pull-only, or push-only. With bidirectional on, Salesforce is the source of truth for deals that have already synced.
Activities One way, out Emails, tasks, notes, meeting summaries and phone calls, each configured separately so you choose what reaches the CRM.
Salesforce records into Apollo One way, in Pull settings bring records back, and can infer accounts where your org works in leads.
Custom objects One way, in Read only. Organization plans can configure up to ten, and the data cannot trigger Apollo workflows.

One of those six rows moves in both directions. The five that do not are Contacts and leads, Accounts, Activities, Salesforce records into Apollo and Custom objects, and those are the rows that decide how you design around this rather than the ones in the brochure.

Which field lands where

There are five objects to configure and the settings on them are not symmetrical. Two of the five behave differently from how their own switch reads, which is the whole reason this section exists rather than pointing at the mapping screen.

In ApolloIn SalesforceWhat to know about the match
Contacts Salesforce contacts or leads, your choice Push based on certain stages is available here and only here. A contact with no stage is not pushed unless you explicitly include No stage in the selection.
Leads Salesforce leads If your org works in leads, contacts associate with leads rather than accounts. Apollo can infer accounts for you in the pull settings instead.
Accounts Salesforce accounts, whether or not you asked Pushing a net new contact creates or updates its account even with Push accounts off, because Salesforce will not accept a contact without one.
Deals Salesforce opportunities Bidirectional, pull-only or push-only. With bidirectional on, Salesforce is the source of truth for deals that have already synced.
Activities Five separate settings Emails, tasks, notes, meeting summaries and phone calls, configured one at a time. This is the object where a duplicate-logging problem is prevented rather than fixed.
The source field Defaults to Apollo Set on new contacts synced from Apollo, and if the field you pick is a picklist you choose the value too. Worth setting deliberately, because it is the only attribution this integration writes.
Unverified emails Off unless you tick it Push unverified emails for contacts and leads governs the email address only, not whether the contact is pushed. A contact with an unverified email still arrives; the address does not.
Custom objects Read only, up to ten on Organization plans They come into Apollo and cannot trigger Apollo workflows, so they are context for a rep rather than something to automate on.

What the push settings actually govern

Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.

The actionHow it reads on the record
A net new contact saved in ApolloGoverned by the push setting and the stage filter
A contact imported from a CSVGoverned the same way
An update to a contact already in SalesforcePushed automatically, regardless of push settings
A record you push by handOverrides every sync setting, including stage restrictions
The account behind any pushed contactCreated or updated regardless, because Salesforce requires one
Anything, during the initial data pullManual push appears but does not work until the pull completes

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.

  • Filtering beyond stage. Apollo states that Salesforce push settings do not support filtering on anything else, so there is no way to push only contacts whose custom field has a particular value.
  • A lead-to-contact conversion. Changing the push type affects new records only, and converting existing leads is Salesforce's own lead conversion process rather than an Apollo setting.
  • The Owner field, in the usual case. Records created through the team sync connection normally carry the integration user, and Apollo's documented alternative is mapping its created_by field to Salesforce CreatedById instead.

Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the three 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.

Field map

Read the second table as the correction to the first. Three of its six rows describe something reaching Salesforce despite a setting that looks like it should stop it, and all three are documented rather than defects. A team that reads only the settings screen will configure this pair correctly and still be surprised by it in week two.

What the lead-or-contact switch actually changes

The plan requirements here are short: a paid Apollo plan, because the free one excludes CRM integrations, and a Salesforce edition with API access. The decision that costs real money is a switch rather than a tier, and this is what it does. Pick one on each side and the grid marks the answer.

Pick one on each side.

How the record was pushed beforeLeadsContacts
Already pushed as a lead updated as a lead updated as a lead
Already pushed as a contact updated as a contact updated as a contact
Never pushed updated as a lead updated as a contact
updated as a lead
Apollo keeps updating existing lead records as leads. It does not convert them and does not create a duplicate contact alongside them.
updated as a contact
Apollo keeps updating existing contact records as contacts, and will not turn one back into a lead. Salesforce does not support that direction either.

Counted off that grid, of six pairings: three give you updated as a lead, three give you updated as a contact. Two of the three rows read the same across both columns, and that is the finding: the switch governs records that have never been pushed and nothing else. Flipping it on a live integration leaves you running two record types at once, with lead conversion in Salesforce as the only way back and no way back from contacts at all.

How to connect Apollo to Salesforce

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 to install the managed package, and an Apollo user with permission to edit CRM integrations. The two are rarely the same person.
How long it takes
An hour of clicks, and the six hours after it are not optional free time.
Setup checklist 0 of 8 done

Your calendar

On a paid Apollo plan the clock starts at the connection: six hours to set the field mapping and the inbound and outbound settings, after which syncing enables itself. You cannot manually pull records during the window, so there is no way to use the time for anything but configuration.

Apollo: Settings, Integrations, Salesforce

Connect for production, or Connect to Sandbox, and never both at once. A team that rehearses in a sandbox has to disconnect it before going live, which means doing the configuration twice unless the rehearsal was the point.

Salesforce AppExchange, via Apollo

Click Install Managed Package in Apollo, which redirects you to the AppExchange. Apollo strongly recommends installing for all users, or for the specific profiles that contain your Apollo users. Installation takes a few minutes and needs Salesforce admin access.

Salesforce: App Launcher, Apollo Setup

Open the Apollo Setup app, click Get Started, and create a new integration user or select an existing one. Apollo strongly recommends keeping every default permission selected to prevent sync issues, and warns that mapping custom Salesforce fields later requires giving this user access to those fields now.

Apollo: Connect, Yes Continue

Whoever connects using the dedicated integration user becomes the team sync user, and that one connection does the account-wide syncing. Individual Apollo users do not need to connect their own Salesforce accounts for standard data sync.

Apollo: Salesforce, Contacts, Sync

Leads or contacts, and the choice only governs records that have never been pushed. Existing leads stay leads and keep being updated as leads; existing contacts stay contacts. Salesforce can convert a lead to a contact and cannot convert one back.

Apollo: Activities, Sync

Emails, tasks, notes, meeting summaries and phone calls are five settings rather than one switch. If something else in the org already logs emails or calls, this is where you keep Apollo out of that lane.

Apollo: people or company search

Apollo documents that a manual push overrides the sync settings entirely, ignoring stage restrictions and other limits, and that a Push all is how you apply a new field or stage mapping to records already in Salesforce. Manual push also does not work during the initial data pull.

The first two steps are scheduling decisions and they are the ones that go wrong, because the clock and the single-org rule both punish a team that connects to have a look. Everything after that is reversible except the lead-or-contact choice, which the grid below is about, and which the CRM layer answers differently in every org.

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

curl -o .claude/skills/apollo-salesforce/SKILL.md https://www.reversecontact.com/integrations-hub/skills/apollo-salesforce.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 configuration window closes by itself
Six hours after you first connect on a paid plan, syncing enables automatically whether or not the field mapping is finished, and you cannot manually pull records until it does. Book the configuration session for immediately after the connection rather than for the following morning, because the integration does not wait and the first sync is the one that writes to every matched record.
Push settings do not govern updates
They apply to net new contacts saved in Apollo or imported by CSV. Every update to a contact that already exists pushes automatically regardless. Teams who switch push off expecting Apollo to go quiet find it still writing, and the only real control over a given field is the mapping.
Accounts are created whether you asked or not
Pushing a net new contact creates or updates its linked account even with Push accounts off, because Salesforce will not accept a contact without one. In an org where account creation is governed, that is a process conversation to have before go-live rather than a surprise for whoever owns data quality.
One org at a time, and not the free plan
You can connect a production org or a sandbox, never both, so rehearsing in a sandbox means disconnecting it before you go live. Apollo's free plan excludes CRM integrations entirely, which makes Basic the real floor for anything on this page.
Existing connections have a deadline
Apollo states that all existing Salesforce connections must upgrade to the managed package by 31 December 2026, and recommends doing it early. The upgrade keeps your field mappings and push and pull settings, and the migrate option is being rolled out gradually, so a team that cannot see it yet is waiting for an email from Apollo rather than looking in the wrong place.

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

01

Insufficient access on cross reference ID

WhyThe integration user cannot see a record that the one being written relates to through a lookup or master-detail field. It is a record sharing problem rather than an object or field permission.

Check the sharing model and the lookup fields for the integration user, not for yourself. Practitioners in r/salesforce point out that being an admin does not guarantee read and edit access to every field, which is why the error survives an admin credential.

02

Syncing started before the mapping was finished

WhyThe six hour configuration window expired. On a paid plan Apollo enables syncing automatically at that point, whether or not anybody was ready.

Fix the mapping and run a manual Push all, which Apollo documents as the way to apply a new field or stage mapping to records already in Salesforce. The first sync cannot be unwound.

03

Apollo is still writing after push was switched off

WhyPush settings govern net new contacts saved in Apollo and ones imported from a CSV. Updates to contacts that already exist push automatically regardless.

Control the field mapping rather than the push toggle. A field Apollo must never write is a field Apollo must not be mapped to.

04

A contact landed on the wrong account

WhyThe contact matched more than one existing Salesforce account, and Apollo documents assigning one at random in that case.

Use consistent account naming, or push only contacts whose accounts already exist. There is no tie-break setting to configure.

05

Accounts are appearing that nobody pushed

WhyPushing a net new contact creates or updates its linked account even with Push accounts off, because Salesforce requires every contact to have one.

Treat it as a governance conversation rather than a setting. In an org where account creation is controlled, have it before go-live rather than with whoever owns data quality afterwards.

06

Contacts with no stage are not reaching Salesforce

WhyPush based on certain stages excludes contacts with no stage unless No stage is explicitly selected in the list.

Add No stage to the selection, or push everything. Remember that stage is the only filter available: Apollo states push settings do not support filtering on custom field values.

07

A sync error survived upgrading the Salesforce edition

WhyAn edition with API access is necessary and not sufficient. The same error is produced by the connected user's permissions and by an Apollo field mapping, and one r/salesforce commenter reports legacy Group Edition blocking API integrations whatever you pay.

Confirm which of the three it is before buying the upgrade. Practitioners in that thread say exactly this, and a field mapping or a sharing rule will keep failing after the plan changes.

08

The migrate option for the managed package is not there

WhyApollo is rolling the upgrade path out over time. Existing connections have until 31 December 2026 and the option appears when Apollo says it is ready.

Wait for the email rather than reconnecting from scratch. The upgrade preserves existing field mappings and push and pull settings, and a fresh connection would restart the six hour window.

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

  • Reps prospect in Apollo and Salesforce has to stay the record
  • Sequence activity needs to appear against the opportunity
  • You want CRM data back in Apollo to target from

Do not bother when

  • You are on Apollo's free plan, which excludes CRM integrations
  • Nobody has decided which system owns which field
  • Your edition has no API access, which no setting fixes

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

The errors are Salesforce sharing problems, not integration problems

It's more than likely record sharing related, not just object and field level. Also, are you the user that the integration is using? If so, id challenge that immediately as you shouldn't ever give an integration full admin rights.

r/salesforce·January 2026·3 points

Answering an admin stuck on insufficient access on cross reference ID, and both halves are right. Another reply explains the error precisely: a record being created relates to another record the user cannot access. Apollo's own advice to keep every default permission on the integration user is the preventative version of the same point.

Being a Salesforce admin does not mean you can see every field

Just because you're an Admin doesn't automatically mean you have read/edit access for all fields. As mentioned by the above commenter, I would start by checking the permissions for all of the lookup or master-detail fields first.

r/salesforce·January 2026·1 points

The sentence that unsticks this error, and it contradicts what the original poster found by searching. It also explains why Apollo warns that mapping a custom Salesforce field later means granting the integration user access to it now.

Apollo itself says not to sync top-of-funnel data

Sync to CRM when the data has been qualified. [...] Don't sync top-of-funnel prospecting data. This is where the default advice falls apart. Most RevOps leaders we work with deliberately keep cold outbound and unqualified inbound out of the CRM.

r/UseApolloIo·December 2025·2 points

A vendor post in the vendor's own subreddit, which is why it is worth printing: the company that built the push settings is arguing for the narrow ones. The reason given is that a CRM where every sequenced contact becomes a record is a dumping ground inside a quarter, which is also the argument for the stage filter being the only filter Apollo offers.

Duplicates in the CRM are paid for twice

One thing I'd add: before teams even optimize Apollo-to-CRM sync, they should clean up duplicate companies and contacts inside the CRM. Otherwise you end up paying twice in Apollo credits for the same company/contact, and worse, the CRM context gets scattered across multiple duplicate records.

r/UseApolloIo·June 2026·1 points

The same point practitioners make about every enrichment pair in this directory, and it has a specific mechanism here: Apollo's contacts deletion sync and contacts merge sync mirror Salesforce deletions and merges, but only once the duplicates have been dealt with on the Salesforce side.

An edition upgrade is not a guaranteed fix for a sync error

Enterprise gives Apollo the Salesforce API access it needs, but it won't automatically clear every sync error. Before paying for the upgrade, confirm the error is actually edition/API related rather than the connected user's permissions or an Apollo field mapping, because either of those can keep failing after the plan change.

r/salesforce·July 2026·1 points

Answering somebody about to pay for an Enterprise upgrade on a Salesforce representative's advice. A second reply in the thread claims legacy Group Edition blocks API integrations regardless of plan, which is a thread claim rather than a documented one and worth checking with Salesforce before either decision.

What the threads add up to

Two useful things come out of these threads. The first is that the errors people report are Salesforce errors rather than Apollo ones: sharing rules, lookup access and edition limits, with admins surprised that holding the admin profile does not settle it. The second is more interesting, because it is Apollo arguing against its own widest setting: a post in Apollo's own subreddit says not to sync top-of-funnel prospecting data to the CRM at all, which is the opposite of what a connector this thorough implies you should do.

The first two quotes describe an error anybody can reproduce and the vendor post describes a policy, which is a different kind of evidence. The policy one is the one to argue about internally, because this integration will implement whichever answer you give it and the settings that enforce the narrow version are the ones covered above.

The longer answer

Every awkward story about this pair traces back to the same thing: Apollo defaults towards writing, and writing to a CRM is a governance decision rather than a feature. The six hour window, the push settings that do not cover updates and the accounts that appear by themselves are all the same design. None of them is hidden, all of them are documented, and all of them bite teams who connected first and planned afterwards. Connect when the person who will configure the mapping has an afternoon free.

The configuration that survives is the usual one: let Apollo write to properties it owns rather than to the fields reps maintain, decide per field which system wins before enabling anything bidirectional, and keep deals pull-only unless you have a specific reason not to. Apollo's own guidance says much the same, favouring selective bidirectional sync over blanket two-way, and it is right. A connector will faithfully implement whatever confusion you hand it.

Set against the HubSpot pairing, the feature sets are close and the work is not. Salesforce adds a managed package, an admin with Modify Metadata, a sandbox decision and an API allocation shared with every other integration in the org. That is the same tax every pair on the CRM layer pays here, and it is why this is an hours-to-days project on Salesforce and an afternoon on HubSpot.

Checked by

Reverse Contact

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 · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

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
3 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Apollo, Salesforce and everything else in this directory, and it returns null with a confidence score rather than a guess.

Free trial, no card required, and 500 credits to start.

Apollo and Salesforce, asked and answered

What do I need before connecting Apollo to Salesforce?

Salesforce admin access to install the Apollo managed package from the AppExchange, permission to edit CRM integrations on Apollo, and a dedicated integration user. You can connect a production org or a sandbox but not both at once, so a team that wants to rehearse in a sandbox first has to disconnect it before going live. Apollo's free plan does not include CRM integrations at all.

What is the six hour window?

On a paid Apollo plan, you get six hours after first connecting Salesforce to configure field mapping and your inbound and outbound sync settings. During that window you cannot manually pull Salesforce records. When it expires, syncing enables itself automatically whether or not anybody finished configuring. You can still change the settings afterwards, but the first sync will have run against whatever you had at the six hour mark.

Will turning off push stop Apollo writing to Salesforce?

No, and this is the most misread setting on the pair. Apollo documents that push settings only affect net new contacts saved in Apollo or imported from a CSV. Updates to contacts that already exist are pushed automatically regardless of push settings. If you need a field never to be written from Apollo, the control is the field mapping rather than the push toggle.

Why did an account appear that I did not push?

Because Salesforce requires every contact to be linked to an account. When you request a net new contact in Apollo and push it, Apollo creates or updates the linked account even if Push accounts is switched off. If your org uses leads instead, contacts associate with leads rather than accounts, and Apollo can infer accounts for you in the pull settings.

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