To connect Outlook or Gmail to Salesforce, most teams install Salesforce's own side-panel add-in for their mail client. They then decide whether reps log messages one at a time or Einstein Activity Capture records them automatically. Calendar and contact sync come from Activity Capture or a third-party tool. Lightning Sync is being retired, so new setups should not depend on it. Choose the approach based on what you need to report on, not on what sounds most automatic.
What are the main ways to connect Outlook or Gmail to Salesforce?
There are four families of options: the native mail add-ins, Einstein Activity Capture, Salesforce Inbox, and third-party sync products. They overlap, and most orgs combine two of them.
| Option | What it does | Who drives it | Watch for |
|---|---|---|---|
| Outlook integration / Gmail integration | Shows Salesforce records beside an open email; lets reps log emails and events to records | The rep, message by message | Logging depends on rep habit |
| Einstein Activity Capture | Captures emails and events automatically and can sync contacts and calendars | Admin-defined rules and configurations | Where captured data is stored and who can see it |
| Salesforce Inbox | Adds productivity features such as tracking and scheduling inside the add-in | The rep, with an extra license | Separate licensing; confirm packaging |
| Third-party sync tools | Server-side capture, broader calendar sync, or richer matching rules | Admin or IT | Security review and another vendor to manage |
How do the Outlook and Gmail side panels work?
The add-in opens a Salesforce pane inside the mail client. It surfaces the related contact, lead, account and open opportunities, and lets reps log the email or meeting to the right records.
For Outlook, each user needs the Salesforce add-in. Users can install it from Microsoft AppSource, or Exchange admins can push it with Microsoft Centralized Deployment. Salesforce's implementation guide also describes a file-based install for locked-down tenants.
For Gmail, the integration runs through the Salesforce extension for Chrome. Salesforce's requirements list Gmail on a Google Workspace domain and a recent Chrome version.
Both integrations are available across Sales Cloud, Service Cloud and Lightning Platform editions from Essentials and Group upward. Admins can design the pane in Lightning App Builder, so a service agent and an account executive see different components.
The panels do not capture anything on their own. If a rep never clicks to log, Salesforce never sees the conversation.
What does Einstein Activity Capture do, and where does its data live?
Activity Capture connects each user's mailbox and calendar to Salesforce and records relevant emails and events against matching contacts, leads, accounts and opportunities. It can also sync contacts and events in both directions.
Historically, emails captured this way were not saved as standard Activity records. They appeared on the activity timeline but sat outside normal reports. Salesforce added separate Activity 360 reports and an Activities dashboard to fill the gap.
That has been changing. Salesforce now offers an architecture called Sync Email as Salesforce Activity, which stores captured email as Salesforce records. Those records can then feed standard reports, flows and the API.
Salesforce Help says Activity 360 reports, the Activities dashboard, Activity Metrics and Recommended Connections retire in Spring '27. Orgs still on the older storage model should plan the move before then.
Two settings matter for privacy. Admins can capture full email content or headers only, meaning sender, recipients and timestamp. Admins can also maintain an excluded addresses list that applies to every Activity Capture user.
What is happening to Lightning Sync and Salesforce for Outlook?
Both legacy products are on the way out. Lightning Sync is retiring in 2027, and Salesforce for Outlook is marked as retiring, with retirement now set for December 2027.
Timing for Lightning Sync depends on how it connects. Microsoft began shutting down Exchange Web Services for Exchange Online in October 2026, and Lightning Sync configurations still on EWS stop syncing. Salesforce added Microsoft Graph authentication as a stopgap, so switch any remaining configuration to Graph now and plan the move to Activity Capture before the 2027 retirement.
Salesforce's recommended path is Activity Capture for sync plus the Outlook or Gmail integration for the side panel. One caveat matters for mixed orgs: Salesforce notes Activity Capture requires Sales Cloud licenses. Teams on other license types should check their options with Salesforce.
Where does Salesforce Inbox fit?
Inbox is an add-on that layers productivity features onto the existing Outlook or Gmail integration. It is not a separate mail client.
Admins enable it from the integration setup page and assign one of two permission sets, with or without Activity Capture. According to Salesforce's guide, all Inbox features also come with Sales Engagement or Sales Cloud Einstein, and some come with Sales Cloud editions.
Packaging in this area has shifted several times. The older standalone Inbox apps were retired in 2021. Confirm what your contract includes before planning around any specific feature.
When does a third-party sync tool make sense?
A third-party product earns its place when native options leave a gap you cannot close with configuration. Common categories are server-side capture tools, calendar and contact sync utilities, and revenue intelligence platforms that log activity as a side effect.
- Server-side capture: connects at the mail server rather than the user's client, useful when reps cannot be relied on to authorize anything.
- Calendar and contact sync: fills gaps for teams outside Sales Cloud licensing or with complex shared calendars.
- Matching control: some tools let admins write detailed rules for which record an email attaches to.
- Conversation platforms: call and meeting tools that also push emails and meetings into Salesforce.
Every added tool means another security review, another integration user and another failure point. Treat it as a deliberate decision, not a default.
What actually syncs between the inbox and Salesforce?
Three kinds of data can move: emails, calendar events and contacts. Each behaves differently, so decide on each separately.
- Emails: logged manually through the add-in, or captured automatically by Activity Capture and matched to records by address.
- Events: meetings can be logged one by one or synced continuously, with options for which event types appear in Salesforce.
- Contacts: contact sync can create noise fast if personal address books flow into the CRM, so set direction and filters carefully.
- Attachments: handling varies by method and storage model; test with real files before go-live.
Salesforce Help also notes a limit on historic capture during initial setup. Plan for older history to stay in the mailbox, not in Salesforce.
Which emails should never land in Salesforce?
Anything personal, privileged, or about employees and board matters should stay out. Automatic capture makes this a design question, not a training reminder.
- HR conversations, performance reviews and anything about a colleague's health or pay.
- Legal counsel, privileged advice and dispute correspondence.
- Board, investor and acquisition discussions.
- Personal email that happens to reach a work mailbox.
- Messages containing regulated personal or financial data your policies keep out of the CRM.
Use the excluded addresses list for known domains and senders, such as outside counsel and the HR team. Consider header-only capture for roles that touch sensitive material. Review sharing settings so captured email is not visible to the whole org by default.
Involve legal and IT before switching on automatic capture. They will ask where the data is stored, who can see it, and how long it is retained.
What does an admin need to set up?
Setup touches three groups: the Salesforce admin, the Microsoft 365 or Google Workspace admin, and the users themselves. Plan them together.
- Decide the operating model first: selective logging, automatic capture, or both.
- In Salesforce Setup, open Outlook Integration and Sync or Gmail Integration and Sync and enable record access.
- For Outlook, turn on Email to Salesforce and Enhanced Email.
- Have the mail admin approve the Salesforce app for the tenant and deploy the add-in centrally where possible.
- Assign permission sets for the integration, Inbox and Activity Capture as needed.
- If you use Activity Capture, build configurations, excluded addresses and sharing settings before adding users.
- Build email application panes per role in Lightning App Builder.
- Pilot with a small group, check matching quality, then widen.
How does each approach change activity reporting?
Manual logging produces standard activity records you can report on immediately. Automatic capture produces more volume, and its reporting value depends on the storage model.
With manual logging, the numbers are clean but incomplete. They show what reps chose to log, which skews toward deals in progress.
With Activity Capture on Sync Email as Salesforce Activity, captured email becomes reportable like other activity. Orgs still on the older model rely on Activity 360 reporting, which Salesforce has scheduled for retirement.
Either way, volume is not engagement. A busy timeline can hide the fact that no senior buyer has replied for a long time.
Which approach fits your team?
Start from the business question, then pick the lightest method that answers it.
| Your need | Best starting point | Why |
|---|---|---|
| Reps want record context while emailing | Outlook or Gmail integration alone | Lowest setup effort; no automatic capture to govern |
| Log only meaningful customer emails | Integration with manual logging | Keeps records deliberate and reports on standard activity |
| Leaders want full engagement history on accounts | Activity Capture on Sync Email as Salesforce Activity | Automatic coverage that still lands in standard reporting |
| Calendar and contact sync with Outlook or Google | Activity Capture, or a third-party sync tool | Replaces Lightning Sync and Salesforce for Outlook |
| Sensitive roles in the same org | Exclusions plus header-only capture | Limits what is stored while keeping activity counts |
| Users without Sales Cloud licenses | Confirm options with Salesforce, or evaluate a third-party tool | Activity Capture licensing may not cover them |
What mistakes do teams make with email integration?
Most problems come from switching on capture before deciding what it is for. These come up repeatedly.
- Turning on automatic capture org-wide with no excluded addresses or sharing review.
- Promising leadership activity dashboards before checking where captured email is stored.
- Leaving Lightning Sync in place without a migration plan before its retirement.
- Letting contact sync pour personal address books into Salesforce.
- Assuming the side panel logs email by itself, then blaming reps for empty timelines.
- Skipping a pilot, so matching errors attach emails to the wrong accounts at scale.
Email integration is one of the cheapest ways to reduce rep data entry, which helps adoption. Treated carelessly, it fills Salesforce with noise and exposes conversations that should never be there.
