pipeline-migration

Migrate Synapse Data Factory pipeline artifacts to Microsoft Fabric Data Factory via REST APIs.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill pipeline-migration-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pipeline-migration
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/pipeline-migration
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill pipeline-migration-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes references (resource) components.

What problem does it solve? Migrating Azure Synapse Analytics pipelines to Microsoft Fabric Data Factory requires manually rewriting activity JSON, converting linked services to Fabric connections, inlining dataset definitions, and translating global parameters — a slow, error-prone process with many platform-specific gotchas. ## Core Features & Use Cases - Activity Type Migration: Converts SynapseNotebook activities to TridentNotebook (GUID-based references), rewrites Validation activities as GetMetadata + IfCondition, and parks unsupported types like SSIS and Databricks. - Artifact Translation: Maps linked services to Fabric connections, inlines dataset definitions into activity typeProperties, and converts global parameters into a Fabric Variable Library with value sets. - Assessment & Orchestration: Provides a read-only pre-migration assessment report and a phased inline migration workflow driven through Synapse and Fabric REST APIs. - Use Case: A data engineer needs to move 30 Synapse pipelines to a Fabric workspace. The skill assesses scope, creates connections and a Variable Library, transforms each pipeline's JSON, deploys it via the Fabric REST API, and produces a validation report. ## Quick Start Ask the AI to migrate all pipelines from your Synapse workspace to a named Fabric workspace, starting with a pre-migration assessment.

Frequently Asked Questions about pipeline-migration

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

FAQPage Schema
How do I migrate Synapse pipelines to Microsoft Fabric Data Factory?▼

Run the read-only assessment first, then execute the phased migration: convert global parameters to a Variable Library, create Fabric connections from linked services, inline datasets into activities, transform activity JSON, and deploy pipelines via the Fabric REST API.

How to convert SynapseNotebook activities to Fabric TridentNotebook?▼

Rename the activity type to TridentNotebook, replace the notebook name reference with the Fabric notebook GUID from GET /v1/workspaces/{wsId}/notebooks, add workspaceId, and remove sparkPool and sessionConfiguration blocks. Notebooks must be migrated to Fabric first.

Does Microsoft Fabric support Synapse dataset items in pipelines?▼

No, Fabric Data Factory has no Dataset item type. All dataset properties must be inlined directly into each activity's typeProperties as storeSettings and formatSettings, with the linked service replaced by a Fabric connection display name.

What happens to Synapse global parameters after migrating to Fabric?▼

Global parameters become a Fabric Variable Library item, referenced as @pipeline().libraryVariables.<name>. Array and Object types are serialized as JSON strings, and Float/Double map to String because Number types are not consumable in pipelines.

Which Synapse activity types cannot be migrated to Fabric Data Factory?▼

ExecuteSSISPackage, Databricks activities, AzureBatch, Custom, and HDInsight MapReduce/Pig/Hive have no Fabric equivalent and are parked. Self-Hosted IR backed linked services require an on-premises data gateway in Fabric before migration.

Why does a migrated Fabric pipeline fail on ExecutePipeline activities?▼

Fabric requires workspaceId in the ExecutePipeline typeProperties even for same-workspace child pipelines, and pipeline.referenceName must be the Fabric item GUID. Omitting workspaceId causes runtime failures because Fabric does not fall back to the current workspace.