Apollo → HubSpot for SDRs: company matching, duplicates, field mapping and CRM hygiene

Developer Support APIs & Integrations
, , ,
1

  1. How reliable is Apollo at detecting that a company or contact already exists in HubSpot, and which properties does it actually use for matching?

  2. Have you experienced duplicate companies or contacts being created by Apollo — especially with similar company names, root domains vs subdomains, or missing/inconsistent domains?

  3. Do you let Apollo create and associate companies automatically, or do you keep company creation/association logic inside HubSpot? Why?

  4. How flexible and reliable is Apollo → HubSpot property mapping in practice? Have you run into issues with custom properties, dropdowns or multi-select fields?

  5. Do you allow Apollo to overwrite existing HubSpot values, or do you generally use “fill empty fields only”? Which fields would you avoid letting Apollo overwrite?

  6. For SDRs using the LinkedIn → Apollo extension → Push to HubSpot workflow, how reliable is the contact being added to the correct existing company with the right data? What are the main friction points in day-to-day use?

  7. How do you protect records that should not be modified by SDRs — for example existing customers, active opportunities, partners or contacts in protected lifecycle stages?

  8. What are the worst edge cases you have seen with the integration — for example partial syncs, wrong company associations after a job change, failed properties, sync delays or retries — and which of these were easy to solve with configuration vs requiring HubSpot workflows or manual cleanup?

    And 9: How do you handle Apollo Industry mapping in HubSpot if you already use your own normalized Industry / Industry Group taxonomy? Do you map Apollo Industry into a separate raw property first, or have you found a safe way to map it directly without creating conflicts or invalid dropdown values?

3

Hey @Stan,

Great questions! This covers a lot of ground on a setup that plenty of SDR teams are navigating. This may be best answered by folks from the community who have used the integration, but here are a few resources that might help frame some of these while others weighs in:

  1. Data enrichment challenges from Apollo.io
  2. Managing associated companies after job change enrichment
  3. Tracking Apollo lists in HubSpot after push
  4. Apollo Integration Still Assigning Contacts to Old Owner

Hey @elizheleva, @EugeneAtKiwi, @lnorden, @HubDoPete – any chance you have experience with the Apollo integration and have insight on any of @Stan’s questions?

Thank in advance!

Sam, Community Manager

4

Hi @Stan Thanks for the tag, @Stassey!

I haven’t managed an Apollo integration myself, so I’ll leave the Apollo-specific recommendations to those with firsthand experience, but a couple of these questions definitely stood out to me from a HubSpot data governance perspective.

Duplicate prevention & matching would be one of my biggest concerns. In my experience with enrichment tools, (We’ve tried 6sense, ZoomInfo, RevDojo) exact-match logic often doesn’t function well against real-world CRM data. Contacts have multiple email addresses, companies may have multiple domains/subdomains, naming conventions vary or are misspelled, etc. Unless the integration has strong fuzzy-matching capabilities, (which most do not, ZoomInfo is the only enrichment tool I found that truly does a fuzzy match) I’d be very cautious about allowing it to automatically create records whenever a direct match isn’t found.

I’d also test activity associations before enabling activity sync. We’ve found that activities created by integrations don’t respect the association limits we have in place for activities created directly within HubSpot. Activities from Integrations still follow HubSpot’s default logic of attaching to the “Top 5” open Deals and Tickets, related or not, resulting in a pretty significant downstream impact on reporting and metrics. (This really messes up our ‘Deal Response Time’ and ‘Average Contact Attempt’ Metrics)

For field mapping, I always take a conversative approach. I populate empty values only and I map outside Data into a “raw” field in HubSpot (as opposed to overwriting the existing field) then standardize it within HubSpot via workflow or field settings.

I can’t speak to which Apollo settings best accomplish those things, but those would definitely be areas I’d test thoroughly in a sandbox before rolling it out to SDRs.

I hope that helps!

Lindsey Norden

HubSpot Community Champion