Changes / ETL / ELT & ingestion / Fivetran
M&Alow impact
Fivetran and dbt Labs complete their merger
Fivetran and dbt Labs completed their all-stock merger, originally announced October 13, 2025, now operating as Fivetran + dbt Labs.
Who’s affected
Teams that buy both Fivetran and dbt (Core, Cloud or Fusion) and have contracts renewing soon, since bundling, packaging and vendor-roadmap changes could show up at renewal.
Not affected: Teams on dbt Core only, or on Fivetran with no dbt dependency, can ignore this. The record shows no price, plan or SKU change.
What it costs
No price or plan change is recorded in the announcement. The drivers to watch are possible future bundling or repackaging of the two products and less leverage when you negotiate with two vendors that are now one.
When to act
The merger closed June 1, 2026 and nothing forces action yet, so a 30-day lead time is enough to review contracts before your next renewal conversation.
Blast radius: No immediate breakage. Possible downstream effects at renewal include contract consolidation, changed support channels, and shifts in dbt and Fivetran roadmap and integrations.
What should you do? decision tree
- you have both a Fivetran and a dbt Labs contract and either renews within the next 6-12 monthsAsk your account rep now whether the contracts will be combined, and get current terms and price protection confirmed in writing.
- you use dbt Cloud or Fusion and Fivetran togetherMap where each tool is a hard dependency (orchestration, transformations, semantic layer) so you know your switching cost before bundling offers arrive.
- you run dbt Core onlyTake no action; keep watching the license and roadmap notes for any change to open-source dbt.
- you are uneasy about single-vendor concentration for ingestion and transformationScope a small pilot of an alternative ingestion or transformation tool to keep negotiating leverage.
- none of the above appliesWait and re-check at your next renewal; no change is needed today.
Options
- WaitDo nothing until the vendor announces packaging or pricing changes; the merger itself changed no list price in the record.
- NegotiateBefore renewal, request price caps and a term that locks current terms for both products, and ask whether a combined agreement would help you.
- OptimizeDocument your dbt and Fivetran usage and dependencies now so a bundle offer can be evaluated against your real usage.
- Re-architectKeep the ingestion and transformation layers loosely coupled (standard SQL, open connectors) so either piece can be swapped later.
Alternatives editorial picks, not sponsored
The facts straight from the source
Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.
Related changes
- FivetranFivetran moves MAR volume tiering from account to connection level
MAR volume tiering is applied per connection instead of per account from March 1, 2025, raising costs for accounts with many equal-sized connections.
Price ↑ - FivetranFivetran signs agreement to acquire Census (reverse ETL)
Fivetran announced a signed agreement to acquire Census, funded by cash and equity; terms were not disclosed and closing is pending.
M&A - FivetranFivetran acquires Tobiko Data (SQLMesh, SQLGlot)
Fivetran announced it has acquired Tobiko Data, the open source company behind SQLMesh and SQLGlot, adding transformation capabilities to its platform.
M&A - InformaticaSalesforce completes its acquisition of Informatica
Salesforce announced it has completed its acquisition of Informatica, folding its data catalog, integration, governance, quality, and MDM products into the Salesforce platform.
M&A - FivetranFivetran adds a $5 minimum per connection (1 to 1M MAR)
A $5 minimum base charge applies to standard connections generating between 1 and 1 million MAR per month, starting January 1, 2026 for PAYG.
Price ↑ - FivetranFivetran deletes now count toward paid MAR
Inserts, updates and deletes all count toward paid MAR; previously deletes did not contribute to paid MAR.
Billing