MongoDB to BigQuery
real-time replication
TwinCommit replicates MongoDB to Google BigQuery in real time by reading the MongoDB transaction log and applying every committed change exactly once and in commit order. Use it to feed BigQuery with live MongoDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MongoDB
log reader
commit-ordered · exactly-once
BigQuery
native writer
How capture works on MongoDB
TwinCommit opens change streams on replica sets and sharded clusters, persists resume tokens with the checkpoint, and keeps multi-document transactions intact.
Prerequisites
- ✓Replica set or sharded cluster (change streams need an oplog)
- ✓changeStream and find privileges on watched databases
- ✓Pre- and post-images enabled for full before/after values (optional)
How apply works on BigQuery
Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Requirements
- ✓A service account with BigQuery Data Editor and Job User
- ✓A dataset for staging tables
- ✓Primary keys declared on target tables (recommended)
Setup
Set up MongoDB → BigQuery in four steps
- 1
Prepare MongoDB
Run twincommit check. It verifies replica set or sharded cluster (change streams need an oplog) and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at BigQuery
Add a target block for BigQuery. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mongodb
uri: ${MONGODB_URI}
target:
type: bigquery
project: acme-analytics
dataset: replica
credentials_file: /secrets/bq.json
tables:
- source: sales.orders
- source: sales.customersMongoDB to BigQuery replication FAQ
How does TwinCommit replicate MongoDB to BigQuery?
+
TwinCommit reads changes from the MongoDB transaction log, buffers them per transaction, and applies each committed transaction to BigQuery in commit order. Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Does MongoDB to BigQuery replication need triggers or capture tables?
+
No. TwinCommit reads the MongoDB log directly and creates no objects in the source database.
Is MongoDB to BigQuery replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same BigQuery transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MongoDB versions are supported?
+
MongoDB 5.0–8.x · MongoDB Atlas · replica sets and sharded clusters.
Stream MongoDB to BigQuery today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.