Skip to content

Migration guide · Salesforce Modernization

Exchange EWS to Microsoft Graph for Salesforce email migration

Exchange Web Services (EWS) connectionsMicrosoft Graph

Short answer

Microsoft is retiring Exchange Web Services in Exchange Online, so Salesforce email and calendar integrations that rely on EWS must move to Microsoft Graph-based options such as Einstein Activity Capture and the current Outlook integration.

Why firms make this move

Several older Salesforce email features and third-party sync tools connect to Exchange Online through EWS. Once Microsoft turns EWS off, those connections stop syncing email and calendar. Firms need to find what still uses EWS, move to supported Graph-based features, and confirm compliance archiving still captures what it should.

What moves

  • Email and calendar sync configuration
  • Outlook integration and add-in settings
  • Third-party sync tools that use EWS
  • Admin consent for Microsoft Graph

How the data maps

FromTo
EWS-based syncEinstein Activity Capture or Outlook integration on Microsoft Graph
Lightning SyncEinstein Activity Capture
Third-party EWS toolVendor's Graph-based version or replacement

See the field-by-field map ↓

What to watch out for

  • Tools nobody knew used EWS
  • Microsoft Entra admin consent
  • Reporting differences with Einstein Activity Capture
  • Archiving coverage

How Vantage Point runs the migration

  1. Inventory email and calendar integrations
  2. Grant Microsoft Graph consent
  3. Configure Einstein Activity Capture and the Outlook integration
  4. Pilot and verify reporting
  5. Retire EWS connections

Typical timeline

Typically 2 to 4 weeks.

Frequently asked questions

Does this affect HubSpot?

HubSpot's own Microsoft 365 connection is managed by HubSpot. This guide is about Salesforce email integrations and third-party tools.

When is EWS turned off?

Microsoft has announced the retirement for Exchange Online; check Microsoft's current timeline, as dates have shifted.

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

Field-level map

Exchange EWS to Microsoft Graph for Salesforce email: field by field

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

FromToHowNotes
EWS connectionService account + EWS endpoint Microsoft GraphEntra ID app registration req rebuild
EWS permissionsImpersonation Graph permissionsMail / Calendar scopes, admin consent req rebuild Scope access to the right mailboxes.
EWS callsFindItem / GetItem Graph/messages and /events endpoints derive
EWS notificationsPush / pull subscriptions GraphChange notifications (webhooks) 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.