migration 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 Learn

We 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.