Two-way sync
Changes in BigQuery or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery 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.
Revenue-operations and data teams replicate Salesforce into BigQuery to analyze the funnel at warehouse scale. Opportunities, Accounts, and Campaigns sync into BigQuery Tables organized by Dataset, joining CRM data with product and finance sources without hitting Salesforce API limits from every dashboard.
Stacksync does both with one connection. Opportunities, Cases, Campaigns, Tasks and Events from Salesforce land in BigQuery as live tables, updated within seconds, and columns computed in BigQuery write back to fields in Salesforce. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Leads and Opportunities sync into partitioned BigQuery Tables for conversion and pipeline reporting.
Salesforce Accounts and Contacts land in a BigQuery Dataset joined to usage and billing data.
Campaigns replicate to clustered BigQuery Tables to tie marketing spend to Opportunity outcomes.
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.
| BigQuery objects | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Projects Connection scope: the service account grants access per project. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Projects is specific to BigQuery and Tasks and Events to Salesforce — each maps to any object or custom field on the other side. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Tables is specific to BigQuery and Products and Price Books to Salesforce — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Partitioned tables is specific to BigQuery and Custom Objects to Salesforce — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Clustered tables is specific to BigQuery and Accounts to Salesforce — each maps to any object or custom field on the other side. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Datasets is specific to BigQuery and Contacts to Salesforce — each maps to any object or custom field on the other side. |
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.
DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
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 applied to BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Salesforce connection.
Changes in BigQuery or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or Salesforce record.
Track your BigQuery ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Salesforce.
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.
Authenticate BigQuery 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.
Pick the BigQuery 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BigQuery and Salesforce: authenticate both systems, choose the objects to sync (such as BigQuery's Projects and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means BigQuery and Salesforce records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed BigQuery and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom BigQuery–Salesforce integration in-house.
Yes — Stacksync ships production-grade connectors for both BigQuery and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on BigQuery: Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Salesforce side: Opportunities, Cases, Campaigns, Tasks and Events, plus custom fields where Salesforce exposes them. On the BigQuery side: Partitioned tables, Clustered tables, Datasets, Projects. Stacksync auto-detects both schemas and converts types between the two systems.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 573 integrations available for BigQuery and Salesforce.