A Guide to Salesloft Salesforce Integration
- Buyer's Guide, Salesforce
- 10 min
- September 17, 2026
Salesloft and Salesforce are designed to work together. Salesloft’s CRM Sync connects sales engagement activity with Salesforce, allowing teams to synchronize records, log activities, map fields, and automate data movement between the two systems.
But there is an important distinction between integrating a sales engagement platform with Salesforce and building a complete record of customer activity and relationships inside Salesforce.
Salesloft’s documentation focuses primarily on what the integration can synchronize. For revenue teams evaluating Salesforce data quality, the more useful question is what happens at the edges of that integration.
What gets captured? What gets written to Salesforce? What object does it become? And what information can still remain outside the CRM?
Get our latest insights into your inbox
What Does Salesloft Capture?
Salesloft captures engagement activity generated through its sales engagement platform, including emails, calls, cadence activity and other seller interactions.
Its Salesforce integration is designed to synchronize both CRM records and activity data. Salesloft says its CRM Sync can automatically record calls and emails as activities in Salesforce, while pushing more than 30 activity properties, including call duration, call disposition, sentiment, email activity counts and cadence identifiers.
The integration also works with Salesforce Leads, Contacts, Accounts and Opportunities.
Salesloft describes the connection as bidirectional, allowing records and field updates to move between Salesforce and Salesloft. Administrators can configure field mappings, determine which system has priority for particular fields, and define synchronization rules.
Salesloft also provides a sync log showing transferred records, fields, timing, direction and outcomes, allowing administrators to troubleshoot failed syncs and mapping errors.
That makes Salesloft more than a simple activity logger. It is designed to keep the sales engagement system and Salesforce synchronized.
But synchronization is not the same thing as comprehensive relationship intelligence.
What Does Salesloft Write to Salesforce?
Salesloft primarily writes two categories of information back into Salesforce.
1. CRM records and field updates
Salesloft can synchronize Salesforce Leads, Contacts, Accounts and Opportunities.
Administrators can configure field mappings and determine the direction and priority of individual fields. Salesloft’s CRM Sync also supports automation rules that can execute actions based on defined criteria.
This means Salesforce can remain the source of important CRM information while Salesloft uses that information to drive sales engagement workflows.
2. Sales activities
Salesloft can write calls and emails into Salesforce as activities.
Those activities can carry additional information such as:
- Call duration
- Call disposition
- Sentiment
- Email activity counts
- Cadence identifiers
- Other activity properties
Salesloft has also expanded its activity logging to account for multiple people involved in an email or meeting. Shared Activity Syncing ensures that emails and meetings involving multiple People are accurately recorded in Salesloft and Salesforce, providing a complete view of interactions across your team and contacts. This feature is crucial for maintaining data integrity and gaining accurate insights.
That is significant for organizations trying to capture more than one stakeholder in a deal.
What about Clari Capture and Salesforce?
The Salesforce integration story becomes more interesting following the Clari-Salesloft merger.
Clari and Salesloft completed their merger on December 3, 2025. The combined company now operates as Salesloft, with Clari Forecast retaining the Clari name while Clari’s broader revenue intelligence, deal management and conversation intelligence capabilities continue under the Salesloft brand.
For existing Clari customers, that creates a practical Salesforce question: What happens to Clari Capture, and how does it fit into the Salesforce activity-capture architecture going forward?
The distinction matters because Clari and Salesloft have historically addressed different parts of the revenue workflow.
Salesloft’s CRM Sync is designed to move sales engagement activity between Salesloft and Salesforce. Clari’s platform has historically used activity and revenue signals to support forecasting, deal inspection and revenue intelligence.
Salesloft’s current platform brings these capabilities together under one company and one broader Predictive Revenue System.
For an existing Clari customer, however, the immediate concern is not the corporate structure. It is the data flow into Salesforce.
What happens to Clari Capture?
The Clari-Salesloft merger raises a very specific Salesforce question for existing Clari customers: What happens to Clari Capture?
Clari Capture was Clari’s activity-capture product. It automatically captured customer interactions, synced activity to the CRM, and could create and enrich contacts based on email and calendar activity. Clari’s own documentation describes Capture as a system that captures contacts and activities, enriches them, and synchronizes them back to the CRM.
That matters because Capture was not simply a reporting feature. It sat in the data path between customer activity and Salesforce.
There is no clear public replacement path yet.Clari and Salesloft now operate as one company under the Salesloft brand. Salesloft says that “the capabilities Clari users rely on today will continue under the Salesloft name” and that Clari Forecast retains the Clari name. It also says that product integration is ongoing and that customers should expect capabilities to deepen over time.
The current Salesloft platform and product pages describe the combined Predictive Revenue System, Salesloft CRM Sync, Clari Forecast and other capabilities. Salesloft has also announced that Clari forecasting, deal intelligence, conversation intelligence and Salesloft engagement data are being brought together in the combined platform.
There is currently no publicly documented migration path that tells an existing Clari Capture customer to move to a specific replacement product, what happens to their existing Capture configuration, or how historical Capture data and Salesforce workflows should be handled.
What Clari Capture used to do matters
Clari’s documentation describes Capture as automatically capturing contacts from calendar invites and email threads, enriching those contacts, creating new contacts in the CRM, and attaching newly identified members of the buying team to the appropriate opportunity.
Clari’s community documentation also shows that Capture had its own logic for deciding when and how activity was written back to Salesforce. For example, Clari documented that Capture could skip writing an activity when it could not determine an exact account match.
So replacing Capture is not simply a matter of changing the name of a product.
It potentially affects:
- How email and calendar activity is captured
- How new contacts are identified
- How contacts are created in Salesforce
- How activities are associated with accounts
- How activities are associated with opportunities
- What historical data remains available
- Which Salesforce objects and fields are populated
- Which other activity-capture products should remain enabled
What should a Clari customer ask?
For an existing Clari customer approaching renewal or reviewing the post-merger Salesforce architecture, the practical questions are straightforward:
- Is Clari Capture still supported for our current deployment?
- If not, what specific Salesloft capability replaces it?
- What happens to our existing Capture configuration?
- Will existing Salesforce activity and contact records remain unchanged?
- What happens to historical Capture data
- How are new contacts captured and created going forward?
- How are activities matched to accounts and opportunities?
- Which users are currently assigned to Clari Capture or another activity-capture mechanism?
- Which users are still syncing through Salesforce Lightning Sync, and which have migrated to Einstein Activity Capture?
- Which system should own activity capture for each user group?
- What happens to historical activity when users move between capture systems?
- What is the migration path and timeline for existing customers?
Salesforce recommends reviewing its Considerations for Migrating to Einstein Activity Capture when moving users from Lightning Sync to Einstein Activity Capture. The migration considerations cover changes to activity capture, data availability and other implications teams should evaluate before making the transition.
The key is to evaluate this at the user level, not assume there is one capture configuration for the entire Salesforce org.
Salesloft and Clari are now one. See how their activity capture compares with Nektar.
The Salesforce configuration matters too
A December 19, 2025 Clari community recommendation stated:
“Salesforce Lightning Sync and Einstein Activity Capture should remain disabled.”
The broader Salesforce configuration also matters when reviewing an existing Clari or Salesloft setup. Salesforce does not support using Einstein Activity Capture and Lightning Sync simultaneously for the same users. Salesforce’s migration documentation describes a transition in which users continue syncing through Lightning Sync until they are assigned the required Einstein Activity Capture permissions; once those permissions are assigned, those users sync through Einstein Activity Capture.
This makes the question a user-level configuration issue rather than an org-wide rule. A RevOps team reviewing its setup should identify which users are still assigned to Lightning Sync, which have been migrated to Einstein Activity Capture, and which activity-capture system is intended to own the sync for each group.
Salesforce is also retiring Lightning Sync, with migration timelines depending on the connected email and calendar system. Salesforce recommends reviewing its Considerations for Migrating to Einstein Activity Capture before making the transition.
For existing Clari customers, the important question is therefore not simply whether Lightning Sync or Einstein Activity Capture is enabled at the org level. It is which users are assigned to which capture mechanism, and how that configuration interacts with the activity-capture system being used by Salesloft/Clari.
The bottom line on Clari Capture
Clari Capture was a real activity-capture and CRM-sync capability. Clari and Salesloft are now one company, and Salesloft says Clari capabilities continue under the Salesloft brand. But Salesloft has not publicly documented a specific replacement or migration path for Clari Capture.
For an existing Clari customer, that makes the status of Capture a question to resolve directly with Salesloft, not something to assume from the merger announcement.
And for anyone evaluating the Salesforce integration today, it is worth separating two questions: What does Salesloft’s current CRM Sync do? And what happens to the activity-capture workflow that previously depended on Clari Capture?
Until Salesloft documents that transition more explicitly, those are not necessarily the same thing.
What Should Clari Customers Clarify?
Before changing an existing Salesforce configuration, teams should establish:
- Is the organization using Clari Capture, Salesloft CRM Sync, or another activity-capture mechanism?
- Which system is responsible for capturing email and calendar activity?
- Where is captured activity stored?
- Which Salesforce objects receive that activity
- What happens to historical activity if the capture configuration changes?
- Is Einstein Activity Capture enabled or disabled?
- Are other Salesforce synchronization tools operating for the same users?
- Which product now owns the relevant activity-capture workflow?
- How are contacts and activities handled when a person is not already represented in Salesforce?
These questions matter because changing the capture layer can change what appears in Salesforce reporting, what data is available to downstream systems, and how historical activity is preserved.
Where Salesloft Stops
Salesloft can synchronize a substantial amount of engagement and CRM data. But the integration remains centered on Salesloft activity and the CRM records connected to that activity.
That distinction matters.
A Salesforce record can tell you that an email happened, a call happened, who was involved and which cadence generated the activity. It does not necessarily mean Salesforce now contains the complete history of every customer interaction across the revenue organization.
Activities that happen outside Salesloft remain outside the Salesloft-to-Salesforce activity stream.
For example, a buyer interaction can happen through:
- A rep’s normal email workflow
- A meeting that wasn’t captured through the engagement platform
- Conversations involving customer success
- Executive-to-executive communication
- Partner interactions
- Other channels outside the Salesloft workflow
The Salesforce integration does not turn every external customer interaction into a Salesloft activity simply because Salesforce is connected.
That is the boundary worth understanding.
What Does This Mean for Salesforce Reporting?
For sales engagement reporting, Salesloft’s Salesforce integration can provide useful structured activity data.
Salesloft highlights the ability to combine Salesloft and Salesforce data for analytics and attribution. Its Salesforce integration supports automation rules and detailed activity properties, while the platform provides a sync log to monitor data moving between the systems.
But Salesforce reporting is only as complete as the data that reaches Salesforce.
If Salesforce contains Salesloft activity but not the activity happening outside Salesloft, reports can still provide an incomplete picture of account engagement.
That can affect questions such as:
- How many stakeholders are actually engaged?
- Which people have interacted with the account?
- How many conversations happened across the entire account?
- Which relationships are strongest?
- What activity happened outside the sales engagement workflow?
- How much customer context exists before an opportunity moves stage?
The integration improves the activity record.
It does not automatically make Salesforce the complete system of relationship context.
What Does This Mean for AI in Salesforce?
AI systems need more than activity volume. They need connected, contextual data.
An AI system working from Salesforce can reason over the information that actually exists in the CRM. If the CRM contains a detailed record of Salesloft activity but customer interactions are distributed across other channels, the model is working from a partial context window.
That can affect AI-generated:
- Opportunity summaries
- Account research
- Buying-group identification
- Next-step recommendations
- Relationship analysis
- Forecasting signals
The issue isn’t whether Salesloft captures data well. It is what happens to the customer context that never passes through Salesloft.
Salesloft can make Salesforce more complete for Salesloft-generated activity. It does not, by itself, make Salesforce a complete record of every customer relationship.
Salesloft + Salesforce: The Practical Takeaway
Salesloft’s Salesforce integration is built to synchronize CRM records and sales engagement activity between two systems.
The important distinction for RevOps teams is between Sales engagement synchronization and complete customer context in Salesforce.
Salesloft’s current CRM Sync provides bidirectional synchronization for Leads, Contacts, Accounts and Opportunities, automatic activity logging, field mapping, automation rules and visibility into synchronization activity.
Following the Clari-Salesloft merger, existing Clari customers also need to understand how their current activity-capture architecture fits into the combined platform and which system is responsible for getting activity into Salesforce. The combined company says the capabilities Clari customers rely on continue under the Salesloft brand, with Clari Forecast retaining its name.
If the objective is to understand what Salesloft captures and writes to Salesforce, the vendor’s CRM Sync provides extensive capabilities.
If the objective is to understand every person, relationship and interaction surrounding an account, the integration’s boundaries become equally important.
Read our other Integration Guides
About Nektar
Nektar helps revenue teams turn Salesforce into a more complete source of customer context.
While sales engagement and conversation platforms capture activity within their respective workflows, customer context is often spread across emails, calendars, meetings and interactions across the revenue organization. Nektar brings that activity together and connects it to the right people, accounts, opportunities and relationships in Salesforce.
The result is a more complete view of who is involved, what is happening, and how the customer relationship is evolving, giving RevOps teams better data for reporting, account intelligence, buying-group visibility and AI-powered workflows.
Enjoyed our content? Follow Nektar on LinkedIn
