Changes / ETL / ELT & ingestion / Fivetran
M&Alow impact
Fivetran 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.
Who’s affected
Teams that run SQLMesh or depend on SQLGlot (directly or through other tools) and want to know how Fivetran ownership might change roadmap, licensing or support. Fivetran customers may also see transformation features added to the platform.
Not affected: Teams that use neither SQLMesh nor SQLGlot, and Fivetran customers who only use connectors and don't plan to adopt its transformation features.
What it costs
The record gives no price, licensing or SKU change, so there is no direct bill impact today. The cost drivers to watch are any future bundling of transformation into Fivetran pricing and the effort to switch if the open source projects' direction changes.
When to act
No effective change is announced and the acquisition is already done, so a short review window is enough to check your dependency and roadmap exposure.
Blast radius: Limited to SQLMesh projects and tools that embed SQLGlot for SQL parsing or transpiling. Any change in licensing or roadmap would affect model definitions, CI checks and deployment workflows.
What should you do? decision tree
- you run SQLMesh in production or use SQLGlot as a library dependencyPin versions, record which projects depend on them, and watch the repos and Fivetran announcements for licensing or governance changes.
- you are a Fivetran customer considering its transformation featuresAsk your account rep how transformation will be packaged and priced, and get it in writing before you commit.
- you use SQLMesh and want to avoid vendor-ownership riskCompare it against dbt and keep your models portable so you can switch without a full rewrite.
- nothing in your stack touches these toolsNo action needed; note the acquisition and revisit at your next Fivetran renewal.
Options
- WaitDo nothing now; no price or license change is announced. Re-check the project repos and vendor notices over the next quarter.
- OptimizePin SQLMesh and SQLGlot versions and keep SQL models in standard, portable form to limit lock-in.
- NegotiateIf you buy Fivetran, ask how transformation will be priced and request price protection in the renewal contract.
- MigrateIf governance or licensing shifts against you, move transformation to another framework such as dbt.
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 - 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 - FivetranFivetran now bills history-mode repeated updates as paid MAR
Repeated updates tracked in history mode now count toward paid MAR; soft delete and live modes are alternatives.
Billing