Blog · Data and analytics

Synapse to Fabric: what the Migration Assistant does, and what it doesn't

Microsoft's Fabric Migration Assistant moves the warehouse. Here is what it covers, and the five-point list we plan for on every Synapse-to-Fabric move.

A row of dark server racks with blue status lights lining both sides of a data center aisle, lit from above

Microsoft now offers the Fabric Migration Assistant for Data Warehouse. For teams on Azure Synapse dedicated SQL pools, it copies metadata and data into a Fabric Data Warehouse and converts the source schema automatically. AI-powered suggestions help with incompatibilities during the move.

That covers the warehouse. A migration also has to cover everything connected to it. Microsoft's own guide ends with a step called Reroute connections: finding every report and pipeline that points at the old warehouse, testing it against the new one, and switching it over.

What we plan for on every Synapse-to-Fabric move:

  1. An inventory: tables, stored procedures, pipelines, reports and who owns each.
  2. One proof report the business trusts, where old and new numbers must match.
  3. Pipelines rebuilt or repointed, with schedules and monitoring.
  4. A cut-over plan with a rollback window.
  5. Decisions on what to modernize now (for example, moving logic into Fabric pipelines) and what to move as it is.

The Migration Assistant handles the warehouse itself. The rest of that list is where projects slip, and where planning pays off.

Talk to an Expert

Tell us what you're working on, and we'll tell you how we would approach it.

Talk to an Expert