Prepare for Fabric Migration

Before migrating individual workloads to Microsoft Fabric, it’s essential to prepare both your organization and your Fabric landing zone resources. This phase ensures that foundational elements are ready, that roles and responsibilities are aligned, and that skills are developed.

⚠️ Without proper preparation, migration efforts are prone to setbacks, rework, and delays. This can compromise your project's success and result in duplicated effort.

Migration Preparation Checklist

The following table outlines the key preparation activities and the roles involved in each:

Activity	Description	Responsible Roles
Prepare tools and initial backlog	Ensure that you have the right Fabric CLI tools, provisioning scripts, and governance automation in place. Create a workload backlog derived from your Fabric digital estate.	Project sponsor, Fabric architect, Project manager
Select regions and tenant configuration	Choose appropriate regions and capacity for Fabric workspaces and OneLake storage. Consider data residency, compliance, and performance.	Fabric architect, Governance lead, Cloud operations
Align roles and responsibilities	Define clear ownership for migration activities: workspace owners, data engineers, platform team, governance office.	Project manager, Stakeholders, Fabric sponsor
Build team skills and readiness	Train teams on Fabric components: Data Factory in Fabric, Lakehouse, Warehouse, Data Activator, Power BI and CLI/REST.	Project manager, Adoption/change lead

Next Step

➡️ Continue with: Prepare tools and backlog