Most Snowflake-to-Databricks migrations get sold on cost and delivered on something else. The credit line item is what gets the project funded, but the teams that finish happy are usually the ones that moved for a different reason: they wanted ML, streaming and GenAI workloads living next to the analytics data instead of shuttling between two platforms. If your only justification is the bill, read the breakeven section below before you commit — the honest number is longer than the deck says.
We're a if you haven't committed yet. This post assumes you have.
What actually changes underneath
The two platforms look similar from a SQL console and are structurally different behind it. The mapping worth internalising before planning anything:
| Layer | Snowflake | Databricks |
|---|---|---|
| Storage | Proprietary micro-partitions inside Snowflake | Delta Lake files in your own S3/ADLS/GCS bucket |
| Compute | Virtual warehouses, T-shirt sized | Job clusters, all-purpose clusters, SQL Warehouses, Photon |
| Governance | Role hierarchy, row access policies, masking policies | Unity Catalog across tables, models, notebooks, dashboards |
| Sharing | Secure Data Sharing | Delta Sharing (open protocol) |
| Billing unit | Credits | DBUs, priced differently per compute type |
The storage row is the one with the most downstream consequences. On Snowflake, storage and compute are separate line items on the same bill; on Databricks, storage is your cloud provider's problem and your cloud provider's invoice. That's a genuine benefit — the data stays readable by other engines — but it also means your "Databricks cost" and your "data platform cost" stop being the same number, and finance needs to know that before the first invoice arrives.
Pick a strategy before you pick a tool
Three patterns, and the choice determines everything after it:
Lift-and-shift. Replicate schemas one-to-one, translate the SQL, cut over. Fastest, and it faithfully preserves every design compromise you made in Snowflake — including the ones you made because Snowflake billed you that way. Defensible when a contract is expiring and the calendar is the constraint.
Re-platform. Translate the schema into a and , and our if you'd rather know the number before the project starts than halfway through it.
Originally published on the Zephico blog.
SOCIAL SHARE CARD GENERATOR