synapse-migration

To migrate Azure Synapse Spark workloads to Microsoft Fabric, you can automate inventory, mapping decisions, and artifact rewrites across Notebooks, Spark Job Definitions, and Lake Databases using a guided workflow with phased validation gates.

The best way to convert Synapse mssparkutils and Linked Services is to use automated tooling that rewrites these specific patterns into Fabric equivalents like notebookutils, Data Connections, and OneLake Shortcuts during your migration.

Migrating Synapse Lake Databases to Fabric OneLake involves orchestrating inventory and mapping decisions, offering options for schemas in a single Lakehouse or separate Lakehouses, and applying auto-bindings for Notebooks and Spark Job Definitions.

Yes, you can automatically migrate Synapse Spark Job Definitions to Fabric. The migration process includes phased validation gates and auto-bindings to ensure your SJDs are correctly mapped and rewritten for the Fabric environment.

If your Synapse Spark workload uses an external Hive metastore, the migration process flags the external HMS as a blocker. Phased validation gates surface these blockers to guide your mapping decisions before artifact rewrites proceed.

Migrating Synapse Notebooks to Fabric does not require extensive manual code rewrites. Automated tooling rewrites Synapse-specific patterns and ADLS access patterns into Fabric equivalents, while enforcing best practices through validity checks.