--- schema_version: "1" id: bdcf3b08db8c10218049ac3c77ddb2a5355f6d2a0176edc98e1b00a7ff7a98bd title: Considerations for Syncing Events collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/exchange_sync_admin_considerations_events_general.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.exchange_sync_admin_considerations_events_general.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 2bcbc7a7aa45f180b8d00489885ee68558ea3f95c04c4bb1c5945c399d8cd2d2 description: Familiarize yourself with these considerations for syncing events with Lightning Sync. products: - Sales Cloud - Cross Cloud - Service Cloud Voice release: "264" --- # Considerations for Syncing Events Familiarize yourself with these considerations for syncing events with Lightning Sync. ### 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
## General Considerations Attachments Event attachments don’t sync between Microsoft® Exchange or Google and Salesforce. Attendees - Up to 50 event attendees sync between Salesforce and Microsoft Exchange or Google. - Syncing attendees experience unexpected sync behavior with events created by nonsyncing organizers. - If the event is created in Salesforce, each attendee sees their own version of the event on their Salesforce calendar. The syncing attendees’ version of the event doesn’t sync. - If created in an external calendar, the attendee’s event syncs to Salesforce, assuming the attendee is set to sync Exchange to Salesforce, Google to Salesforce, or both ways. On the version of the event synced to Salesforce, the attendee is the organizer and only participant. Other attendees aren’t visible. The attendee can edit any field, but those edits don’t sync from Salesforce to Exchange. If the nonsyncing organizer updates the event from your calendar application, the organizer’s edits override the attendee’s and sync to Salesforce. Letting the organizer’s edits override the attendee’s ensures that the attendee sees the latest meeting details. In these scenarios, the nonsyncing organizer can be a nonsyncing Salesforce user or an outsider to the syncing attendee’s Salesforce org, email domain, or company. - Event invitations and cancellations for syncing events are emailed to attendees from Exchange or Google, not from Salesforce. - Attendee responses to event invitations never sync from Salesforce to Exchange or Google. In Lightning Experience and the Salesforce mobile app, it isn’t possible for attendees to respond to event invitations. To avoid overwriting attendance statuses in Salesforce Classic, [users can learn where to respond to event invitations based on their set sync directions](https://help.salesforce.com/s/articleView?id=sales.lightning_sync_user_exchange_respond_events.htm&type=5&language=en_US). - Attendees can be unintentionally removed from syncing events when both of these conditions are met. - When the organizer is set up for one of these sync directions: Both Ways, Exchange to Salesforce, or Google to Salesforce. - When a user changes or removes the matching email address from the Salesforce user account, contact, or lead. Exception: Under these conditions, original attendee records can remain invited to syncing events despite having been intentionally removed. - When the organizer replaces the email address on the Microsoft or Google event with an address that doesn’t match the original Salesforce user, contact, or lead. - When a user adds an email address on the Microsoft or Google event, and the email address matches a record that has an original attendee's email address in a custom email field. - If an event organizer is set up to sync after attendees have been syncing, participants can experience some unexpected behavior for scheduled events. - Attendees can see and change a standalone event on their Salesforce calendars. When an event organizer is set up to sync after attendees have been syncing, a new syncing event is created. The event organizer sees the new syncing event, but to prevent duplicates, attendees with a standalone event don't see the syncing event. If an organizer adds new attendees to the new syncing event, attendees with a standalone event see a duplicate event. All meeting participants are visible on the Microsoft or Google event. - Attendees sometimes see duplicates in Salesforce after admins reset sync for event organizers and attendees. Changing Event Owner If an event owner is changed, the event is removed from the previous owner’s Salesforce calendar, but not from the previous owner’s Google or Microsoft calendar. Cloning The clone action is hidden in Salesforce Classic when Lightning Sync is enabled. Custom Fields If you added custom fields to your Salesforce events, Lightning Sync doesn’t sync those fields between Salesforce and your calendar application. But when matching records between Salesforce and your calendar application, Lightning Sync considers custom email fields on Salesforce records when Shield Platform Encryption is applied to some standard fields. See the Shield Platform Encryption section. Email Address Aliases Lightning Sync doesn’t support contact or event matching with alias email addresses. To make sure that contacts and events sync between applications, opt to add primary email addresses to contacts or events when possible. To make sure that Salesforce users sync as event attendees on events, assign only primary Microsoft or Google email addresses when you create Salesforce user profiles. Salesforce Scheduler Lightning Sync supports using the Salesforce Scheduler feature with these sync directions only: - Salesforce to Exchange - Salesforce to Google Using Salesforce Scheduler with other sync directions can result in sync failure or overwritten data, including canceled events. Mobile Event sync is supported on all versions of the Salesforce mobile app. Some sync features can be limited on Microsoft or Google mobile apps. For more details, check the product documentation for those apps. Shield Platform Encryption Lightning Sync is supported when Shield Platform Encryption is enabled on any Salesforce object or field. But if you encrypt the Email field on the User object, the User Email field is duplicated in the Salesforce database when users are added to sync configurations that sync contacts or events. Even when the User Email field is encrypted using Shield Platform Encryption, this duplicate field stores user emails in the Salesforce database in an unencrypted state. When Shield Platform Encryption is turned on, Lightning Sync matching behavior is modified. Normally, Lightning Sync matches records using the same standard Salesforce fields. But when you encrypt the Email field on Salesforce users, contacts, or leads, Lightning Sync expands its search to any custom email field you added to the record in these cases: - When matching event attendees between Microsoft or Google and Salesforce - When automatically relating matching Salesforce contacts or leads to your events Because Lightning Sync relates the first matching email address it identifies, users, contacts, and leads can be matched based on the standard Email field or a custom email field. Sync Conflicts - If a change you made in Salesforce didn’t sync to your calendar, you could have experienced a sync conflict. Sync conflicts occur when at least one of these conditions is true. - You’re set up to sync events both ways. - You, another user with access, or an automated action updates the event in your calendar application and Salesforce before Lightning Sync syncs the changeIf a sync conflict occurs, Lightning Sync gives preference to the change made in your external calendar. If automatic, mass event updates are made from your calendar application or Salesforce, you’re likely to experience sync conflicts more often. Companies usually make mass event updates when admins or developers set up automation or create custom API calls to create or update Salesforce, Microsoft, or Google events. - Updates that are made in Microsoft or Google to the date or time of an existing Salesforce Scheduler service appointment don’t automatically sync to Salesforce. To keep service appointments in sync: - Make changes to or update service appointments in Salesforce. - After changing the date or time of a service appointment from Microsoft or Google, manually make the same change in Salesforce. Sync Totals Lightning Sync can sync up to 50,000 events per user. If you have more than 50,000 events that meet the event sync filters set by your admin, an additional nonsyncing event is picked up for sync only when one of the 50,000 stops syncing. An event stops syncing when any one or more of these conditions are true. - If someone deletes the event in Salesforce or in the Microsoft or Google calendar application - If the event occurred and no longer meets past event sync filters - If an event sync issue occurs ## Considerations for Syncing Events with Google Calendar™ Event Series and Recurring Events Sync for recurring events (Salesforce Classic) and event series (Lightning Experience, the Salesforce app) isn’t supported for Lightning Sync for Google. Event Descriptions Salesforce event descriptions are truncated to 8,192 characters after syncing with Google Calendar. This limit affects Lightning Sync for Google users who are set up to sync events either both ways or from Salesforce to Google only. ## Considerations for Syncing Events with Microsoft® Calendar Syncing Events Events created using Bookings with Me in Outlook don’t sync between Microsoft and Salesforce. Sync for event series (repeating events created in Lightning Experience, the Salesforce app) is supported only for Microsoft Exchange. - Sync for recurring events (repeating events created in Salesforce Classic) isn’t supported. - If you’re set up to specify which Microsoft events sync to Salesforce using the Outlook integration, that feature isn’t supported for event series. If you select an event series in Outlook, the option to log that event isn’t available. - When you edit a series from Microsoft calendar, only updates to future events sync to Salesforce. When you delete a series from Microsoft calendar, only future events are removed from Salesforce. - When you delete individual events from an event series, the delete syncs between Salesforce and Microsoft calendars based on your sync direction. The individual events are removed from the Microsoft series regardless of whether your Salesforce admin has selected the Delete synced events option in your sync configuration. - When you convert a series to a standalone event from Microsoft calendar, Lightning sync doesn’t remove the series from Salesforce calendar. Instead, we recommend that you delete the series from Microsoft calendar and create a standalone event. - When you convert a standalone event to a series from Microsoft calendar, Lightning Sync deletes the matching standalone event in Salesforce and creates a series. The new series doesn’t retain relationships from the original event to other Salesforce records that you added manually. If you’re set up to automatically relate contacts or leads to events, Lightning Sync attempts to relate records based on the data you saved in the new series. - When you make critical changes to your series from either your Microsoft calendar or Salesforce, Salesforce event descriptions and relationships to other records aren’t retained. Events that you edited to fall outside of the series are also updated and begin syncing again. Deleted events are recreated to include the critical changes and also begin syncing again. Critical changes include modifications to: - All-day event checkbox - Appointment times (StartDateTime, Duration) - Recurrence patterns (RecurrenceType, Instance, Interval, DayOfMonth, DayOfWeekMask, MonthOfYear, DayOfWeekIndex) - Ranges of occurrences (Occurrences, EndDateOnly, EndKind) - Editing the Assigned To field for an event series is possible, but it causes issues when syncing with Microsoft calendars. To reassign an event series, delete the series, and recreate it with the desired owner. - Changing the private flag on an individual event from a series is possible, but it causes issues when syncing with Microsoft calendars. To set a different private flag for an individual event, create a standalone event with the private flag set as desired. - When an event series includes recurrence patterns supported in Microsoft but not in Salesforce, you can’t see or edit the pattern in Salesforce. Instead, edit these events from your Microsoft calendar. - When a non-organizer logs an event using the Outlook integration, all attendees initially appear on the record. To prevent duplicate entries and sync conflicts across users, background sync (Lightning Sync or Einstein Activity Capture) updates the record to remove the other attendees, leaving only the user who logged the event. #### See Also - [Respond to Event Invitations from Your Microsoft or Google Calendar](https://help.salesforce.com/s/articleView?id=sales.lightning_sync_user_exchange_respond_events.htm&release=264.0.0&type=5 "To avoid overwriting your attendance status when syncing with Einstein Activity Capture or Lightning Sync, consider your sync direction before you accept and decline event invitations.")