The Salesloft Data Sync App is a Salesforce managed package known as an External Client Application (ECA) that replaces the legacy Connected App as Salesloft's required CRM integration.
Migrating your team from the legacy Salesforce Connected App to the Salesloft ECA is a required, multi-step process.
The migration happens in phases: admin installs and connects the Salesloft Data Sync App, users re-authenticate their personal Salesforce connections, and the admin removes the legacy Connected App. Use this guide to coordinate and complete the full migration.
After completing this guide, you will be able to:
- Understand the full migration sequence and what happens at each phase
- Verify that all users have successfully re-authenticated via the Salesloft Data Sync App
In this article:
Before starting, confirm you have completed the following:
- You are a Salesloft Admin.
- Your team is on one of the following Salesforce editions: Professional (with API access), Enterprise, or Unlimited.
- The Salesloft ECA package must be installed in your Salesforce org and authorized via OAuth in Salesloft â see Install the Salesloft ECA from AppExchange.
- We recommend using the Google Chrome browser.
- Confirm your team's Salesforce domain setup: If your org uses a custom Salesforce domain, confirm that users will be routed to the correct domain during the OAuth re-authentication flow.
Things to Note: No admin action is required to remove the legacy Connected app. Salesloft will decommission the legacy Connected App in the fall of 2026. Customers should migrate to the Salesloft Data Sync app by September 2, 2026. When decommissioning occurs, any users who have not yet re-authenticated via the Salesloft Data Sync App will be force-disconnected. We recommend ensuring all users re-authenticate promptly to avoid disruption.
The migration follows sequential phases. Phases 1 is covered in a separate guide. This guide focuses on Phases 2.
|
Phase
|
Who acts
|
What happens
|
|
1. Admin installs and connects ECA
|
Admin
|
Salesloft Data Sync App
is installed from AppExchange and authorized via OAuth. This ECA takes precedence for the integration user. Individual user connections remain on the Connected App.
|
|
2. Users re-authenticate
|
All Salesloft users
|
Each user completes a one-time OAuth flow to connect their personal Salesforce account via the ECA, Salesloft Data Sync App.
|
Things to Note: Phase 1 (install and OAuth connection) must be completed before proceeding. If you have not completed these steps, see Install and Connect the Salesloft Data Sync App from Salesforce Marketplace.
After the admin installs and connects, users should re-authenticate their individual connection. Re-authenticating means that the user needs to disconnect from the previous connection and connect to the new one.
Communicate the change to your team
Notify your users that they need to re-connect their Salesforce account. Key points to communicate:
- The re-authentication is a one-time action and takes under a minute to complete.
- Users will see a prompt in Salesloft when they need to re-authenticate. They should not ignore it. Users who do not reconnect will eventually lose connection as the deadline approaches if they don't.
Things to Note: If the Salesloft Data Sync App has been installed for a team, users can connect to Salesforce via the app, even before the admin does.
Monitor re-authentication progress
- Open Connected Apps OAuth Usage: Confirm each user's CRM connection status in Salesforce.
- Check the connected count for the Legacy Connected App: Go to Apps > Connected Apps > Connected Apps OAuth Usage. Search for the connected app Salesloft and click on User Count.
- See who has connected to the Salesloft Data Sync App: Go to External Client Apps â OAuth Usage â Salesloft SF Sync â Click User Count
- Identify users who have not re-authenticated: Review the list of users and identify any whose Salesforce connection shows as disconnected or still using the Connected App.
- Follow up with disconnected users: Contact any users who have not re-authenticated and direct them to the user-facing re-authentication guide: Connect Your Salesforce Account from the Salesloft Data Sync App in Salesforce Marketplace.
Once your integration user has re-authenticated via the Salesloft Data Sync App, you may choose to proactively revoke access to the legacy Connected App for all users. This is optional â if you take no action, Salesloft will revoke access to the legacy Connected App on your team's behalf after the migration deadline.
- If you do nothing: Salesloft will revoke access to the legacy Connected App automatically after the migration deadline. Users who have not yet re-authenticated will be prompted to reconnect at that time.
- If you want to act now: Revoking access yourself pulls prompts all users to reconnect to the new Salesloft Data Sync App immediately rather than waiting for Salesloft's automatic disconnection after the migration deadline.
To revoke access and uninstall the legacy Connected App, follow Steps 3 and 5 in Salesforce's Manage a Connected App's Current Sessions article.
The migration is complete when:
- All users show a connected status in Salesloft â no users are showing a disconnected status.
- CRM activity logging and deal sync are functioning normally for all users â no sync errors appear in the CRM Sync Logs.
Q: What is changing with this migration?
Salesloft is moving from the legacy Salesloft Connected App to the new Salesloft Data Sync (External Client App, or ECA). The ECA handles the OAuth connection that syncs data between Salesloft and Salesforce. No other systems or configurations are affected.
Q: What is the Salesloft Data Sync (ECA) package ID?
The managed package ID is 04tcv000000StRNAA0
Q: What action is required from users?
Each user must disconnect from the legacy Connected App and re-authenticate via OAuth to the new Salesloft Data Sync (ECA) within their Salesloft settings. Once they do, activity logging to Salesforce will resume as normal.
Q: What happens if users don't reconnect before September 2nd?
Users who have not reconnected by September 2nd will be automatically disconnected. To ensure a clean cutover, we recommend that admins revoke access to all users from the legacy Connected App within Salesforce after the new ECA is installed. This will prompt each user to reconnect the next time they log into Salesloft.
Q: Does the authentication method change?
No. The ECA requires the same Username-Password OAuth flow for both end users and the integration user â consistent with how the legacy Connected App operates. If preferred, an API-only user can be leveraged for the integration user.
Q: Are any configuration changes required?
No. Field mappings, sync logic, activity logging settings, user mappings, automation rules, permission assignments, and reporting/dashboards all live within the Salesloft app and are unaffected by the ECA migration.
Q: Will existing functionality continue to work after migration?
Yes. CRM sync, activity logging (Tasks, Emails, Calls, Meetings), cadence-related automation, and person, opportunity and account synchronization are all unaffected. The only action required is user re-authentication with the new ECA.
Q: Are there any changes to permissions or the security model?
No. The existing integration user will work with the new ECA as-is. No new Permission Sets, Permission Set Groups, or additional object/field-level permissions are needed. It's also worth noting that the app scopes are not changing â the ECA requests the same permissions as the legacy Connected App.
Q: Is a security review required?
If your organization's policies require a review for authentication model changes, we recommend looping in your internal security team. The primary change is the mechanism by which the OAuth token is fetched, not what it has access to.
Q: What about Apex code, Named Credentials, middleware, or custom automation?
There is no impact on any of these. The Salesloft Data Sync (ECA) is solely responsible for the OAuth connection â nothing else depends on it.
Q: What about the Salesloft Insights managed package and Custom Flows?
The Salesloft Insights managed package should be updated as part of this process. The updated version adds two new record-triggered flows that are disabled by default â no existing reports, dashboards, fields, permission sets, or functionality are changed. This package is entirely separate from the Salesloft Data Sync (ECA) and has no bearing on the migration itself.
Q: What does the admin need to do to install the new ECA?
When the admin installs the Salesloft Data Sync (ECA), they will be prompted to grant access to all users in the Salesforce org. Access is self-limiting â only users with an active Salesloft login will be able to authenticate.
If you run into issues during the migration, check the table below. For broader Salesforce integration troubleshooting, see the Salesforce Troubleshooting Guide.
|
Problem
|
Likely cause
|
Fix
|
|
User re-authenticates but lands on the Connected App flow instead of the Salesloft Data Sync App
|
The user's browser has a cached session
|
Ask the user to clear their browser cache, log out of Salesforce entirely, and retry the re-authentication.
|
Next:
Related:
Troubleshooting: