skills.rest
weiflycc-cmd
weiflycc-cmdCOMMUNITY
Explore all skills by this author →
GitHub

synapse-migration

Automate Azure Synapse Analytics workload migration to Microsoft Fabric.

Updated Jun 1, 2026
Search Tags:#data migration#pipeline migration#microsoft fabric#sql warehouse#azure synapse#spark notebooks#synapse migration
One-click install
npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill synapse-migration-weiflycc-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: synapse-migration
Source: https://github.com/weiflycc-cmd/skills-for-fabric/tree/main/plugins/fabric-skills/skills/synapse-migration
Command: npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill synapse-migration-weiflycc-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating Azure Synapse Analytics workloads to Microsoft Fabric requires manual rewrites of Spark notebooks, T-SQL code, and pipeline configurations to account for breaking changes in APIs, connectivity patterns, and supported syntax, which is time-consuming and error-prone for data teams.

Core Features & Use Cases

  • Automated Code Translation: Converts mssparkutils calls to Fabric's notebookutils, including the required namespace change from env to runtime.
  • T-SQL and Connectivity Rewrites: Removes unsupported Dedicated SQL Pool distribution hints, replaces PolyBase external tables with COPY INTO statements, and migrates Synapse Linked Services to Fabric Data Connections and OneLake Shortcuts.
  • Pipeline Migration Guidance: Maps Synapse Pipeline activities to Fabric Data Pipeline equivalents and provides before/after code patterns for common migration scenarios. Use case: A data engineer migrating a Synapse workspace with production Spark notebooks, Dedicated SQL Pool tables, and ETL pipelines can use this skill to automate repetitive translation tasks and ensure alignment with Fabric best practices.

Quick Start

Use the synapse-migration skill to port your Synapse Spark notebooks, Dedicated SQL Pool tables, and Pipelines to Microsoft Fabric, including automatic translation of mssparkutils calls and Linked Service replacements.

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 requires translating mssparkutils calls to the notebookutils namespace, including changing the env to runtime context. This process automates the porting of Synapse workloads to Fabric Lakehouses while aligning with new API standards.

Can I convert Synapse Dedicated SQL Pool DDL to Fabric Warehouse syntax?▼

Converting Synapse Dedicated SQL Pool DDL to Fabric Warehouse syntax involves removing unsupported distribution hints and replacing PolyBase external tables with COPY INTO statements. This ensures T-SQL code complies with Fabric's supported connectivity and data access patterns.

What is the best way to migrate Synapse Linked Services to Microsoft Fabric?▼

Migrating Synapse Linked Services to Microsoft Fabric is best handled by replacing them with Fabric Data Connections and OneLake Shortcuts. This updates the connectivity patterns to match Fabric's specific data access model and ensures seamless pipeline integration.

How do Synapse Pipeline activities map to Fabric Data Pipelines?▼

Synapse Pipeline activities map to Fabric Data Pipeline equivalents through guided before and after code pattern translations. This mapping ensures that ETL workflows migrated from Synapse maintain functional parity within the Microsoft Fabric environment.

Do I need to rewrite T-SQL code when moving Azure Synapse workloads to Fabric?▼

Rewriting T-SQL code is required when moving Azure Synapse workloads to Fabric due to breaking changes in supported syntax. You must remove unsupported Dedicated SQL Pool distribution hints and rewrite PolyBase statements to COPY INTO for successful migration.

Why does mssparkutils fail in Microsoft Fabric and how do I fix it?▼

The mssparkutils API fails in Microsoft Fabric because Fabric uses the notebookutils namespace with a runtime context instead of env. Fixing this requires automated code translation to update the API calls for Fabric Lakehouse compatibility.

Related Skills

Explore More Data & Analytics Skills→
tomztomz

azure-synapse

Configure Azure Synapse Analytics environments across SQL, Spark, and pipelines.

Community
Advanced
rritecrritec
3

spark-authoring-cli

Manage Microsoft Fabric Spark authoring tasks and generate notebook-ready code.

Community
Advanced
rritecrritec
3

sqldw-consumption-cli

Execute read-only T-SQL queries against Microsoft Fabric SQL endpoints from the command line.

Community
Advanced
patrikboroschpatrikborosch
14

synapse-migration

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

Community
Advanced