Skip to content

Migration guide · Salesforce Modernization

Lightning Sync to Einstein Activity Capture migration

Lightning Sync (Exchange Web Services)Einstein Activity Capture (Microsoft Graph)

Short answer

Moving from Lightning Sync to Einstein Activity Capture (EAC) replaces Salesforce's retiring Outlook and Exchange sync with EAC, which captures email and calendar activity through Microsoft Graph as Microsoft retires Exchange Web Services. The move needs planning because EAC stores and reports activity differently.

Why firms make this move

Lightning Sync relied on Exchange Web Services, which Microsoft is retiring. Einstein Activity Capture is Salesforce's replacement. Firms need to configure EAC, decide what is captured and logged to records, check visibility settings, and confirm that compliance archiving still captures what it should.

What moves

  • Email and calendar sync configuration
  • Sharing and visibility settings
  • Logging rules so key activity appears in reports
  • User permission sets and connections

How the data maps

FromTo
Lightning Sync configurationEAC configuration
Synced eventsEAC captured events
Logged emailsLogged-to-record emails

See the field-by-field map ↓

What to watch out for

  • Captured emails missing from standard reports
  • Users missing permission sets
  • Archiving and supervision coverage
  • Shared mailboxes and delegates

How Vantage Point runs the migration

  1. Review current sync and reporting needs
  2. Configure EAC and Microsoft Graph connection
  3. Pilot with a small group
  4. Roll out and decommission Lightning Sync

Typical timeline

Typically 2 to 4 weeks.

Frequently asked questions

Why don't EAC emails show in reports?

EAC stores captured emails outside standard objects unless you enable logging to records.

Is Lightning Sync really going away?

Yes. Salesforce is retiring Lightning Sync and Microsoft is retiring the Exchange Web Services it depends on.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Lightning Sync to Einstein Activity Capture: field by field

5 mappings we start from on this migration, 3 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Lightning Sync configSync settings Einstein Activity Capture configConfiguration req rebuild
Lightning SyncContact sync EACContact sync direct
Lightning SyncEvent sync EACEvent sync direct
Synced emailsEmails logged as Tasks EAC activities— req manual review EAC activity data is stored differently and reporting is limited. Decide if emails must also be logged as records.
Sync filtersInclusion / exclusion EAC configurationExclusions rebuild

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.