Skip to content
CRM

Drift to Salesforce integration — real-time, two-way sync

Keep Drift and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Drift and Salesforce

Run Drift and Salesforce side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Stacksync syncs Contacts, Conversations, Messages, Accounts in Drift with Leads, Opportunities, Cases, Campaigns in Salesforce in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.

Common use cases

  • 01 Sync meetings booked in Drift to CRM activities so pipeline attribution stays accurate.
  • 02 Archive historical Drift conversation and contact data into a warehouse ahead of a platform migration.
  • 03 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 04 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

Common sync patterns

Migration with a parallel run

When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.

Divisional or regional split

Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.

Where both track pipeline: deal visibility across systems

Deal stage and value on shared accounts stay visible from either CRM.

What you can sync between Drift and Salesforce

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Drift objects Salesforce objects How this pairing syncs
Contacts Visitor and lead records created or matched from chat identities; the main CRM-sync object. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Accounts Company records used for account-based routing and targeting. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Meetings Meetings booked through Drift, synced to CRM as sales activities. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Meetings is specific to Drift and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Conversations Chat threads with status and participants; the center of Drift's data model. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Conversations is specific to Drift and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Messages Individual messages within a conversation, used for transcript and intent analysis. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Messages is specific to Drift and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Users Agents and sales reps who own conversations and meetings. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Users is specific to Drift and Custom Objects to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Drift and Salesforce

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Drift Salesforce Sub-second propagation

DetectionDrift notifies Stacksync of record changes through webhook events. Webhook events for new conversations, messages, and contact changes.

DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Drift Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

DeliveryEach detected change is written to Drift through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Drift: Subject to the platform's API rate limits.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Drift ⇄ Salesforce

Connect Drift and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Drift–Salesforce connection.

Real-time

Two-way sync

Changes in Drift or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Drift or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Drift or Salesforce record.

Observability

Monitoring

Track your Drift ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Drift and Salesforce.

How the Drift and Salesforce connectors work

Drift

Integration surface
REST API
Authentication
OAuth 2.0 via apps registered on the Drift developer platform
Change detection
Webhook events for new conversations, messages, and contact changes; polling for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Drift to Salesforce — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Drift and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Drift connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Drift and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Drift ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Drift Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Drift and Salesforce integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 312 integrations available for Drift and Salesforce.

Popular · 5 of 312
All Drift integrations All Salesforce integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own