Skip to content
Data warehouse ⇄ CRM

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

Keep Dremio 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 Dremio and Salesforce

Sync Salesforce into Dremio continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.

The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.

Stacksync does both with one connection. Leads, Opportunities, Cases, Campaigns from Salesforce land in Dremio as live tables, updated within seconds, and columns computed in Dremio write back to fields in Salesforce. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
  • Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.

Cleanup that sticks

Deduplication and normalization done in Dremio can be written back, so warehouse-side cleanup actually fixes the CRM.

CRM analytics on live data

Accounts, contacts, and activity from Salesforce are queryable in Dremio moments after they change, so dashboards stop lagging the reality they describe.

Scores and segments back on the record

Lead scores, churn risk, or usage segments computed in Dremio appear as fields in Salesforce, where the people working accounts actually see them.

What you can sync between Dremio 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.

Dremio objects Salesforce objects
Spaces and folders Namespaces that organize virtual datasets and govern access. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated.
Reflections Materialized accelerations that make repeated extraction queries cheaper. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP.
Jobs Query execution records useful for monitoring sync workloads. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close.
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. Cases Support records; synced with help desk tools or internal databases for escalation workflows.
What ships with Dremio ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dremio 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 Dremio or Salesforce record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Dremio and Salesforce connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than 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 Dremio 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 Dremio 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
    Dremio connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dremio 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 · Dremio ⇄ 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
    Dremio Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dremio and Salesforce integration FAQ

SECURITY

Security teams love 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.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

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

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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