Skip to main content

Assessing Your Azure Data Factory for Migration to Fabric Data Factory

Headshot of article author Sindhu Bharadwaj

As organizations modernize their data integration workflows, moving from Azure Data Factory (ADF) to Fabric Data Factory is an important milestone. Before starting the migration, it’s crucial to determine which pipelines and activities are ready to move, which require modifications, and which are not yet supported in Fabric. The built-in migration assessment tool in ADF streamlines this evaluation.

Why Perform a Migration Assessment?

Migration involves more than transferring resources. It ensures compatibility and minimizes disruption. Use the assessment tool to:

  • Identify pipelines and activities ready for migration
  • Flag items that need changes or aren’t currently supported
  • Export a comprehensive report for planning and tracking

How to Run the Assessment

  • Open your Azure Data Factory instance in the Azure portal.
  • Select the Run upgrade assessment (preview) button in the authoring canvas toolbar.
Screenshot for running upgrade assessment from Azure Data Factory authoring canvas

Figure: Run upgrade assessment

  • Review the side pane listing of your pipelines and the activities within. Expand each pipeline for more details.
Screenshot showing assessment summary on the side panel

Figure: View assessment summary

  • Select Export option to download a CSV report containing pipelines and activity statuses.

 

Screenshot showing the drilldownn of assessment along with export option

Figure: View assessment summary drill-down

Understanding Assessment Results

Each pipeline and activity will be tagged with one of four statuses:

  • Ready: Good to go for migration
  • Needs review: Requires changes before migration (e.g., parameters)
  • Coming soon: Support in progress; migrate later (e.g., dataflows)
  • Not compatible: No equivalent in Fabric; refactor required

Note: The overall pipeline status will reflect the most restrictive status among its activities—if there are activities tagged as “Needs review,” “Coming soon,” or “Not compatible,” the pipeline will inherit “Not compatible” as the pipeline status to ensure migration readiness is accurately represented.

Next Steps

While we are building a native UX based migration experience you may:

Resources