The dbt-Fivetran merger (October 2025) and Dataform’s parallel maturation have changed the analytics engineering tool landscape. What was a lopsided comparison — dbt for production, Dataform for simple BigQuery workloads — now has genuine tradeoffs on both sides.
The merger
The dbt-Fivetran merger announced in October 2025 created a combined entity approaching $600M ARR with over 10,000 customers. This is not a minor acquisition. It signals a strategic pivot from best-of-breed composition toward unified data platforms.
For years, the modern data stack thesis was modular: pick the best tool for each layer (ingestion, transformation, orchestration, BI) and compose them. Fivetran handled extraction. dbt handled transformation. They complemented each other as independent products. The merger collapses that boundary. The combined entity now controls the two most common tools in the analytics engineering workflow, and the commercial incentive is to make them work better together than with alternatives.
This matters for tool choice in two ways. First, teams using both Fivetran and dbt get tighter integration — the dbt_ad_reporting package is already the most popular dbt package for marketing data, and deeper coupling between connectors and transformation packages is inevitable. Second, teams using neither may face a market where the dominant vendor bundles ingestion and transformation, making independent alternatives less competitive over time.
Core/Cloud divergence
The merger accelerates a trend that was already uncomfortable: the growing divergence between dbt Core (open source) and dbt Cloud (commercial).
The Rust-based dbt Fusion engine delivers 30x faster parsing. Cloud customers get access. Core users do not. The semantic layer, Mesh for multi-project governance, and advanced CI features like Slim CI remain Cloud-only. Each release moves more capabilities behind the paywall.
This creates a strategic tension. dbt’s community of 100,000+ Slack members was built on Core’s accessibility. The ecosystem of 200+ packages was built by developers using Core. The career portability of dbt skills — appearing in nearly every analytics engineering job posting — was built on a tool anyone could download and learn for free.
As Cloud-exclusive features accumulate, the gap between “knowing dbt” and “having production dbt” widens. A team running Core misses Slim CI, the Fusion engine, the semantic layer, and advanced scheduling. These are not nice-to-haves — they are the features that differentiate dbt from competitors. The open-source version increasingly becomes a gateway to the commercial product rather than a standalone tool.
Some community members have discussed an OpenTofu-style fork if commercial pressures intensify. Whether that materializes depends on how aggressively dbt Labs pushes Cloud-only features. But the discussion itself signals that the relationship between the open-source project and the commercial entity is under strain.
Dataform maturation
While dbt consolidated through acquisition, Google’s Dataform matured significantly. The service that was once dismissed as a toy now includes VPC Service Controls, Dataplex integration for automatic data catalog synchronization, SSH authentication, and enterprise compliance certifications (SOC 1/2/3, HIPAA, ISO 27001).
Google positions Dataform as a free, production-ready transformation service within the BigQuery ecosystem. The key word is “free.” As dbt’s commercial features become more central to its value proposition, the cost differential between the two tools grows. A 10-person team pays $12,000 annually for dbt Cloud. Dataform costs nothing beyond BigQuery compute.
The testing gaps, tooling gaps, and ecosystem limitations remain real. But Dataform’s core engine — compiling SQLX to SQL and executing it against BigQuery — is now enterprise-grade. The question is no longer “is Dataform production-ready?” but “are the ecosystem gaps worth the licensing cost?”
Tool choice implications
For multi-warehouse teams, the merger reinforces dbt’s position. The combined Fivetran-dbt entity offers a unified ingestion-to-transformation pipeline across 20+ platforms. No other tool matches that breadth.
For BigQuery-exclusive teams, the calculus has shifted. Dataform is no longer a compromise — it is a legitimate tool for production workloads. The decision now hinges on whether dbt’s ecosystem premium (packages, CI/CD, IDE tooling, community) justifies its cost when the alternative is mature and free.
For dbt Core users, the merger raises strategic questions. If the most valuable features keep moving to Cloud, Core becomes less competitive against Dataform for BigQuery-only workloads. A team that chose Core to avoid licensing costs may find that Dataform offers a better free tier, with native GCP integration that Core cannot match.
For the broader market, the trend toward platform consolidation is clear. The dbt-Fivetran merger, Fivetran’s pricing changes, and Google’s investment in Dataform all point toward a future where transformation is bundled with adjacent capabilities rather than sold as a standalone layer. The best-of-breed era is not over, but the economic incentives favor consolidation.
As of 2026, both tools transform SQL effectively. The decision hinges on whether an organization’s trajectory aligns with BigQuery-exclusive simplicity or multi-cloud optionality, and whether the dbt ecosystem justifies the licensing cost.