What's the integration architecture nightmare between Salesforce, Gong, Outreach, and a marketing automation platform — which sync directions break first, and how do you fix them?

The Salesforce + Gong + Outreach + MAP Integration Nightmare — Which Syncs Break First and How to Fix Them

The four-tool stack (Salesforce, Gong, Outreach, Marketo/HubSpot) has one rule: Salesforce is the system of record, everything else is a system of action. The moment you treat any satellite tool as authoritative on shared fields, you get write conflicts, duplicate records, ghost accounts, and attribution collapse. The breaks are predictable — and fixable.

---

THE DETAIL

Where the stack breaks, in order of frequency:

1. Outreach ↔ Salesforce Opportunity Write Conflict Outreach treats Salesforce opportunities as read-only — opportunity edits in Outreach don't push back to Salesforce. Tasks created in Salesforce also don't sync down into Outreach. Reps stage-advancing in Outreach while an admin edits in SFDC creates phantom pipeline. Fix: if Salesforce is your source of truth, deselect "Create" on the Salesforce side and keep "Update" — this prevents Outreach from spawning duplicate records that haunt you for months.

2. API Limit Exhaustion Killing the Whole Stack Relationships multiply API calls fast. Import 100 contacts whose accounts aren't already in Outreach and you burn 101 API calls — one for the contact batch, plus 100 for each new account. At scale, a bulk import that looks small can eat your daily API budget before lunch. When thresholds are hit, Outreach pauses all push/pull operations until the next rolling 24-hour block — you'll see "LIMIT_EXCEEDED" in plugin logs and wonder why nothing's syncing. Fix: set your Global API Call Usage threshold to 70–80% and your Outreach-specific threshold to 20–30%, leaving headroom for other integrations.

3. Gong → Salesforce: Activity Logged as Notes, Not Field Updates Gong's CRM integration strategy centers on a logging-only approach, where conversation data is pushed to CRM systems as activity notes rather than structured field updates. MEDDPICC fields stay blank. Forecast calls are based on conversation sentiment, not structured data. Fix: use Gong's custom field export to map call outcomes directly to SFDC fields — or use Zapier/Workato to convert Gong activity webhooks into field writes.

4. Gong Can Only Connect to One CRM Gong only supports integration with one CRM at a time — it's not currently possible to connect two CRMs simultaneously in Gong. If you run Salesforce as CRM and HubSpot as MAP, Gong call data never touches HubSpot directly. Fix: pipe Gong → SFDC → HubSpot through the SFDC-HubSpot native sync, or use a middleware layer (Workato, Census) to bridge the gap.

5. Marketo/HubSpot ↔ Salesforce Lead Status Collision If the sync user lacks the ability to edit opportunities or campaigns, Marketo cannot update Salesforce, leading to data gaps that frustrate both sales and marketing teams. Opportunities typically flow one way — from Salesforce to Marketo — not bidirectionally. The moment a rep manually changes lead status in SFDC while a Marketo nurture flow overwrites it, you've lost the record. Fix: hard-code field-level ownership — MAP owns Lead Score and Last Campaign, SFDC owns Lead Status and Owner.

6. Inbound Sync Latency Compounding Across the Stack Inbound polling — Salesforce changes syncing into Outreach — runs every 10 minutes by default. For near-real-time inbound sync, consider middleware like Workato to trigger on Salesforce record changes. With Outreach on a 10-min poll, Gong on a 6-hour export cycle, and Marketo on its own polling schedule, a rep can be calling into a contact that marketing already unsubscribed — 4 hours ago.

---

Sync Direction Ownership Table

---

Architecture Fix: Single Source of Truth Model