What you’re working toward.
A controlled prospect handoff that protects CRM ownership and campaign exclusions.
- Bring these people
- Outbound operations, sales leadership, and the HubSpot administrator
Have these inputs ready
- A deduplicated pilot population and agreed qualification criteria.
- A field map covering identifiers, owners, source, stages, and protected values.
- An explicit suppression policy with a named owner.
Define the direction
Decide which system owns prospect discovery, which owns customer status, and when a researched contact should become a CRM record. Verify the current connector’s supported objects and sync options in the vendor documentation.
- Decide when a discovered person should become a CRM record: research approval, outreach approval, or a qualified response. Keep record creation separate from enrollment into a campaign.
- Document push and pull settings independently. Include an already-linked record in the pilot because limiting new-record creation does not necessarily stop updates to existing records.
A sync policy naming the eligible population and the trigger for each movement.
Map and protect fields
Write a field-level map for email, account domain, owner, source, qualification, and enrichment values. Protect trusted CRM fields from low-confidence overwrites. Use stable identifiers and explicit duplicate handling.
- Map picklist values and owners before enabling broad movement. Decide how blanks and enrichment updates interact with trusted rep-entered fields.
- Review companies with the same domain or duplicate account records. Resolve ambiguity before pushing contacts that need a company association.
A field map with source ownership, overwrite policy, and duplicate-resolution rules.
Respect exclusions
Keep customers, open opportunities, opted-out contacts, and internal domains out of inappropriate campaigns. Agree how suppression decisions propagate and how stale records are handled.
- Create test records representing a customer, an active opportunity, a previously opted-out contact, and an internal domain. Verify each is excluded from the intended outreach process.
- Trace suppression through every campaign entry point. Do not assume a sync filter is also an outreach suppression rule.
A suppression test covering both record movement and campaign enrollment.
Test the whole handoff
Test new and existing contacts, a changed email, missing company, owner changes, and a suppressed record. Confirm that replies and qualified opportunities reach the right person. Monitor errors before expanding the sync population.
- Test a new contact, an existing linked contact, a changed owner, an invalid dropdown value, and a contact whose company already exists twice.
- Record the source ID, CRM ID, expected company, owner, and activity outcome. Expand only after the pilot’s errors have assigned resolutions and the sales owner accepts the handoff.
A pilot acceptance log and a named sync-error owner.
Separate sync eligibility from outreach eligibility
Illustrative rules for an outbound pilot; the same record can belong in the CRM and be excluded from outreach.
Know when the work is ready.
Use these checks in the handover. Keep evidence of the result and assign an owner to anything that still fails.
- Existing linked records respect the approved field ownership.
- A contact lands on the intended company when duplicates exist.
- Suppressed records cannot enter the acquisition campaign.
- An invalid field value produces a visible, owned exception.
Catch the problems early.
Treating push filters as a complete stop switch
Apollo documents different behavior for new records and updates to existing contacts. Test both populations when changing the integration.
Letting enrichment overwrite sales context
A newer value is not automatically a better value. Protect reviewed ownership and qualification fields through explicit mapping decisions.
Product references
Apollo distinguishes new-contact push conditions from automatic updates to existing contacts. It also documents company creation and association behavior during contact pushes.
Use the vendor’s mapping controls to implement the field contract, then verify the result on representative records.