Considerations for Syncing Events from Your Calendar Application to
Salesforce Only
Before Salesforce admins set up Lightning Sync, they can
familiarize themselves with these considerations for syncing events from Google or Microsoft®
to Salesforce only. That way, their rollout generates no surprises.
Required Editions
Available to sync records from: Salesforce Classic, Lightning Experience, and the
Salesforce mobile app
Available to set up from: Salesforce Classic and Lightning Experience
Available in: Professional, Enterprise, Performance,
Unlimited, and Developer Editions with Sales Cloud, Service Cloud, and
Lightning Platform
Admins decide whether Lightning Sync users sync events,
and in which direction, by defining sync settings from Lightning Sync configurations in
Setup.
When syncing from Microsoft or Google calendars to Salesforce only, there’s potential for Lightning Sync to overwrite event
data. To prevent such an occurrence, admins can be considerate about how they roll out Lightning Sync.
Admins can consider whether reps meet one or more of these scenarios.
Reps are migrating reps from Salesforce for Outlook
Reps routinely edit their events records in Salesforce
Reps already have access to the Outlook integration or the Gmail integration
For example, say that a rep maintains meeting notes in
Salesforce event records. But the matching event in that rep’s calendar doesn’t include
those notes. If reps are set up to sync from Microsoft or Google to Salesforce, Lightning Sync overwrites the
event in Salesforce with the one from the calendar.
Admins can prevent reps’ events from being overwritten by following our guidelines for
syncing events from Microsoft or Google to Salesforce only.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.