New: The Agentic CDP

·Read the analysis

Connect · Data warehouse

Salesforce to Databricks

Directory data as of October 23, 2026

12 of the 44 CDPs in the CdpHub directory list both a connector that reads from Salesforce and one that sends data to Databricks, so they can sit between the two, and 18 go the other way, from Databricks to Salesforce.

12CDPs can carry Salesforce data into Databricks
18CDPs can carry Databricks data to Salesforce
30of 44 CDPs list Salesforce
26of 44 CDPs list Databricks

CDPs that can carry Salesforce data into Databricks

12 CDPs

Each of these CDPs lists a connector that reads from Salesforce and one that sends data to Databricks. A route is a possible path, not a tested one: what travels depends on each connector, so check the documentation links.

  • Reads from Salesforce

    Salesforce → Amperity

    Salesforce Sales Cloud (source). Pulls customer records from Salesforce Sales Cloud objects and reports into Amperity through its REST API, loading them in full each run.

    Sends to Databricks

    Amperity ⇄ Databricks

    Shares tables both ways between Amperity and Databricks through Amperity Bridge, using the OpenSharing protocol, an evolution of Delta Sharing, instead of file copies or ETL jobs.

  • Reads from Salesforce

    BlueConic ⇄ Salesforce

    Imports Salesforce records into BlueConic by object or SOQL query, including Service Cloud cases as timeline events, and exports segment profiles to Salesforce objects in batches.

    Sends to Databricks

    BlueConic ⇄ Databricks

    Imports and exports BlueConic profiles, groups and timeline events with a Databricks workspace through Delta Sharing up to six times a day, offered as a paid upgrade.

  • Reads from Salesforce

    Salesforce → CaliberMind

    Pull connector. Copies Salesforce CRM data from 17 standard objects, such as accounts, leads, opportunities and tasks, into CaliberMind's warehouse through a Fivetran-run pull connector using the Bulk API.

    Sends to Databricks

    CaliberMind → Databricks

    Lets Databricks read exported cm dataset tables from a Google Storage bucket with service account credentials from CaliberMind, for customers with Bring Your Own Data Warehouse.

  • Reads from Salesforce

    Salesforce → Insider One

    Pulls Salesforce contacts, leads, accounts or custom SOQL results into Insider One on a cron schedule through the REST API and OAuth, as incremental or full syncs.

    Sends to Databricks

    Insider One → Databricks

    Export. Shares Insider One events and user attributes with your Databricks workspace over Delta Sharing, refreshed on a sync period of up to 24 hours, for analysis through Unity Catalog.

  • Reads from Salesforce

    Salesforce → Klaviyo

    Syncs custom property data for each Salesforce lead into Klaviyo every hour, to target and personalize messages using CRM lead data.

    Sends to Databricks

    Klaviyo ⇄ Databricks

    Data warehouse import and export. Links Klaviyo and Databricks through a token for a Klaviyo-only account, importing profile and event data and exporting Klaviyo data back, with an Advanced KDP subscription.

  • Reads from Salesforce

    Lytics ⇄ Salesforce

    Imports Salesforce leads, opportunities and custom objects into Lytics and creates or updates Salesforce objects from Lytics audience members in real time.

    Sends to Databricks

    Lytics ⇄ Databricks

    Imports Databricks tables into Lytics, loads audiences, events, audience changes, system events and metrics into Delta tables, and can back Lytics Cloud Connect audiences.

  • Reads from Salesforce

    Salesforce → mParticle

    Sales and Service Cloud feed. Brings Salesforce Sales Cloud and Service Cloud records, such as leads and cases, into mParticle as a feed.

    Sends to Databricks

    mParticle → Databricks

    Loads mParticle data into Databricks Delta Lake, where scheduled jobs and SQL queries can work on it.

  • Reads from Salesforce

    Redpoint Global ⇄ Salesforce

    CRM channel. Keeps Salesforce leads, contacts or accounts in step with the Redpoint Interaction data warehouse, syncing either way through mapped fields and the Salesforce SOAP service.

    Redpoint Global ⇄ Salesforce

    Data Management. Reads Salesforce objects into Redpoint Data Management with SOQL queries and inserts, updates or deletes them with the Salesforce Output tool over the SOAP endpoint.

    Sends to Databricks

    Redpoint Global ⇄ Databricks

    Adds Databricks to Redpoint Interaction as an auxiliary database through the Simba Spark ODBC driver, pointing the connection at a Unity Catalog.

  • Reads from Salesforce

    Salesforce → Segment

    Source. Pulls Salesforce objects into Segment on a schedule for syncing to a warehouse.

    Sends to Databricks

    Segment → Databricks

    Loads Segment event data into Databricks on a schedule as a storage destination, ready for SQL analysis.

  • Reads from Salesforce

    Salesforce → Tealium

    Apex triggers. Sends Salesforce lead and contact updates to Tealium Collect from Apex triggers and a TealiumCollect class, linking them to Customer Data Hub records through a Tealium ID field.

    Salesforce → Tealium

    Bulk data source. Imports records from a Salesforce object into Tealium as events on an hourly, daily or weekly schedule through the Bulk API 2.0, in early access for select customers.

    Sends to Databricks

    Tealium → Databricks

    Writes event, visitor and log data to Databricks, staged through your own cloud storage on AWS, Azure or Google Cloud, singly or batched, from AudienceStream or EventStream.

  • Reads from Salesforce

    Salesforce → Treasure AI

    Import. Imports Salesforce objects into Treasure Data with optional SOQL queries over related objects, using the Bulk API for large volumes, to combine CRM data with other sources.

    Sends to Databricks

    Treasure AI → Databricks

    Export. Writes Treasure Data job results to a Databricks table in append, overwrite or replace mode, signing in with OAuth M2M or a deprecated personal access token.

    Treasure AI → Databricks

    Open Catalog Access. Federates Treasure Data's Glue catalog of Iceberg tables into Databricks Unity Catalog so Databricks can query them without copies, an Open Catalog Access option enabled on request.

  • Reads from Salesforce

    Salesforce → Zeotap

    Source. Syncs standard and custom Salesforce CRM objects, such as accounts, contacts and leads, into Zeotap daily, weekly or monthly through a connected app, keeping user IDs for matching.

    Sends to Databricks

    Zeotap → Databricks

    Destination. Activates Zeotap audiences into Databricks Delta tables by writing JSON files to your Google Cloud Storage bucket, which Databricks Autoloader loads into the table you name.

The other way: Databricks to Salesforce

18 CDPs

Each of these CDPs lists a connector that reads from Databricks and one that sends data to Salesforce.

  • Reads from Databricks

    Databricks → ActionIQ

    Layers ActionIQ's CDP on top of Databricks through native reverse ETL, mapping to customer data where it lives so business users can work with it without copying it into the CDP.

    Sends to Salesforce

    ActionIQ → Salesforce

    Salesforce Sales Cloud

  • Reads from Databricks

    Databricks → Adobe

    Brings Databricks data into Experience Platform for Real-Time CDP Ultimate customers.

    Sends to Salesforce

    Adobe → Salesforce

    Destination. Sends Real-Time CDP audiences and profile attributes to Salesforce CRM as either leads or contacts, keeping audience membership current through the composite API.

  • Reads from Databricks

    Amperity ⇄ Databricks

    Shares tables both ways between Amperity and Databricks through Amperity Bridge, using the OpenSharing protocol, an evolution of Delta Sharing, instead of file copies or ETL jobs.

    Sends to Salesforce

    Amperity → Salesforce

    Salesforce Sales Cloud (destination). Sends customer profiles from Amperity to Salesforce Sales Cloud through its SOAP API.

  • Reads from Databricks

    BlueConic ⇄ Databricks

    Imports and exports BlueConic profiles, groups and timeline events with a Databricks workspace through Delta Sharing up to six times a day, offered as a paid upgrade.

    Sends to Salesforce

    BlueConic ⇄ Salesforce

    Imports Salesforce records into BlueConic by object or SOQL query, including Service Cloud cases as timeline events, and exports segment profiles to Salesforce objects in batches.

  • Reads from Databricks

    Databricks → Blueshift

    Import. Imports customer data, events, catalogs and recommendation feeds from Databricks SQL warehouses into Blueshift, including incremental loads from Delta tables.

    Sends to Salesforce

    Blueshift → Salesforce

    Creates or updates records of any Salesforce object, such as leads, contacts and accounts, from Blueshift campaign journeys through a connected app and cloud app templates.

  • Reads from Databricks

    Databricks → CleverTap

    Imports data from a Databricks SQL warehouse into CleverTap, authenticating with a personal access token or with OAuth machine-to-machine credentials for a service principal.

    Sends to Salesforce

    CleverTap → Salesforce

    Export. Pushes CleverTap user profiles, event properties and campaign responses, such as NPS feedback, into Salesforce in real time through an OAuth 2.0 webhook calling a custom Apex REST endpoint.

  • Reads from Databricks

    Databricks → DinMo

    Connects a Databricks SQL warehouse or all-purpose cluster on AWS, Azure or GCP to DinMo with a personal access token, so DinMo can read your tables and write its own technical schemas.

    Sends to Salesforce

    DinMo → Salesforce

    Custom objects. Pushes DinMo model rows into a Salesforce custom object, inserting new records or updating fields on existing ones by ID, with each custom object set up as its own destination.

    DinMo → Salesforce

    Standard objects. Inserts, updates or upserts Salesforce accounts, cases, contacts, contracts or leads from DinMo models, one object per destination, using fields that already exist.

  • Reads from Databricks

    Databricks → Fivetran Activations

    Source. Uses Databricks, Unity Catalog included, as a Fivetran Activations source through a service principal or personal access token, on the Basic or Advanced Sync Engine.

    Sends to Salesforce

    Fivetran Activations → Salesforce

    Syncs any standard or custom Salesforce object from Fivetran Activations over OAuth through the bulk API, with create, upsert, mirror and delete options and multi-destination lead syncs.

  • Reads from Databricks

    Databricks → Hightouch

    Source. Connects Databricks to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.

    Sends to Salesforce

    Hightouch → Salesforce

    Syncs leads, accounts and product-usage data such as health scores from your warehouse into Salesforce CRM records.

    Hightouch → Salesforce

    Sandbox. Syncs warehouse data into a Salesforce sandbox org, to test syncs before production.

  • Reads from Databricks

    Lytics ⇄ Databricks

    Imports Databricks tables into Lytics, loads audiences, events, audience changes, system events and metrics into Delta tables, and can back Lytics Cloud Connect audiences.

    Sends to Salesforce

    Lytics ⇄ Salesforce

    Imports Salesforce leads, opportunities and custom objects into Lytics and creates or updates Salesforce objects from Lytics audience members in real time.

  • Reads from Databricks

    Databricks → mParticle

    Warehouse Sync. Ingests user and event tables, but not views, from Databricks into mParticle through Delta Sharing, as one-time or recurring syncs.

    Sends to Salesforce

    mParticle → Salesforce

    Sales and Service Cloud events. Sends mParticle event data to Salesforce Sales Cloud and Service Cloud through the Bulk API 2.0, for CRM and support teams.

  • Reads from Databricks

    Databricks → Odie

    Links Totango to a Databricks workspace with a personal access token, host name and HTTP path, so lakehouse data can feed standard Customer Data Hub jobs.

    Sends to Salesforce

    Odie → Salesforce

    Embedded app. Adds a Totango tab to Salesforce through a managed package, which needs an Enterprise or Unlimited license, so licensed Totango users can open Totango there.

    Odie → Salesforce

    Insights widget. Shows Totango health, engagement, usage and account tags in a Visualforce widget on Salesforce account layouts, fed by an outbound insights job and readable without a Totango license.

    Odie ⇄ Salesforce

    CRM sync. Imports Salesforce accounts, users, tasks, touchpoints and, with an add-on, opportunities into Totango on a schedule, and exports tasks, touchpoints, insights and users to Salesforce.

  • Reads from Databricks

    Redpoint Global ⇄ Databricks

    Adds Databricks to Redpoint Interaction as an auxiliary database through the Simba Spark ODBC driver, pointing the connection at a Unity Catalog.

    Sends to Salesforce

    Redpoint Global ⇄ Salesforce

    CRM channel. Keeps Salesforce leads, contacts or accounts in step with the Redpoint Interaction data warehouse, syncing either way through mapped fields and the Salesforce SOAP service.

    Redpoint Global ⇄ Salesforce

    Data Management. Reads Salesforce objects into Redpoint Data Management with SOQL queries and inserts, updates or deletes them with the Salesforce Output tool over the SOAP endpoint.

  • Reads from Databricks

    Databricks → RudderStack

    Source. Reads Databricks tables or SQL models with RudderStack Reverse ETL and activates the results in marketing and sales tools.

    Sends to Salesforce

    RudderStack → Salesforce

    Creates and updates Salesforce leads, contacts and other objects from RudderStack identify calls and warehouse records.

  • Reads from Databricks

    Databricks → Segment

    Data Graph. Links Databricks catalogs to Segment's Data Graph through a service principal that reads them and writes checkpoint tables to a catalog of its own, for Linked Audiences and Linked Events.

    Databricks → Segment

    Reverse ETL source. Connects a Databricks SQL warehouse to Segment Reverse ETL through a service principal, with OAuth machine-to-machine sign-in required for any new source.

    Sends to Salesforce

    Segment → Salesforce

    Actions. Sends Segment data to Salesforce for CRM through Actions such as Lead, Custom Object and Case.

  • Reads from Databricks

    Databricks → Tealium

    Cloud data source. Imports a Databricks table into Tealium attributes, connecting to a SQL warehouse on AWS, Azure or GCP with a service principal's OAuth secret rather than a personal access token.

    Databricks → Tealium

    Delta Sharing data source. Shares Databricks tables with Tealium through Databricks-to-Databricks Delta Sharing, in early access, so no credentials leave Databricks and CloudStream can read the data without copying it.

    Sends to Salesforce

    Tealium → Salesforce

    Connector, customer credentials. Inserts and updates leads, contacts and custom objects, converts leads and adds them to campaigns in Salesforce from AudienceStream or EventStream, with your own connected app.

    Tealium → Salesforce

    Connector, Tealium credentials. Inserts and updates leads, contacts and custom objects, converts leads and adds them to campaigns in Salesforce from AudienceStream or EventStream, with Tealium-managed OAuth.

    Tealium → Salesforce

    Standard Objects connector. Creates, updates or deletes Salesforce standard objects from AudienceStream or EventStream.

  • Reads from Databricks

    Databricks → Treasure AI

    AI Studio connection. Gives Treasure AI Studio agents query and charting access to a Databricks lakehouse in chat, through a Databricks OAuth app that each user authorizes for their own connection.

    Databricks → Treasure AI

    Composable Audience Studio. Runs Composable Audience Studio parent segments on Databricks Unity Catalog tables with federated queries and service principal OAuth, so audiences are built without copying data.

    Databricks → Treasure AI

    Import. Imports Databricks tables or custom SELECT query results into Treasure Data, with filter conditions and incremental columns, over OAuth M2M or a personal access token.

    Databricks → Treasure AI

    Live Connect zero-copy. Reads Databricks tables shared over Delta Sharing into Treasure Data, by default in memory, for ID unification and activations, a Live Connect zero-copy option enabled on request.

    Sends to Salesforce

    Treasure AI → Salesforce

    Export. Writes Treasure Data job results to an existing Salesforce object in append, truncate, update or upsert mode, signing in with client credentials or OAuth.

  • Reads from Databricks

    Databricks → Zeotap

    Source. Pulls records from a Databricks table into Zeotap on a schedule, over JDBC with OAuth for smaller tables or a job-based connection advised above one million records.

    Sends to Salesforce

    Zeotap → Salesforce

    Batch. Sends Zeotap audience data into Salesforce objects such as contacts, accounts, leads, cases, opportunities, tasks, campaigns or custom objects, after a sign-in on your Salesforce domain.

    Zeotap → Salesforce

    Real-time. Upserts Salesforce contact or custom object records from Zeotap Journeys in real time, through an API user and an external ID field on the target object.

Get an email when these routes change

CdpHub Pro will alert you when a CDP adds, renames or retires a connector between Salesforce and Databricks. Join the waitlist for early access.

Join the Pro waitlist →

Salesforce and the other warehouses

About these numbers

CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. A route counts a CDP that lists a connector reading from one end and another sending data to the other: a possible path, not a tested one. What travels, how often and in which format depends on each connector and its plan, so follow the documentation links. Counts are updated as catalogs change; this page reflects the directory as of October 23, 2026. CdpHub is independent and not affiliated with Salesforce, Databricks or any platform listed.

Getting Salesforce data into Databricks?

Vendor-neutral help choosing the route that fits your stack, and getting the connection running.

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy