Salesloft + Salesforce Integration Guide: Full Setup 2026

The Salesloft Salesforce integration is the backbone of most Salesloft deployments: when it is configured well, every call, email, and meeting logs itself, and reps live in one system instead of two. When it is configured badly, you get duplicate records, sync conflicts, and a CRM full of noise that ops spends Fridays cleaning up.

This guide walks through the full setup in 2026, connection, field mapping, sync rules, and the mistakes that cause most of the pain. We integrate sequencers with CRMs constantly when building outbound systems, so this is written from the trenches.

Before You Start: Prerequisites

You will need:

• A Salesloft plan that includes CRM sync (team tiers and above)
• Salesforce Professional edition or higher with API access enabled
• A Salesforce integration user with appropriate permissions (read/write on Leads, Contacts, Accounts, Opportunities, Activities)
• Admin rights in both systems

The dedicated integration user matters more than people expect. If the sync runs under a personal admin login and that person leaves or changes permissions, the integration silently breaks.

Step 1: Connect the Accounts

1. In Salesloft, go to Settings → Integrations → CRM and choose Salesforce.
2. Authenticate via OAuth using the integration user credentials.
3. Choose the environment: production or sandbox. Run your first configuration in sandbox if your Salesforce org is heavily customized.

The connection itself takes minutes. Everything that matters happens in the next three steps.

Step 2: Configure Object Sync

Salesloft syncs People to Salesforce Leads or Contacts, and Accounts to Accounts. The key decisions:

Lead vs. Contact mapping. If your Salesforce model uses Leads for new prospects, map Salesloft-created people to Leads and let your existing conversion process promote them. If you run an account-based model without Leads, map directly to Contacts under matched Accounts.

Record creation rules. Decide whether Salesloft can create new Salesforce records or only update existing ones. For most orgs, allowing creation with duplicate matching on email is right, but turn on Salesforce duplicate rules first.

Sync direction per field. This is the big one. For each mapped field, choose Salesforce-wins, Salesloft-wins, or most-recent-wins. Set ownership deliberately: CRM should own firmographic truth (account fields, lifecycle stage), the sequencer owns engagement state.

Step 3: Map Fields Minimally, Then Expand

Start with the core set:

Resist mapping every custom field on day one. Every additional bidirectional field is a future conflict, and unwinding a bad mapping after months of sync is painful.

Step 4: Configure Activity Logging

This is the integration's main payoff. In Settings → Activity Logging, enable logging for emails, calls, and meetings, and decide:

• Log as Tasks vs. Email Message objects: Email Message objects give richer reporting but consume more storage.
• Sentiment and disposition mapping: map Salesloft call dispositions to your Salesforce call outcome picklist so reporting stays consistent.
• Sequence step context: include sequence and step names in the activity subject so anyone reading the record sees where the touch came from.

Step 5: Test, Then Roll Out

Pick 2-3 reps, run them for a week, then check: do new prospects appear correctly? Do activities log once (not twice)? Do field values hold, or do they flip back and forth between systems (the classic sign of a direction conflict)?

Only then roll out org-wide.

Common Problems and Fixes

Duplicate records. Usually caused by allowing creation without duplicate matching, or by reps importing CSVs into Salesloft that already exist in Salesforce under different emails. Fix: enforce email matching and Salesforce duplicate rules.

Field ping-pong. A field flips values on every sync because both systems claim ownership. Fix: set one direction per field, no exceptions.

Activities logging twice. Typically the Salesforce email sidebar and Salesloft both logging the same email. Disable one logging path.

Validation rule failures. Salesforce rejects Salesloft updates because required fields are missing. Fix: either provide defaults in mapping or exempt the integration user from specific validation rules.

The Bigger Picture: Integration Is Not a Strategy

A clean Salesloft Salesforce sync keeps data tidy. It does not create pipeline. The work that fills the system, list building, verification, deliverability infrastructure, messaging, and sequencing strategy, sits upstream of any integration, and that upstream is where most outbound programs actually fail.

That upstream system is our specialty. At LeadHaste, we orchestrate 20+ tools, sequencers and CRMs included, into one outbound machine that delivers qualified meetings into whatever CRM you run. Clients own all the infrastructure we build, and our case studies show what a fully orchestrated system produces compared to a stack of half-connected tools.

Ready for an outbound system that fills Salesforce instead of just syncing with it?

We build and run the whole machine, data, infrastructure, copy, sending, and CRM integration, with a performance guarantee behind it.

Book your free pilot →