Two-way sync
Changes in BigQuery or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and Snowflake in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Data teams sync BigQuery and Snowflake when the two warehouses coexist — after an acquisition, across departments, or during a migration. Tables and Schemas replicate between the platforms so each side queries current data without duplicate pipeline builds.
Stacksync syncs tables between BigQuery and Snowflake continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
BigQuery Datasets and Tables mirror into Snowflake Databases and Schemas with schema changes propagated.
Snowflake Streams feed updates into partitioned BigQuery Tables for near-real-time parity.
Materialized Views built in Snowflake replicate as BigQuery Tables for teams standardized on GCP.
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 | Snowflake objects | How this pairing syncs | |
|---|---|---|---|
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Tables The main landing and activation target for synced records. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Materialized Views Precomputed results synced outward for low-latency reads. | Datasets is specific to BigQuery and Materialized Views to Snowflake — each maps to any object or custom field on the other side. | |
| Projects Connection scope: the service account grants access per project. | Streams Row-level change records on a table, consumed to process deltas instead of full scans. | Projects is specific to BigQuery and Streams to Snowflake — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Stages File staging areas used for bulk loads into synced tables. | Partitioned tables is specific to BigQuery and Stages to Snowflake — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | Tasks Scheduled SQL used to transform synced data after it lands. | Clustered tables is specific to BigQuery and Tasks to Snowflake — 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 applied to Snowflake as a row-level write, with types converted between the two schemas.
DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.
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–Snowflake connection.
Changes in BigQuery or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Snowflake 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 Snowflake record.
Track your BigQuery ⇄ Snowflake sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Snowflake.
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 Snowflake 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 Snowflake 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 Snowflake: authenticate both systems, choose the objects to sync (such as BigQuery's Tables and Datasets), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for BigQuery and Snowflake: Cross-warehouse replication; Change capture; View sharing. BigQuery Datasets and Tables mirror into Snowflake Databases and Schemas with schema changes propagated.
BigQuery: GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs. Authentication: Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver. Snowflake: SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API. Authentication: Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles. Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: The Storage Write API supports high-throughput streaming ingestion, which suits continuous sync loads better than legacy streaming inserts. Snowflake: External tables are not supported. Stacksync's field mapping accounts for these differences between BigQuery and Snowflake without custom code.
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 Snowflake records are not retained after a sync operation.
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 583 integrations available for BigQuery and Snowflake.