Salesforce Outlook and Gmail Integration: Setup Guide for 2026

The short answer: which Salesforce email tool does what

Salesforce has renamed and retired its email tools several times, which is why search results are confusing. As of late 2026, this is the line-up, based on Salesforce’s documentation and release notes:

Email-to-Case is a different thing. It turns messages sent to a shared support address into cases. It does not touch reps’ personal inboxes, so it does not replace anything in this table. Service teams often run both.

Outlook vs Gmail: what differs

Both clients get the same side panel and the same Einstein Activity Capture. The differences are in how you install, what the user needs and where things break.

Log by hand or capture automatically?

This is the real decision. The side panel puts the rep in control: they choose which emails and meetings go into Salesforce and which record they belong to. Einstein Activity Capture takes the rep out of the loop and captures everything that matches a Salesforce contact or lead.

In practice, most teams turn on both. Capture runs in the background for coverage, and reps use the panel to attach important threads to the right opportunity or case.

How email and calendar data flows into Salesforce

Admin setup, step by step

This is the common path for a Sales Cloud org on Microsoft 365 or Google Workspace. Do it in a full or partial sandbox first if you can, with a few test mailboxes. Setup page names below are from Salesforce’s documentation; exact labels can shift between releases.

1. Check licenses and editionsConfirm users have standard Sales Cloud, Service Cloud or Lightning Platform licenses and use Lightning Experience. Count how many need automatic capture: Einstein Activity Capture Standard comes with Sales Cloud, but Salesforce has changed its seat allowance over time, so check how many Standard seats your org shows. Performance and Unlimited Editions, or add-ons such as Sales Cloud Einstein and Inbox, give the fuller version.
2. Turn on Enhanced EmailIn Setup, search for Enhanced Email and make sure it is on. Logged emails then become EmailMessage records that can relate to several contacts and a deal at once.
3. Enable the integrationOpen the Outlook Integration and Sync page or the Gmail Integration and Sync page in Setup and turn the integration on. Turn on the option that logs emails as Enhanced Email records.
4. Shape the side panelCreate an email application pane in the Lightning App Builder: which record details, related lists and actions reps see. Assign it by profile, so sales and service get different panes.
5. Deploy to usersFor Outlook, ask your Microsoft 365 admin to deploy the Salesforce add-in centrally to the right groups. For Gmail, ask your Google Workspace admin to force-install the Chrome extension, or send users a short install note.
6. Set up Einstein Activity CaptureIn the Einstein Activity Capture settings, create a configuration per group of users: what to sync (emails, events, contacts), in which direction, and the connection type for Microsoft or Google. Assign the Einstein Activity Capture permission set and add users to the configuration.
7. Store captured email as recordsTurn on Sync Email as Salesforce Activity. Decide whether to keep full emails or only headers (sender, recipients and time), and check how much data storage this will use.
8. Set exclusions and sharingExclude internal domains, personal addresses and sensitive senders such as HR, legal and payroll. Review who can see captured emails: once they are records, your activity sharing rules apply.
9. Test, then roll out by teamSend and receive test emails, book a test meeting and check that each lands on the right contact, account and opportunity. Start with one team for two weeks, then widen.

What each user does

• Outlook: open an email, click the Salesforce add-in icon (pin it to the ribbon or the message bar), and log in with Salesforce credentials once.
• Gmail: install or accept the Chrome extension, open Gmail, click the Salesforce icon and log in.
• Capture: when prompted in Salesforce, connect the Microsoft or Google account, then review personal exclusions in the activity settings.
• Daily use: on an important thread, use the panel to link the email to the right opportunity, even if capture already logged it.

What maps to what

Agree on these rules before go-live. They decide what your reports will show.

Which records an email links to is decided by a matching flow. Since Summer ’25, admins can customize this flow, for example to link emails to a custom project object. Test any change with real examples before you switch it on for everyone.

Calendar sync, Google Calendar and OneNote

Calendar sync comes from Einstein Activity Capture, for both Outlook and Google Calendar. You choose per configuration whether events flow from the calendar to Salesforce, from Salesforce to the calendar, or both. Events then appear on the timeline of the people and deals involved.

Two retirements matter here. Salesforce is retiring the view-only synced calendar overlay in EAC, and it has scheduled Activity 360 Reports, Activity Metrics, the Activities dashboard and Recommended Connections to retire in Spring ’27 (February 2027). Salesforce points customers to standard activity reports on Event, Task and EmailMessage records instead, which is one more reason to sync email as records.

OneNote has no native Salesforce connector. Keep meeting notes in Salesforce Notes on the record, or connect OneNote with Microsoft Power Automate, which has connectors for both. Slack and Teams are a separate topic: see the sibling guide on Salesforce Slack and Teams integration.

Privacy: what gets captured and who sees it

Automatic capture is powerful and easy to over-share. Settle these points with legal and the sales team before you switch it on:

• Scope. EAC adds emails to Salesforce when the people on them match records such as contacts and leads. You can exclude domains and addresses on top of that.
• Sensitive content. Salesforce has offered settings that keep emails with sensitive information out of capture, but they have changed between releases. Treat any such filter as a safety net, not a policy.
• Visibility. Captured emails follow activity sharing once they are records. A manager may see a rep’s whole conversation history with an account. Make sure people know that.
• Bodies or headers. You can store only sender, recipients and time instead of the subject and body. Headers-only is often enough for activity reporting and much safer, though Salesforce notes that some Einstein generative AI features need the full email.
• Deletion. Decide who can delete a captured email and how long you keep activity records. Old activity can be archived to save storage.
• Telling customers. Your privacy notice should say that customer communication is stored in your CRM.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Moving off Salesforce for Outlook and Lightning Sync

Salesforce for Outlook retires on January 30, 2027, according to Salesforce’s retirement notice (the date was moved up from December 2027). After that date it stops syncing contacts, events and tasks, the panel disappears, and admins can no longer change its settings. Lightning Sync has been closed to new customers since Winter ’21 and is scheduled to retire in 2027. Microsoft switches off Exchange Web Services (EWS) in Exchange Online for good on April 1, 2027, after blocking it by default from October 1, 2026, so Lightning Sync connections still on EWS need to move to Microsoft Graph or off Lightning Sync now.

1. List who still uses each tool and what they rely on: contact sync, calendar sync or side panel logging.
2. Set up the Outlook integration and an Einstein Activity Capture configuration that matches the old sync directions.
3. For Lightning Sync, use the migration tool in Setup, which moves users to Einstein Activity Capture.
4. Run both in parallel for a short period with a pilot group, and watch for duplicate events.
5. Switch the old tool off, remove the desktop plug-in, and clear its unresolved items.

Common problems and fixes

• Duplicate events. Two sync tools running at once (old plug-in plus EAC, or EAC plus a third-party tool) create every meeting twice. Fix: one calendar sync per user, and turn the old one off after the pilot.
• Email on the wrong opportunity. Contacts on several open deals confuse the matching. Fix: tune the matching flow and teach reps to relink key threads in the panel.
• Reports show no email. Captured email still sits in the separate EAC store. Fix: turn on Sync Email as Salesforce Activity, and check how much earlier history carries over.
• Storage fills up. Every synced email uses data storage. Fix: project volume per user, store headers only where that is enough, and archive old activity.
• Panel missing for some users. The add-in was not deployed to their group, or Chrome blocks third-party cookies. Fix: check deployment groups and the browser policy.
• Contact sync loops. Two-way contact sync with messy personal address books floods Salesforce with junk contacts. Fix: start one-way, from Salesforce to the mailbox.
• Sensitive mail captured. HR, legal or board emails with an external party land in the CRM. Fix: exclusions before go-live, and headers-only for leadership.

When a third-party tool or custom integration makes sense

Native tools cover most teams. Third-party capture tools and revenue intelligence platforms add richer matching, longer history and their own analytics, usually priced per user per month. A custom integration makes sense when:

• You run an old on-premises Exchange version or a mail system the native tools don’t support.
• Emails must link to custom objects with logic a flow can’t express.
• Retention schedules, legal holds or regulated records need an auditable pipeline.
• You need years of past email history in Salesforce, not just what was captured after go-live.

A typical build reads mail and calendars server-side through the Microsoft Graph or Gmail API, applies your matching and privacy rules, and writes EmailMessage, Task and Event records through the Salesforce API with a dedicated integration user. Simple automations, such as creating a lead from a web-form email, can run in an iPaaS like Zapier, Make or Power Automate.

The ranges come from the API integration cost guide; data migration and history backfill are covered in the cost of data integration. For the wider picture of connecting Salesforce to other systems, start with the Salesforce integration guide.

Go-live checklist

Tick what is already true. It shows how ready your email and calendar integration is.

FAQ

Where Gilzor fits

When native email capture isn’t enough, Gilzor’s engineers can map the data flow, build the integration between your mail system and Salesforce, and support it after launch. See Gilzor’s Salesforce integration services for how these projects are run.