Migrating to the Microsoft Fabric platform offers a transformative opportunity for your organization to optimize data management and leverage advanced capabilities. Depending on your current technology infrastructure, your migration journey will fall into one of two primary scenarios. Understanding these scenarios is crucial for determining the best approach for your migration strategy to achieve a seamless transition.
Whether your organization is opting for a straightforward lift and shift or a more comprehensive evaluate, design and build migration strategy – the key to a successful Microsoft Fabric migration lies in careful planning and a thorough understanding of your current data environment.
Migration scenarios
Depending on your organization’s current technology infrastructure, one of two migration scenarios will be taken when implementing Microsoft Fabric: (1) cloud-to-cloud migration or (2) on-premises to cloud migration.
- Cloud-to-cloud migration: This scenario involves moving data and processes from one cloud environment to Fabric. This would be done by an organization that is already using a different cloud platform, such as Databricks or Snowflake, or is already leveraging Azure, but looking to move to Fabrice for improved efficiency and capabilities.
- On-premises to cloud migration: This scenario involves transitioning from on-premises data storage and processing to a cloud-based solution. This would be done by an organization with on-premises infrastructure looking to move to the cloud using Fabric.
Understanding these two scenarios can help your organization determine the best approach for your migration strategy, whether it involves a straightforward lift and shift or a more comprehensive evaluate, design and build approach.
Migration approaches
Regardless of whether your organization is partaking in a cloud-to-cloud or on-premises to cloud migration, there are two main migration approaches you can choose from: (1) lift and shift approach or (2) evaluate, design and build approach.



