Salesforce CRM sync
The 'Marketo–Salesforce sync' is the platform's flagship integration and the single largest source of support tickets — schema drift, picklist mismatches, lock-row contention.
What people actually say
✕Field Integrity Exceptions are among Marketo's most frequent sync errors, triggered whenever Marketo sends a value that violates a Salesforce picklist, required field or validation rule — and any Salesforce schema change forces an immediate Marketo remap.
Source: DGT27, Marketo Salesforce sync errors ↗✕Running many Smart Campaigns concurrently slows the sync, and large data loads regularly take hours or longer to process when Salesforce API limits are hit or queue locking kicks in.
Source: Marmato Digital, Salesforce sync errors in Marketo ↗✕Reviewers explicitly flag CRM sync errors as an ongoing data-health issue and note the MS Dynamics integration is noticeably weaker than the Salesforce one — neither is friction-free.
Source: Capterra, Marketo reviews ↗
Sync runs as an Inngest job that owns idempotency, retries and rate-limit budgeting end to end. Field mappings live in typed TypeScript, so renaming a Salesforce field is a PR with a compile error — not a 4am alert. We write through the Salesforce Bulk API in batches sized to the org's limits, log every conflict to an inspectable queue, and never silently lose a lead because a picklist drifted.