Compare
SQL Server to Databricks: what are the options?
Databricks offers two free or bundled routes: Lakebridge, whose Morpheus transpiler converts T-SQL and whose BladeBridge converter handles SSIS experimentally, and Genie Migrate, an agentic converter in the workspace. Partner tools and Novuz cover what those leave, chiefly SSIS packages, SQL Agent schedules and evidence per object. Run Lakebridge on the T-SQL first. Here are the facts, from each vendor’s published material.
Side by side
How do the SQL Server to Databricks routes differ?
| Lakebridge | Genie Migrate | Partner tools (Next Pathway SHIFT, LeapLogic) | Novuz | |
|---|---|---|---|---|
| Approach | Transpilers: Morpheus for T-SQL, BladeBridge for SSIS; Switch, which uses a language model, is experimental | An agent in the Databricks workspace converts files, then revises and rechecks them | Vendor translation platforms with planning and testing products | Fixed, versioned rules convert about 95% of objects; a resolver handles the rest, with engineer approval |
| T-SQL procedures and views | Morpheus, recommended by Databricks for SQL Server | T-SQL to Databricks SQL, or notebooks (Beta) | Both list SQL Server or its SSIS estate as a source for Databricks | Converted by rule to Databricks SQL or notebooks |
| SSIS packages | BladeBridge to notebooks, listed as experimental; Script Task and Script Component code must be rewritten by hand | Not listed | SHIFT lists SSIS as a source; LeapLogic cites a SQL Server and SSIS case study | Control flow, data flows and expressions converted by rule; Script Tasks reviewed |
| SQL Agent schedules | Not listed | Not listed | See vendor documentation | Rebuilt as Databricks Workflows with the original dependencies |
| Equivalence evidence | Reconcile compares named source and target tables at schema, row and column level | Checks syntax and semantic intent; Databricks recommends comparing results on test data | Next Pathway Tester; LeapLogic schema, record and aggregate validation | A reconciliation report for every object; typically above 95% on first pass |
| Where it runs | Your Databricks environment | Your Databricks workspace; up to 500 files per run | See vendor documentation | Inside your environment, as a Docker container or VM |
| Price | Free; Switch incurs model token costs | Not stated | Not published | Fixed price per scope after a $3,000 assessment |
Re-verified monthly against each vendor’s published material. Last checked: 2026-11-03. Sources: the Lakebridge overview, tool chooser and SSIS guide, the Databricks Genie Migrate documentation, Next Pathway’s SHIFT Translator page and Impetus’s LeapLogic Databricks page. An object counts as automated only if it needs no manual edit, and a one-line fix counts as manual.
When to choose
Which SQL Server to Databricks route should I choose?
- Run Lakebridge first. It is free, and Morpheus is Databricks’ recommended transpiler for T-SQL.
- Try Genie Migrate for batches of T-SQL files when your workspace has it enabled, and test the results on real data.
- Choose a partner tool if the program also covers sources such as Informatica, DataStage or Netezza.
- Choose Novuz if SSIS packages and SQL Agent schedules carry the business rules, or if you need a fixed price and a reconciliation report for every object.
- Bottom line: convert the T-SQL with the free tools, then decide on the packages and schedules by what you must prove.
Next question
Where to read next
Which tools convert SSIS packages fully? None without exceptions; the SSIS options page sets out each route.
Four pillars
What Novuz gives you that the other routes do not
Test any route against these four, ours included. Each one comes with a proof you can check yourself.
Deterministic
The same code in gives the same code out. About 95% of objects convert by fixed, versioned rules with no model calls. The rest go to the resolver, and an engineer approves every proposal.
Proof: Convert twice and diff the output. The diff is empty.
Proven
Every object ships with a reconciliation report. Schema, row counts and column-level values are compared against the original on the same inputs. Pass, fail or review, per object.
Proof: Reconciliation above 95% on first pass, typically.
Agentically primed
Agents can run Novuz through its APIs, and your agents can run the pipelines Novuz delivers through MCP. The conversion in between stays deterministic.
Proof: Conversion by rules, agents around it. No model in the conversion path.
Inside your walls
Runs as a container or VM in your cloud or your data center. Code, data, lineage and the resolver’s knowledge base stay with you. Works air-gapped.
Proof: No outbound connection required. Fixed price set before work starts.
Bottom line. Translation is the easy part. A comparison is worth making when the other route can show you the same output twice, a report for every object, agents around the conversion and code that never leaves your walls. If it cannot, that is what Novuz is for.
FAQ
Frequently asked questions
What tools migrate SQL Server to Databricks?
Databricks’ free Lakebridge converts T-SQL with its Morpheus transpiler and SSIS experimentally with BladeBridge. Genie Migrate converts T-SQL with an agent in the workspace. Partner tools include Next Pathway SHIFT and LeapLogic. Novuz converts procedures, packages and schedules by fixed rules with a reconciliation report for every object.
Does Lakebridge convert SSIS?
Yes, experimentally. Its SSIS guide converts DTSX packages to Databricks notebooks through BladeBridge, and says Script Task and Script Component code in C# or VB.NET must be rewritten by hand.
What is Genie Migrate?
A Databricks converter, formerly called the agentic code converter. Agents convert SQL files from T-SQL, Snowflake, Teradata and other dialects into Databricks SQL or notebooks, then check syntax and intent. Notebook output is in Beta, and each run handles up to 500 files.
What happens to SQL Agent jobs?
They have to be rebuilt as Databricks Workflows or another scheduler. Lakebridge and Genie Migrate do not list SQL Agent. Novuz rebuilds the schedules with their original dependencies and reconciles the jobs they run.
Last reviewed:
Find out what your logic debt is costing you.
Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.
Not sure which door? The scorecard takes ten minutes and tells you.