How do I move my dbt Cloud workflow to Bruin on BigQuery?
Point Bruin at your BigQuery connection and bring your dbt Cloud logic across as Bruin assets. Ingestion, transformation, quality, and lineage then run against BigQuery from one CLI.
Command
bruin runDefined in
SQL + Python + YAML
Works with
dbt Cloud + BigQuery + Bruin
What you get
How it works in code
$ bruin run ./pipeline # against bigqueryRun bruin run and your whole workflow runs against BigQuery from one tool.
Related use cases
Migrate from dbt Cloud to Bruin on Snowflake
How do I move my dbt Cloud workflow to Bruin on Snowflake?
Migrate from dbt CloudMigrate from dbt Cloud to Bruin on Postgres
How do I move my dbt Cloud workflow to Bruin on Postgres?
Migrate from dbt CloudMigrate from dbt Cloud to Bruin on Databricks
How do I move my dbt Cloud workflow to Bruin on Databricks?
About Bruin
What is Bruin?
Bruin is an open-source, AI-powered data platform. One project covers the whole path from source to answer: data ingestion (with ingestr), SQL and Python transformations, quality checks, column-level lineage, a data catalog and scheduling. On top of that data, an AI data analyst answers questions in Slack, Microsoft Teams, Google Chat, WhatsApp, Discord, Telegram, email or the browser, and builds dashboards from a prompt.
Pipelines are plain SQL, Python and YAML files in your own Git repository, and the work runs inside your own warehouse: Snowflake, BigQuery, Databricks, Redshift, Postgres, ClickHouse, DuckDB and others. The Bruin CLI is open source under Apache 2.0 and runs on a laptop, in CI or on-prem. Bruin Cloud is optional and adds scheduling, the AI data analyst, governance, SSO and audit logs.
For migrations that means moving one pipeline at a time, with the old and new versions running side by side until the numbers match.
- Replaces
- Separate tools for ingestion, transformation, orchestration, data quality, cataloguing and BI
- Open source
- Bruin CLI under Apache 2.0; ingestr source-available under the Functional Source License
- Your data
- Stays in your warehouse; pipelines stay in your Git repository
- Security
- ISO/IEC 27001:2022 certified and SOC 2 Type 2 attested
- Used by
- Data teams at Lessmore, StarBerry, NativeMinds, SCG, M8 Games and Fabrikatör
Why Bruin for migrations
Incremental, not a rewrite
Move one pipeline, compare its output, then move the next. Nothing has to switch over in one go.
Start from what you have
bruin import database turns existing warehouse tables into assets, and dbt models port with their Jinja intact.
Run inside your current scheduler
Call Bruin from an existing Airflow DAG while you move, then retire the DAG later.
Prove the numbers match
bruin data-diff compares the old and new tables before you switch.
How it works
01
Import
Map existing tables with bruin import database and start a project.
02
Port one pipeline
Move one ingestion and its models, add checks, and run both versions side by side.
03
Compare and switch
Diff the outputs, switch consumers to the Bruin tables, and turn off the old job.
Migrate incrementally, not all at once
Bruin CLI and ingestr are on GitHub.
A demo walks through your own data.