Intellus Accelerator · Concept

Move off Synapse without three weeks of archaeology in a spreadsheet.

The accelerator reads a whole Synapse workspace, SQL pool catalogs, Spark notebooks and pipelines, and builds one inventory with a complexity rating per object. From that it emits Databricks-native equivalents: Unity Catalog Delta DDL, translated T-SQL, remapped notebooks and Workflows as Asset Bundles. Everything it cannot translate honestly is marked and handed to a human.

For Data platform teams Maturity Concept Platform Azure Databricks
The problem

A Synapse workspace is not one migration, it is three.

Synapse Analytics is on a clear end-of-road path, and teams that picked Databricks find the same thing every time. A dedicated SQL pool, a set of Spark notebooks and a pipeline layer that is ADF wearing a different badge each need a different translation strategy. Nobody has a full inventory of what is still running, so the project starts with hand-written discovery.

🧱

Dedicated SQL pool DDL does not port

DISTRIBUTION = HASH, clustered columnstore indexes, resource classes and workload groups have no literal equivalent in Unity Catalog. A naive lift produces Delta tables with a terrible file layout and no one notices until the first month-end run.

⚠️

Stored procedures break silently

Dynamic SQL through sp_executesql, #temp tables, CROSS APPLY, TRY/CATCH, DATEADD argument order, CONVERT style codes. Line-by-line rewriting is slow, and a wrong ISNULL is a wrong number in a report six months later.

🔗

Orchestration is rebuilt from memory

Pipelines and notebooks reference linked services, workspace-managed identities and Key Vault entries that map to external locations, storage credentials and secret scopes. The mapping is one-to-many and undocumented, so it gets reconstructed by hand.

How it works

Front-load the archaeology, automate the mechanical rewrite, route the judgement calls to a person.

It reads the workspace from its Git-connected repository or an ARM export, plus live catalog metadata from the dedicated and serverless SQL pools. Every object gets classified as mechanical, needs review, or needs a design decision. Output lands as reviewable code in a repository, never pushed straight into a workspace.

1

Workspace inventory and dependency graph

Parses the Synapse Git repo or ARM export together with SQL pool system catalogs: every table with its distribution, index type, partitioning and column types, every procedure, view, notebook and pipeline, and the lineage between them. Which pipeline calls which notebook, which notebook writes which table, which view no one queries.

2

Table DDL with layout advice

Converts dedicated SQL pool DDL to Unity Catalog Delta. Distribution keys and columnstore indexes are translated into a concrete liquid clustering or partitioning proposal based on column cardinality and observed query patterns, rather than dropped on the floor.

3

T-SQL to Databricks SQL and PySpark

Rewrites stored procedures, views and functions with an annotated diff and a comment on every construct that changed meaning. Dynamic SQL, cursors, table variables and transaction blocks are left in place, marked, and routed to a human.

4

Notebook and utility remapping

Translates Synapse Spark notebooks to Databricks conventions: mssparkutils calls mapped to dbutils, linked-service reads to Unity Catalog external locations, Key Vault references to secret scopes.

5

Orchestration as code

Turns the pipeline activity graph into Databricks Workflows job definitions emitted as Asset Bundles, keeping dependencies, retry behaviour and trigger schedules explicit and reviewable in a pull request instead of rebuilt as click-work.

6

Wave planning and open decisions

Groups objects into dependency-safe waves with a complexity rating each, so the estimate comes from the actual workspace. Security models, incremental and SCD logic, and warehouse sizing are surfaced as decisions with context attached, for a human to sign off.

Built on

Azure Synapse on the way in, Unity Catalog and Asset Bundles on the way out.

Source side is read-only: workspace Git integration, ARM exports and SQL pool system catalogs. Target side is Azure Databricks with Unity Catalog enabled. The conversion pass combines a T-SQL parser for the deterministic work with Claude for the steps that need judgement about intent, and Git-based review is the delivery mechanism.

Azure Synapse Analytics Dedicated SQL pools Serverless SQL pools Synapse Spark pools Synapse pipelines ADLS Gen2 Azure Key Vault Microsoft Entra ID Azure Databricks Unity Catalog Delta Lake Liquid clustering Databricks SQL warehouses Databricks Workflows Databricks Asset Bundles Auto Loader Secret scopes Databricks SDK for Python T-SQL parser Claude Azure DevOps / GitHub

Bring a workspace export and we will run the inventory pass against it.

We walk through the output together: object counts, the complexity split, the dependency graph, and the list of decisions that need an owner. That session is the honest input to a migration estimate, not a sales deck.