The dbt Labs and Fivetran merger is the largest deal in data infrastructure this decade – an all-stock combination of two of the most widely used tools in the modern data stack. Here’s what actually happened, why it happened, and what it means for data teams trying to plan budgets, contracts, and architectures over the next 12 months.

On October 13, 2025, Fivetran and dbt Labs announced they had signed a definitive agreement to merge in an all-stock deal. George Fraser, Fivetran’s CEO, will lead the combined company. Tristan Handy, dbt Labs’ CEO, will become co-founder and President. Combined ARR is approaching $600 million. The two companies share more than 1,500 joint customers, and Fivetran estimates that 80-90% of its existing customers already use dbt in some form.

The deal isn’t closed yet – it’s still subject to regulatory approval, and both companies will keep operating independently until then. But the strategic direction is set. And for any data team that runs Fivetran, dbt, or both, it’s worth understanding exactly what’s changing and what isn’t, before renewal conversations start.

What actually happened: the deal in plain numbers

This is an all-stock merger, not a cash acquisition. dbt Labs shareholders take a minority stake in the combined entity. Both boards approved the deal. Both shareholder bases approved it. Andreessen Horowitz is an investor in both, which made the cap table math easier than most M&A.

For Fivetran, this is the third deal in five months. They acquired Census in May 2025 to add reverse ETL and rename it as Fivetran Activations. They acquired Tobiko Data, the company behind SQLMesh, in September. Now dbt Labs in October. The pattern is a deliberate roll-up of the modern data stack into one platform – ELT, transformation, and activation under one vendor.

Why this deal happened now

The official narrative is “open data infrastructure” – a unified platform for data movement, transformation, metadata, and activation that works across any compute engine, catalog, or BI tool. That’s the marketing line. The strategic reality is more interesting.

Both companies were hitting growth ceilings as standalone point solutions. Fivetran’s core ingestion business is under pressure from cloud-native alternatives like Airbyte and from warehouses building their own ingestion – Snowflake has OpenFlow, BigQuery has its native data transfer service, Databricks has Lakeflow. dbt Labs faced a similar squeeze: warehouses are increasingly bundling transformation natively, and competitors like SQLMesh and Dataform have been chipping at the edges.

Meanwhile, Microsoft Fabric, Databricks, and Snowflake have been winning big deals by selling integrated platforms instead of best-of-breed point solutions. The “modern data stack” model that built both Fivetran and dbt – assemble specialized tools, mix and match for flexibility – has become a tougher sell as enterprises consolidate vendors and look for predictable bills.

George Fraser told Reuters the combined company would be near cash-flow break-even, and that the increased scale strengthens its eventual path to a public listing. Translation: this is a survival and IPO-readiness move as much as it is a product strategy. For background on how the broader stack is shifting, our breakdown of the modern data stack is a useful starting point.

What the data community is actually worried about

The reaction on r/dataengineering, LinkedIn, and Hacker News has been notably skeptical. Both companies have promised the merger will be “non-disruptive” and that dbt Core will remain open under its current license. Even so, three concerns keep coming up across analyst write-ups, practitioner blog posts, and Coalesce 2025 hallway conversations.

Industry analysts have drawn comparisons to Salesforce buying Tableau and Google buying Looker – both deals where customers saw stagnant innovation and rising prices in the years that followed. The pattern isn’t guaranteed, but it’s enough of a precedent that data leaders are doing the math now rather than waiting for the next contract cycle.

There’s also a quieter concern about Fivetran already owning SQLMesh through its Tobiko acquisition. SQLMesh is, in some respects, a dbt competitor. Owning both means the combined company can pick which one gets the long-term roadmap investment – and the answer is unlikely to be “both equally.”

Five practical implications for data teams

Strip out the analyst takes and the Reddit drama, and there are five things that genuinely matter for teams running Fivetran, dbt, or both today.

1. Renewal conversations will get harder

If your renewal is in the next 12 months, expect bundled pricing pitches. The combined sales motion will be “you already use both, here’s a discounted package.” That sounds good until you realize the bundle removes your leverage to negotiate either component independently. Reviewing your feature list and architecture against what you actually use is worth doing before any renewal call – and if you don’t already have data lineage documented end-to-end, this is the moment to fix that.

2. dbt Core stays open, but watch the gap

Both companies have publicly committed to keeping dbt Core under its current Apache 2.0 license. That commitment is real. What it doesn’t guarantee is roadmap investment. The most likely outcome is that Core continues to receive bug fixes and security patches while substantive new features land in dbt Cloud and dbt Fusion. Teams running on Core should plan for a widening capability gap and decide whether that’s acceptable for their use case.

3. Multi-vendor architectures just got more valuable

The teams least exposed to this merger are the ones who built their architecture on open standards – SQL, Iceberg, REST APIs, version-controlled transformation logic – rather than tool-specific implementations. If your dbt models are clean SQL in Git, you can run them on a different transformation engine. If your ingestion is documented with clear schemas, you can swap connectors. Data integration portability is suddenly a more attractive design principle than it was a year ago, and treating data transformations as portable assets rather than vendor-locked artifacts is the most practical way to get there.

4. Orchestration is still missing from the bundle

Even after the merger, the combined Fivetran-dbt platform doesn’t fully solve workflow orchestration. dbt Cloud has basic scheduling. Fivetran has sync schedules. Neither handles complex multi-system orchestration well. Teams running Airflow, Dagster, or Prefect alongside their stack will still need to do that integration work themselves. For background on how these layers fit together, our explainer on ETL vs ELT covers where the seams typically end up. This orchestration gap is either a gap waiting for the next acquisition or a deliberate space left for partners.

5. The “modern data stack” model is being replaced by something else

This merger is less an isolated event and more a symptom of where the industry is heading. Microsoft Fabric, Databricks Lakeflow, Snowflake’s native ingestion, and now Fivetran-dbt are all converging on the same idea: enterprises want fewer vendors, unified billing, and integrated experiences. The old “best-of-breed for every layer” approach is being replaced by something closer to modern data stack consolidation – either platform-native consolidation (Fabric, Databricks) or merged-vendor consolidation (Fivetran-dbt). The flexibility you used to get from mixing specialized tools is becoming harder to maintain without a deliberate strategy for it.

What to actually do in the next 90 days

The merger isn’t closed yet. The companies are still operating separately. Nothing changes for any customer overnight. But the smart play is to use this window to build optionality before renewal conversations happen with new pricing structures and bundled offers on the table.

None of this is panic. It’s the kind of due diligence any data leader should do before a major vendor shift. The teams who act in this window will protect themselves. The teams who wait will accept whatever terms the combined company puts on the table.

Where Peliqan fits if you want a single platform without the merger drama

The strongest argument the new Fivetran-dbt company is making is consolidation – one vendor, one bill, one platform for ingestion plus transformation plus activation. That’s a real benefit, and it’s the right direction for many teams. The trade-off is that you’re consolidating with two companies that are still figuring out how to integrate their products, their pricing, and their go-to-market motions while a regulatory approval process plays out.

Peliqan was built from day one as a single integrated platform – ELT, transformations, reverse ETL, AI agents, and a built-in data warehouse, all under one roof. There’s no merger to wait for. There’s no integration risk between two product teams. And the pricing model is fixed and transparent: plans start at around $199/month, not consumption-based with surprise spikes. For teams who like the consolidation thesis but don’t want to bet their architecture on a deal that hasn’t closed yet, it’s worth understanding what’s already shipping.

If you’re already evaluating alternatives in light of the merger, our deeper write-ups on Fivetran alternatives and dbt alternatives and competitors walk through the broader landscape, not just Peliqan. The point isn’t that everyone should switch – it’s that everyone should at least know what their options look like before they’re back at the negotiating table.

Comparing the post-merger world: what changes, what doesn’t

The bigger picture: this is consolidation, not innovation

It’s worth saying clearly: the dbt Labs and Fivetran merger isn’t happening because these are bad products. They’re not. dbt is one of the most beloved tools in modern data engineering. Fivetran genuinely solves a hard problem reliably. The merger is happening because best-of-breed point solutions are losing the strategic battle to integrated platforms. It’s a survival move, dressed up as a vision statement.

The market is consolidating across the board. Microsoft Fabric is consolidating. Databricks is consolidating with Lakeflow. Snowflake is building native ingestion and transformation. Boomi acquired Rivery in late 2024. Now Fivetran has acquired Census, Tobiko, and dbt Labs in five months. Every one of these moves is the same underlying bet: enterprises want fewer vendors, simpler bills, and less integration work. That bet is largely correct.

The risk for data teams is that consolidation done by acquisition is messier than consolidation done by design. When you buy an integrated platform that was built integrated, you get one product, one team, and one roadmap. When you buy a “platform” that was assembled from acquisitions, you get multiple products in a transitional state, multiple teams trying to align, and a roadmap that depends on integration work that hasn’t been done yet. The first 18 months after a deal like this are usually the hardest. Customers feel that.

Final take

The dbt Labs and Fivetran merger is a meaningful event. It will reshape the modern data stack conversation for the next several years. It’s not a disaster, and the teams running both products today don’t need to panic. But it’s also not nothing – and pretending it’s just two complementary partners getting closer would be ignoring the obvious shift in pricing power, vendor concentration, and product strategy that comes with a $600M ARR combination.

For most teams, the right response is the boring one: document your dependencies, audit your costs, build an option, and time your renewal carefully. For teams who were already considering a more consolidated approach, the merger is a reasonable forcing function to look at platforms that were built integrated from day one rather than assembled through deals. If AI workloads are part of that conversation, our walkthrough on how to build an MCP server shows what an integrated approach looks like in practice. Either way, the next 12 months are when the decisions that matter get made – not after the merger closes, but before.