Sync
In Salesforce, Sync is the process of keeping records consistent between Salesforce and external systems - email, calendars, ERPs, marketing platforms - so a change in one place is reflected in the other.
Definition
In Salesforce, Sync is the process of keeping records consistent between Salesforce and external systems - email, calendars, ERPs, marketing platforms - so a change in one place is reflected in the other. Modern Salesforce syncs run on Einstein Activity Capture (for email and calendar, replacing the retired Lightning Sync), Data Cloud Activations (for unified-profile data), Marketing Cloud Connect (for campaign sync), and custom integrations via the Platform Event, Change Data Capture, and REST/Bulk APIs.
In plain English
“Sync in Salesforce means keeping the same record in two places up to date. The most common ones are Einstein Activity Capture (Outlook/Gmail email and calendar, replacing the retired Lightning Sync), Data Cloud Activations (unified profiles to downstream tools), and custom API-based syncs to ERPs or data warehouses.”
Worked example
A CRM manager at Summit Group sets up three syncs in the same org: Einstein Activity Capture for every sales rep (Outlook emails and meetings auto-flow into the Activity Timeline), a Data Cloud Activation that pushes a "Lapsed VIP" segment nightly to Marketing Cloud, and a Platform-Event-based integration to their ERP that pushes closed-won Opportunities and pulls invoice status. Each sync handles a different system pair and cadence, but together they keep the CRM, the calendar, the marketing tool, and the ERP in agreement.
Why Sync matters
Sync is the umbrella term for any process that keeps records consistent across Salesforce and external systems. The common patterns are: Einstein Activity Capture for email and calendar (the modern replacement for the retired Lightning Sync), Data Cloud Activations for sending unified profiles and segments to downstream channels, Marketing Cloud Connect for Sales/Service ↔ Marketing Cloud campaign data, Salesforce Connect and external objects for read-mostly cross-system queries, and custom integrations built on REST/Bulk APIs, Change Data Capture, or Platform Events.
Mature sync implementations address three hard problems: conflict resolution (what happens when both sides change the same record), error handling (retry vs. dead-letter for failed syncs), and monitoring (dashboards that surface sync lag and failure rates before users complain). Choice of sync technology depends on direction (one-way vs. bidirectional), latency tolerance (real-time vs. nightly), and payload size (individual records vs. bulk datasets). Starting with Salesforce-native options (EAC, Data Cloud Activations, Salesforce Connect) is almost always cheaper than building a custom integration; drop to custom only when the native pattern does not fit.
How organizations use Sync
Uses Einstein Activity Capture for bidirectional email and calendar sync across the whole sales org; retired Lightning Sync as part of that rollout.
Built a custom Platform-Event-based sync between Salesforce and their ERP with explicit conflict resolution - ERP wins on invoice fields, Salesforce wins on Account data.
Runs nightly Data Cloud Activations to push unified segments into Marketing Cloud and ad audiences, monitoring the Activation run history for silent partial failures.
Test your knowledge
Q1. What is Sync in Salesforce?
Q2. What tools support sync?
Q3. What's a key concern for bidirectional sync?
Discussion
Loading discussion…