synapse-migration

Automate Azure Synapse Spark workload migration to Microsoft Fabric via REST APIs.

14|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill synapse-migration-patrikborosch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synapse-migration
Source: https://github.com/patrikborosch/AnalyticsPlatformAgents/tree/main/creator/skills/synapse-migration
Command: npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill synapse-migration-patrikborosch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating Azure Synapse Analytics Spark workloads to Microsoft Fabric requires rewriting code, replacing Linked Services, remapping compute, and validating data integrity across dozens or hundreds of notebooks and Spark Job Definitions. This Skill automates the end-to-end migration workflow, handling API-driven artifact transfer, code refactoring for mssparkutils to notebookutils, and post-migration validation.

Core Features & Use Cases

  • API-Driven Migration: Automates the transfer of Spark pools, Lake Databases, notebooks, and Spark Job Definitions from Synapse to Fabric via REST APIs.
  • Code Refactoring: Rewrites Synapse-specific patterns including mssparkutils imports, Linked Service references, spark.read.synapsesql calls, and ADLS paths to OneLake shortcuts.
  • Validation & Reporting: Generates migration reports with portal links, validates row counts and shortcut health, and flags blockers like GPU pools or .NET for Spark workloads.

Quick Start

Use the synapse-migration skill to migrate your Synapse workspace to a target Fabric workspace by providing the source workspace name and target workspace name.

Frequently Asked Questions about synapse-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Azure Synapse Spark notebooks to Microsoft Fabric?

Migrating Azure Synapse Spark notebooks to Microsoft Fabric is automated via REST APIs that transfer artifacts and refactor mssparkutils imports to notebookutils. You provide the source Synapse workspace and target Fabric workspace to initiate the end-to-end transfer.

What gets refactored when moving Synapse Spark workloads to Fabric?

When moving Synapse Spark workloads to Fabric, code refactoring automatically rewrites mssparkutils imports, Linked Service references, spark.read.synapsesql calls, and ADLS paths to OneLake shortcuts. This ensures your notebooks and Spark Job Definitions execute correctly in the Fabric Lakehouse environment.

Do I need Azure CLI authentication tokens for Synapse to Fabric migration?

Yes, Synapse to Fabric migration requires Azure CLI authentication tokens for Synapse ARM, Synapse data plane, and Fabric REST API audiences. These tokens authorize the API-driven transfer of Spark pools, Lake Databases, notebooks, and Spark Job Definitions.

Can I migrate all Azure Synapse Spark pools to Fabric?

You cannot migrate all Azure Synapse Spark pools to Fabric automatically. The migration process validates your workspace and flags blockers like GPU pools or .NET for Spark workloads, which require manual intervention or alternative compute strategies.

How does Synapse to Fabric migration validate data integrity?

Synapse to Fabric migration validates data integrity by generating post-migration reports that check row counts and verify OneLake shortcut health. These reports include direct portal links to the migrated artifacts in your Fabric workspace for immediate visual confirmation.