Connect for Outlook
Connect for Outlook was Salesforce first Outlook plugin, a desktop add-in released in the early 2000s that synced contacts, events, and tasks between Outlook and Salesforce and added a Salesforce panel to Outlook so users could log emails as activities on Salesforce records.
Definition
Connect for Outlook was Salesforce first Outlook plugin, a desktop add-in released in the early 2000s that synced contacts, events, and tasks between Outlook and Salesforce and added a Salesforce panel to Outlook so users could log emails as activities on Salesforce records. It ran inside the Outlook desktop client, used the SOAP API to talk to Salesforce, and shipped as an MSI installer that admins pushed to user laptops.
Salesforce retired Connect for Outlook in 2014, replaced it with Salesforce for Outlook (also now retired as of June 2024), and the current supported product is Outlook Integration paired with Einstein Activity Capture. Connect for Outlook still appears in legacy training material and on long-running Salesforce orgs where some user laptop never had the plugin uninstalled. The functionality lives on through the modern stack, but the install path, sync behavior, and field mappings are all different.
What Connect for Outlook did and how Salesforce replaced it
The features Connect for Outlook shipped
The plugin added a Salesforce sidebar to the Outlook desktop app. From there, users could log an open email as a Task on a Contact or Account, sync their Outlook calendar to Salesforce Events, and sync Outlook Contacts to Salesforce Contacts. The sync was bidirectional and ran on a schedule the user configured. Field mappings were limited: name, email, phone, address, and a few custom fields the admin had pre-mapped at the org level.
How the sync engine worked
The sync ran on a timer inside the user Outlook session. Every sync cycle, the plugin queried Salesforce through the SOAP API for changes since the last sync, applied them to Outlook, then walked Outlook for changes and pushed them to Salesforce. Conflicts were resolved on a last-write-wins basis with a preferred-side setting the user picked at install time. The pattern is the same idea behind modern sync but without modern conflict tools and without delta APIs.
Connect for Outlook vs Salesforce for Outlook
Confusingly similar names, different products. Connect for Outlook was the original (early 2000s through 2014). Salesforce for Outlook came next (2010 through 2024 retirement) and was a complete rewrite with a cleaner UI, broader field mapping, and better support for newer Outlook versions. Both ran on the desktop. Both used the SOAP API. Both are now retired. The current product is Outlook Integration, which runs as a Microsoft 365 cloud add-in rather than a desktop install.
Why Salesforce retired Connect for Outlook
Two reasons. First, Outlook itself moved away from heavy desktop add-ins toward Microsoft 365 web add-ins, which Connect for Outlook could not support. Second, the SOAP-based auth and sync model did not scale to the larger orgs and bigger sync volumes of the late 2000s. The plugin would silently fail to sync, corrupt records on conflict, or simply hang the user Outlook session. By 2012, Salesforce for Outlook had been pushing users to migrate for several years, and the retirement notice landed in 2014.
The current replacement: Outlook Integration plus Einstein Activity Capture
Outlook Integration is the modern UI piece. It is a Microsoft 365 add-in that installs from the Microsoft store, runs inside Outlook on desktop and web, and surfaces Salesforce records in a side panel. Users log emails, create activities, and view Salesforce data without leaving Outlook. Einstein Activity Capture is the modern sync piece. It runs server-side, syncs emails and calendar events from Microsoft 365 or Google Workspace into Salesforce, and uses AI to match contacts and surface insights. The split between UI and sync is intentional; Connect for Outlook tried to do both in one desktop plugin, which is what made it brittle.
Migration path for orgs still on Connect for Outlook
Most orgs migrated years ago, but a few long-running deployments still have user laptops with the plugin installed even though it stopped working when Salesforce shut down the SOAP endpoints. The migration is straightforward: uninstall the plugin from each user laptop (often through SCCM or a similar enterprise tool), install Outlook Integration from the Microsoft 365 store, and enable Einstein Activity Capture per user from Salesforce Setup. Custom field mappings from Connect for Outlook need to be re-created in EAC; they do not import.
Why this still comes up
Connect for Outlook references persist in old Salesforce training videos, knowledge articles, and partner solution documentation. Anyone learning Salesforce from materials published before 2015 will encounter the product. The relevant action today is to recognize it as retired, point to the modern replacement, and not waste cycles trying to install or troubleshoot it.
How to migrate off Connect for Outlook
Connect for Outlook is retired and cannot be reinstalled. The actionable workflow is removing leftover installs and moving users to the current Outlook Integration plus Einstein Activity Capture combination.
- Audit the user base for legacy installs
Run a software inventory across user laptops (SCCM, Jamf, Intune, or your endpoint tool) and identify machines with Connect for Outlook still installed. Some IT teams discover hundreds of dormant installs that no one has touched in years.
- Uninstall the plugin
Use the standard MSI uninstall command or your endpoint management tool. The plugin is harmless when SOAP endpoints are off but consumes Outlook startup time and adds a non-functional sidebar.
- Install Outlook Integration from the Microsoft 365 store
From Microsoft 365 admin center, deploy the Salesforce Outlook add-in to the same users. The add-in installs centrally and applies to Outlook on desktop and web. No per-user setup needed.
- Enable Einstein Activity Capture
In Salesforce Setup, search for Einstein Activity Capture, enable it for the org, and create EAC configurations that assign specific users to specific sync settings. EAC supports both Microsoft 365 and Google Workspace.
- Re-map custom fields
Connect for Outlook custom field mappings do not migrate. List the custom fields you were syncing (typically Account, Contact, Lead, Event, Task custom fields) and re-create equivalent EAC mappings or, where EAC cannot, use a Flow to write the data on email or event capture.
- Notify users and train
Send a one-page guide on what changed. The UI is different, the sync is server-side rather than desktop, and there is no longer an Outlook sidebar config screen the user controls.
- Connect for Outlook installs are persistent. Users who left the company years ago still appear in the install inventory until IT removes them.
- EAC is opt-in per user; bulk-enabling sends each user a notification email. Coordinate with internal communications before flipping the switch.
- EAC does not write captured activities to standard Task or Event records by default; it stores them in its own object schema. Reports built on Task and Event may show a drop after migration unless you reconfigure.
- Outlook Integration requires Office 365 mail accounts. On-prem Exchange or POP/IMAP accounts cannot use the modern add-in.
- Field mappings have to be re-created in EAC. There is no migration tool from Connect for Outlook config to EAC config.
Trust & references
Cross-checked against the following references.
- Salesforce Connect for Outlook RetirementSalesforce Help
- Outlook Integration OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Connect for Outlook.
- Einstein Activity Capture OverviewSalesforce Help
- Inbox OverviewSalesforce Help
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 Connect for Outlook used for?
Q2. What modern tools have replaced Connect for Outlook?
Q3. Why is Einstein Activity Capture an improvement over Connect for Outlook?
Discussion
Loading discussion…