Forum Discussion
Helper Imigration multiple adf jsons template to fdf without microsoft ui migration utitlity
Hi dataengineerv2,
Based on our understanding, since you only have ADF artifacts stored in Git or exported JSONs and no active ADF environment, creating a temporary ADF instance, reconnecting it to the repository, and then using the migration assessment could be a viable approach to bring those artifacts into a supported migration workflow. Once the initial migration is completed and validated, we suggest treating Fabric as the new source of truth by enabling Git integration and using Deployment Pipelines and Fabric REST APIs for ongoing lifecycle management, rather than repeatedly rebuilding temporary ADF environments. For future additions, you can generally migrate new pipelines incrementally and validate them as separate migration waves, although any shared dependencies should still be reviewed.
Additionally, please refer to the links below:
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn
Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn
Microsoft Fabric REST API references - Microsoft Fabric REST APIs | Microsoft LearnWe hope the information provided helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Super UserHi dataengineerv2,
Good question and just to clarify one important point: Microsoft now provides official migration options for moving Azure Data Factory pipelines to Fabric Data Factory.
There are mainly a few scenarios to consider :
1. If you still have access to the original ADF environment
You should start with the Microsoft migration / assessment experience. It can assess pipeline readiness, classify items as Ready, Needs review, Coming soon, or Not compatible, and help you plan the migration more safely.
2. If you want to bring ADF into Fabric without immediately rebuilding everything
You can use the Azure Data Factory item / Mount experience in Fabric. This allows you to view and work with your existing ADF from a Fabric workspace while keeping the original ADF environment unchanged.
3. If you want to automate migration at scale
Microsoft has published the Microsoft.FabricPipelineUpgrade PowerShell module. This is probably the closest official option to what you are describing. It can help upgrade ADF and Synapse pipelines to Fabric pipeline definitions.
However, I would still be careful with the idea of a fully automated ADF JSON → Fabric pipeline conversion.
ADF and Fabric Data Factory don’t map 1:1 in every area. Linked services, datasets, triggers, integration runtimes, credentials, gateways, parameters, and unsupported connectors may still require review or manual remediation.
So if you only have exported ADF JSON files but no access to the original ADF environment, I would probably use the PowerShell migration module as the first thing to investigate, then build an assessment layer around it to classify what can be migrated automatically and what needs redesign.
In practice, I would approach it like this :
ADF JSON / existing ADF
- migration assessment
- PowerShell upgrade module where supported
- manual review of connections, credentials, IR/gateway, triggers, unsupported activities
- validation in Fabric workspace
- deployment with Git integration / deployment pipelines
Useful Microsoft docs :
Migration planning for ADF to Fabric
https://learn.microsoft.com/en-us/fabric/data-factory/migrate-planning-azure-data-factory
Upgrade ADF pipelines to Fabric
https://learn.microsoft.com/en-us/azure/data-factory/how-to-upgrade-your-azure-data-factory-pipelines-to-fabric-data-factory
PowerShell migration module
https://learn.microsoft.com/en-us/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-for-azure-data-factory-to-fabric
PowerShell migration tutorial
https://learn.microsoft.com/en-us/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-tutorial
Bring / Mount Azure Data Factory into Fabric
https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-bring-azure-data-factory-to-fabric
Migration best practices
https://learn.microsoft.com/en-us/fabric/data-factory/migration-best-practices
So I would not start from a custom parser unless the official PowerShell upgrade path cannot cover your scenario. The custom parser approach can still be useful, but more as an assessment or gap-analysis tool than as the primary migration engine.