Migrate assets (infrastructure, apps, and data)
In this phase of the journey, you use the output of the assess phase to initiate the migration of the environment. This guide helps identify the appropriate tools to reach a "done state", including native tools, third-party tools, and project management tools.
The following sections describe the native Azure tools available to perform or assist with migration. For information on choosing the right tools to support your migration efforts, see the Cloud Adoption Framework's Migration tools decision guide.
Azure Migrate delivers a unified and extensible migration experience. Azure Migrate provides a one-stop, dedicated experience to track your migration journey across the phases of assessment and migration to Azure. It provides you the option to use the tools of your choice and track the progress of migration across these tools.
Azure Migrate provides the following functionality:
- Enhanced assessment and migration capabilities:
- Hyper-V assessments.
- Improved VMware assessment.
- Agentless migration of VMware virtual machines to Azure.
- Unified assessment, migration, and progress tracking.
- Extensible approach with ISV integration (such as Cloudamize).
To perform a migration using Azure Migrate follow these steps:
- Search for Azure Migrate under All services. Select Azure Migrate to continue.
- Select Add a tool to start your migration project.
- Select the subscription, resource group, and geography to host the migration.
- Select Select assessment tool > Azure Migrate: Server Assessment > Next.
- Select Review + add tool(s), and verify the configuration. Click Add tool(s) to initiate the job to create the migration project and register the selected solutions.
Azure Site Recovery
The Azure Site Recovery service can manage the migration of on-premises resources to Azure. It can also manage and orchestrate disaster recovery of on-premises machines and Azure VMs for business continuity and disaster recovery (BCDR) purposes.
The following steps outline the process to use Site Recovery to migrate:
Depending on your scenario, these steps may differ slightly. For more information, see the Migrate on-premises machines to Azure article.
Prepare Azure Site Recovery service
- In the Azure portal, select +Create a resource > Management Tools > Backup and Site Recovery.
- If you haven't yet created a recovery vault, complete the wizard to create a Recovery Services vault resource.
- In the Resource menu, select Site Recovery > Prepare Infrastructure > Protection goal.
- In Protection goal, select what you want to migrate.
- VMware: Select To Azure > Yes, with VMware vSphere Hypervisor.
- Physical machine: Select To Azure > Not virtualized/Other.
- Hyper-V: Select To Azure > Yes, with Hyper-V. If Hyper-V VMs are managed by VMM, select Yes.
Configure migration settings
- Set up the source environment as appropriate.
- Set up the target environment.
- Click Prepare infrastructure > Target, and select the Azure subscription you want to use.
- Specify the Resource Manager deployment model.
- Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
- Set up a replication policy.
- Enable replication.
- Run a test migration (test failover).
Migrate to Azure using failover
- In Settings > Replicated items select the machine > Failover.
- In Failover select a Recovery Point to fail over to. Select the latest recovery point.
- Configure any encryption key settings as required.
- Select Shut down machine before beginning failover. Site Recovery will attempt to shut down virtual machines before triggering the failover. Failover continues even if shutdown fails. You can follow the failover progress on the Jobs page.
- Check that the Azure VM appears in Azure as expected.
- In Replicated items, right-click the VM and choose Complete Migration.
- Perform any post-migration steps as required (see relevant information in this guide).
For more information, see:
Azure Database Migration Service
The Azure Database Migration Service is a fully managed service that enables seamless migrations from multiple database sources to Azure data platforms, with minimal downtime (online migrations). The Azure Database Migration Service performs all of the required steps. You can initiate your migration projects with the assurance that the process takes advantage of best practices recommended by Microsoft.
Create an Azure Database Migration Service instance
If this is the first time using Azure Database Migration Service, you need to register the resource provider for your Azure subscription:
- Select All services, then Subscriptions, and choose the target subscription.
- Select Resource providers.
- Search for
migration, and then to the right of Microsoft.DataMigration, select Register.
After you register the resource provider, you can create an instance of Azure Database Migration Service.
- Select +Create a resource and search the marketplace for Azure Database Migration Service.
- Complete the Create Migration Service wizard, and select Create.
The service is now ready to migrate the supported source databases (for example, SQL Server, MySQL, PostgreSQL, or MongoDb).
For more information, see:
Data Migration Assistant
The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can affect database functionality in your new version of SQL Server or Azure SQL Database. DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.
For large migrations (in terms of number and size of databases), we recommend that you use the Azure Database Migration Service, which can migrate databases at scale.
To get started with the Data Migration Assistant follow these steps.
- Download and Install the Data Migration Assistant from the Microsoft Download Center.
- Create an assessment by clicking the New (+) icon and select the Assessment project type.
- Set the source and target server type. Click Create.
- Configure the assessment options as required (recommend all defaults).
- Add the databases to assess.
- Click Next to start the assessment.
- View results within the Data Migration Assistant tool set.
For an enterprise, we recommend following the approach outlined in Assess an enterprise and consolidate assessment reports with DMA to assess multiple servers, combine the reports and then use provided Power BI reports to analyze the results.
For more information, including detailed usage steps, see:
- Data Migration Assistant overview
- Assess an enterprise and consolidate assessment reports with DMA
- Analyze consolidated assessment reports created by Data Migration Assistant with Power BI
SQL Server Migration Assistant
Microsoft SQL Server Migration Assistant (SSMA) is a tool designed to automate database migration to SQL Server from Microsoft Access, DB2, MySQL, Oracle, and SAP ASE. The general concept is to collect, assess, and then review with these tools, however, due to the variances in the process for each of the source systems we recommend reviewing the detailed SQL Server Migration Assistant documentation.
For more information, see:
Database Experimentation Assistant
Database Experimentation Assistant (DEA) is a new A/B testing solution for SQL Server upgrades. It will assist in evaluating a targeted version of SQL for a given workload. Customers who are upgrading from previous SQL Server versions (SQL Server 2005 and above) to any new version of the SQL Server can use these analysis metrics.
The Database Experimentation Assistant contains the following workflow activities:
- Capture: The first step of SQL Server A/B testing is to capture a trace on your source server. The source server usually is the production server.
- Replay: The second step of SQL Server A/B testing is to replay the trace file that was captured to your target servers. Then, collect extensive traces from the replays for analysis.
- Analysis: The final step is to generate an analysis report by using the replay traces. The analysis report can help you gain insight about the performance implications of the proposed change.
For more information, see: