Salesforce for Outlook
Salesforce for Outlook was a desktop application that connected Microsoft Outlook to Salesforce so sales reps could sync contacts, events, and tasks, and relate Outlook emails to Salesforce records.
Definition
Salesforce for Outlook was a desktop application that connected Microsoft Outlook to Salesforce so sales reps could sync contacts, events, and tasks, and relate Outlook emails to Salesforce records. It installed locally on each Windows machine and ran from the system tray, syncing data in the background based on settings an admin defined in Outlook configurations.
This product is retired. Salesforce set its full retirement for December 2027, after earlier targets of June 2023 and June 2024, and the create-record action menu was already removed in Summer 2021. The replacements are the Outlook Integration (a side panel inside Outlook) and Einstein Activity Capture (automatic email, event, and contact sync). If you still see Salesforce for Outlook anywhere in your org, treat it as legacy and plan the move.
From a desktop sync client to a retired product
What Salesforce for Outlook actually did
Salesforce for Outlook (often shortened to SFO) was a client application that each user installed on a Windows PC. Once installed, it placed an icon in the system tray and ran quietly in the background. Its main job was two-way sync. Contacts, calendar events, and tasks could flow between a rep's Outlook mailbox and their Salesforce records, so updating a meeting in one place updated it in the other. Email was handled differently. SFO did not sync every email automatically. Instead, it added a side panel to the Outlook reading pane that searched Salesforce for records matching the addresses in the From, To, and CC lines. A rep could then add a selected email, and any attachments, to one or more of those matched records. This kept email out of the heavy background sync while still letting reps log the messages that mattered. An admin controlled all of this through Outlook configurations in Setup. Those settings decided which records synced, in which direction, and how conflicts resolved. Because the client lived on the desktop, it depended on supported versions of Outlook and Exchange, originally as far back as Outlook 2010 and Exchange 2010.
Why it was retired
The retirement reflects a broader shift away from locally installed desktop software toward cloud-hosted add-ins. A desktop client has real costs. It needs to be pushed to every machine, patched when Outlook or Windows changes, and supported across versions that Microsoft itself eventually drops. Reps working from a browser, a Mac, or a phone got little benefit from a Windows tray application. Salesforce announced the retirement in stages. Early release notes pointed to June 2023, then the date moved to June 2024, and the current plan sets full retirement for December 2027. Ahead of that, Salesforce removed the action menu that created new Salesforce records from inside Outlook in Summer 2021, so part of the product stopped working years before the full shutdown. The newer products are add-ins and services that Salesforce hosts. They do not require a per-machine install, they run inside the modern Outlook clients including the web version, and they line up with Lightning Experience rather than the older interface. That direction is why the desktop client was wound down rather than updated.
The Outlook Integration replacement
The Outlook Integration, which you may also see called Lightning for Outlook, is the direct successor to the SFO side panel. It is an add-in that appears inside Outlook on the desktop and on the web. From that panel a rep can see Salesforce records that match an email, log the email and its attachments to those records, and create new records without leaving the inbox. The integration covers the manual, in-the-moment work that reps do while reading and writing mail. Logging an email to an opportunity, relating an event to an account, or checking a contact's recent activity all happen in the side panel. With Inbox features added, the same panel can show email tracking, suggested times for meetings, and email templates. The key difference from SFO is delivery. There is no desktop executable in the system tray. The admin enables the integration in Setup and assigns it to users, and the panel shows up in their Outlook. That removes the install-and-patch burden that made the old client expensive to run, while keeping the side-panel workflow reps were used to.
The Einstein Activity Capture replacement
Einstein Activity Capture (EAC) replaces the background sync half of Salesforce for Outlook. Where SFO synced contacts, events, and tasks based on Outlook configurations, EAC connects a user's email and calendar account to Salesforce and captures activity automatically. Emails and events tied to Salesforce contacts and leads are surfaced on the related records without the rep logging each one by hand. EAC also keeps contacts and events in sync between the connected mailbox and Salesforce. Because it works at the account level rather than through a desktop client, it supports both Outlook and Gmail, and it runs regardless of which device the rep uses to read mail. One difference worth planning for is where captured email lives. EAC stores much of the captured activity data on Salesforce-managed infrastructure rather than as standard Task records, which changes how that data appears in reports compared with the old logged-activity model. Teams that depend on reporting over every email should confirm the behavior they need before rolling EAC out broadly, and pair it with the Outlook Integration when reps still want to log specific messages by hand.
What happens to your data and configurations
A common worry with any retirement is data loss. For Salesforce for Outlook, the contact, event, task, and email information that already synced into Salesforce stays where it is. Retirement does not delete records that the client previously created or updated. The Outlook side of that data, the items in the user's mailbox, also remains untouched. What goes away is the client and its settings. Once SFO is retired, admins and users lose access to Outlook configurations, the Setup area that governed sync direction and behavior. The desktop client stops syncing, and any workflow that relied on the tray application or its action menu no longer functions. That split matters for migration planning. Because the synced data survives, the move is mostly about re-establishing the live connection through the new tools rather than rescuing old records. An admin maps the features the team relied on, such as side-panel logging or contact and event sync, to the Outlook Integration and Einstein Activity Capture, then enables those for the same users. Historical records continue to exist alongside the new activity that the replacements capture.
How to recognize SFO in a legacy org
Because Salesforce for Outlook ran for many years, plenty of orgs still carry traces of it. Knowing the signs helps you scope a cleanup. On a user's machine, the clearest signal is the Salesforce for Outlook icon in the Windows system tray and a separate side panel docked in the Outlook reading pane that is branded for the desktop client rather than the modern add-in. In Setup, look for Outlook configurations and the older Email-to-Salesforce style settings tied to the desktop sync. Profiles or permission sets may still reference SFO access even when no one actively uses it. Release notes in older orgs will also mention the retirement timeline, which is a useful prompt to act. The practical move is to confirm whether anyone still depends on the client, then enable the Outlook Integration and Einstein Activity Capture for those users and switch them over. After the team is on the replacements, the legacy configurations can be retired and the desktop client uninstalled from machines. Doing this before December 2027 avoids a sudden loss of email logging and sync when the product fully shuts down.
Trust & references
Cross-checked against the following references.
- Salesforce for Outlook RetirementSalesforce
- Salesforce for Outlook Is RetiringSalesforce
Straight from the source - Salesforce's reference material on Salesforce for Outlook.
Hands-on resources to go deeper on Salesforce for Outlook.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What was Salesforce for Outlook before it was retired in June 2024?
Q2. Is Salesforce for Outlook still part of the supported Salesforce product set today?
Q3. Which modern feature provides the automatic email and calendar sync that Salesforce for Outlook once did?
Discussion
Loading discussion…