Azure Migration Services Explained: The Complete Toolkit
ByDishank Sharma
Table of contents
TLDR: Azure migration services are Microsoft's tools for moving workloads into Azure. Azure Migrate discovers, assesses, costs and moves servers. Azure Database Migration Service moves databases. Storage Mover and Data Box move files and bulk data. Azure VMware Solution relocates VMware estates, and Azure Accelerate helps fund the work.
If you are planning a migration to Azure cloud, or are part-way through one, the hard part usually is not Azure itself. It is knowing which of Microsoft's Azure cloud migration services applies to each workload. The toolkit covers discovery, cost modelling, server moves, database migration, file and bulk data transfer, and VMware relocation. Most teams use two of these tools and never learn the rest exist.
This guide explains every core Azure migration service in plain English, gives you an Azure migration strategy you can follow step by step, and shows how data migration to Azure works in practice, whether you are moving one database or a whole application estate. You can read what Microsoft Azure is and how it works.
Microsoft Azure migration services: the core toolkit
Azure Migrate: the hub for the whole project
Azure Migrate is Microsoft's central migration service. It discovers your on-premises servers, databases and web apps, assesses them for cloud readiness, estimates cost, and then moves the servers, all from one place. If you look at only one Azure migration service before you start, make it this one. It does the job that AWS Migration Hub, Application Discovery Service and Application Migration Service do between them.
Azure Migrate business case and Azure Cost Management: from estimate to actual spend
The business case feature in Azure Migrate models what your workloads would cost to run in Azure, using the discovery data it has already collected. You get a real total cost of ownership (TCO) comparison instead of a guess, which helps with budget sign-off. Once workloads are live, Azure Cost Management tracks what you actually spend, so you can compare the two.
Azure Database Migration Service: built for data migration to Azure
Azure Database Migration Service moves databases into Azure with minimal downtime. It handles SQL Server to Azure SQL, and MySQL, PostgreSQL and MongoDB to their Azure managed equivalents, keeping the source live while data syncs. This is the service most "data migration to Azure" searches are looking for, and it exists to remove the downtime risk that makes database moves the scariest part of any migration. For Oracle to Azure SQL, Microsoft's SQL Server Migration Assistant converts the schema first.
Azure Storage Mover and AzCopy: moving files online
Azure Storage Mover is a managed service that moves file shares from on-premises storage into Azure Storage and tracks each job. AzCopy is the free command-line tool for one-off or scripted copies. Use them when your connection can carry the volume in a reasonable time.
Azure Data Box: when bandwidth is the bottleneck
Azure Data Box is a physical device Microsoft ships to you. You load your data locally, ship it back, and Microsoft uploads it into your Azure storage account. It is the Azure equivalent of AWS Snowball, built for data volumes that would take too long over a standard internet connection.
Azure VMware Solution: move VMware as it is
Azure VMware Solution runs your VMware environment on dedicated hosts in Azure. You move virtual machines without converting them and keep using the VMware tools your team knows. It is the fastest route out of a data centre for a large VMware estate, and you can modernise individual workloads later.
Azure Site Recovery: migration's disaster recovery cousin
Azure Site Recovery is Microsoft's disaster recovery service. It continuously replicates servers into Azure, which is why it has often been used to stage a low-risk migration. Microsoft now recommends Azure Migrate for most server migrations, so treat Site Recovery as your DR tool once the move is done.
Azure cloud migration services at a glance
Most migrations to Azure use three or four of these tools together.
| Tool | What it does | Use it when | Cost to use the tool |
|---|---|---|---|
| Azure Migrate | Discovers, assesses and moves servers | Every migration; start here | Discovery and assessment free; server migration free for 180 days per server |
| Azure Migrate business case | Models Azure cost against current spend | You need budget sign-off | Included in Azure Migrate |
| Azure Cost Management | Tracks actual Azure spend | From the first workload you move | Free for Azure spend |
| Azure Database Migration Service | Moves databases with minimal downtime | You are moving SQL Server, MySQL, PostgreSQL or MongoDB | Check Azure pricing |
| Azure Storage Mover and AzCopy | Moves files online | Your connection can carry the volume | No charge for the tools |
| Azure Data Box | Moves data on a shipped device | Your connection is too slow | Per order |
| Azure VMware Solution | Runs VMware on dedicated Azure hosts | You want to move VMware as it is | Per host |
| Azure Site Recovery | Replicates servers for disaster recovery | You need DR after the move | Per protected server |
Azure vs AWS migration tools: the equivalents
| Job | Azure | AWS |
|---|---|---|
| Discover and assess | Azure Migrate | Application Discovery Service, Migration Hub |
| Build the cost case | Azure Migrate business case | Migration Evaluator |
| Move servers | Azure Migrate | Application Migration Service (MGN) |
| Move databases | Azure Database Migration Service | AWS Database Migration Service |
| Move files online | Azure Storage Mover, AzCopy | AWS DataSync |
| Move bulk data offline | Azure Data Box | AWS Snowball |
| Move VMware as is | Azure VMware Solution | Amazon Elastic VMware Service |
| Migration funding | Azure Accelerate | Migration Acceleration Program (MAP) |
| Startup credits | Microsoft for Startups | AWS Activate |
Table of contents
Azure migration strategy: a 6-step framework that works
An Azure migration strategy is the plan that decides what moves, in what order, by which method, and at what cost. Most Azure migration strategy content is either too abstract to act on or written for enterprises with a dedicated migration office. This version works for an SMB moving its first workload and for a startup replatforming after outgrowing its setup. It follows the same order as Microsoft's Cloud Adoption Framework: plan, ready, adopt, manage.
- Assess first, not last. Run Azure Migrate discovery and assessment before you decide anything else. You cannot build an Azure migration strategy on assumptions about what you are running.
- Pick a strategy for each workload. Rehost, replatform, refactor, repurchase, relocate, retain or retire. Decide per workload, not as one blanket choice for your whole environment.
- Build your landing zone. Set up the Azure subscriptions, networking, identity and security policies your workloads will land in, before the first one moves. Microsoft's Azure landing zone templates are a good starting point.
- Treat data migration to Azure as its own workstream. Databases carry the most migration risk. Put Azure Database Migration Service in the plan early, not as an afterthought.
- Migrate in waves, and test before you cut over. Move a low-risk workload first, test it in Azure, then move the rest in groups. Test anything customer-facing before the final cutover.
- Watch cost from the first workload. Use Azure Cost Management from day one so your migration to Azure cloud does not turn into a surprise bill three months in.
The pattern is simple: discovery before decisions, strategy before tooling, foundations before workloads, and cost visibility from the first move, not the last.
Which Azure tool matches which migration strategy (the 7 Rs)
| Strategy | What it means | Main Azure tool | What it does for you |
|---|---|---|---|
| Rehost | Lift and shift, no code changes | Azure Migrate | Replicates and moves servers with minimal changes |
| Replatform | Small changes, such as a managed database | Azure Migrate and Database Migration Service | Moves the app as is and swaps in Azure SQL on the way |
| Refactor | Rebuild for cloud | Azure Migrate (assessment) and Azure App Service, AKS or Functions | Assesses the app, then you rebuild on platform services |
| Relocate | Move VMware as is | Azure VMware Solution | Runs your VMware stack in Azure without converting VMs |
| Repurchase | Switch to a SaaS product | Database Migration Service or Storage Mover for the data | Moves your data into the new product |
| Retain | Keep on-premises for now | Azure Migrate (discovery) | Records what stays and what depends on it |
| Retire | Switch it off | Azure Migrate (discovery and business case) | Finds unused servers and shows the saving |
Table of contents
Data migration to Azure: how it works
Data migration to Azure cloud follows five steps, whether you are moving one database or fifty.
- Inventory your databases. Azure Migrate discovers SQL Server instances and assesses them for Azure readiness. List the other engines (MySQL, PostgreSQL, Oracle, MongoDB) by hand if you need to.
- Choose the target for each database. For SQL Server, pick between Azure SQL Database (fully managed, single databases), Azure SQL Managed Instance (closest to full SQL Server compatibility) and SQL Server on Azure Virtual Machines (full control). MySQL and PostgreSQL go to their Azure flexible servers.
- Convert the schema if the engine changes. Moving Oracle to Azure SQL? Use SQL Server Migration Assistant to convert tables, views and code first.
- Choose online or offline migration. Online migration keeps the source database live and syncs changes until a short cutover. Offline migration is simpler, but the application is down while the data copies.
- Test, then cut over. Check row counts, run your key queries against the new database, update connection strings, then switch traffic.
Moving files and bulk data: online or Data Box?
The choice comes down to how long the transfer would take on your connection. As a guide, 10 TB over a fully used 100 Mbps line takes about 9 days.
| Your situation | Use |
|---|---|
| Small or medium file shares, good connection | Azure Storage Mover, or AzCopy for one-off copies |
| Transfer would take more than about a week, or the line is shared | Azure Data Box |
| Data keeps changing during the move | An online tool for the final sync, even if Data Box carried the bulk |
Table of contents
The programs that help you pay for a migration to Azure cloud
-
Azure Accelerate: Microsoft's program for funding and supporting larger migrations and modernisation projects. In 2025 it brought together the earlier Azure Migration and Modernization Program (AMMP) and Azure Innovate. It offers incentives, credits and expert help, and is usually accessed through a Microsoft partner. It plays the same role as AWS's MAP.
-
Microsoft for Startups: Azure credits and support for early-stage companies, which can offset much of an early migration to Azure. Eligibility and credit levels depend on your stage.
Where to land: Azure regions and data rules for India, Canada and the US
Choose your target Azure region before you start replication, because every Azure Migrate project and database migration points at one.
| Market | Azure regions | Data rules to check before you move |
|---|---|---|
| India | Central India (Pune), South India (Chennai), West India (Mumbai) | DPDP Act, 2023 (most duties apply from 13 May 2027); RBI rules that keep payment data in India; sector rules for banks, NBFCs and insurers |
| Canada | Canada (Central) in Montreal, Canada West (Calgary) | PIPEDA; Quebec's Law 25, which requires a privacy impact assessment before personal data leaves Quebec; provincial rules for health and public sector data |
| United States | Several, including US East (N. Virginia), US East (Ohio) and US West (Oregon) | Sector rules such as HIPAA for health data; state privacy laws such as California's CCPA |
Table of contents
Why use a partner for a migration to Azure?
Azure's tools handle the mechanics of moving servers and data. They do not decide which workload gets which strategy, how to sequence a multi-app move without breaking dependencies, how to apply for Azure Accelerate funding, or how to set up a landing zone that passes a security review on day one. That judgement is where most migrations succeed or stall.
Planning a migration to Azure? Build the strategy first
HabileLabs is a Microsoft Partner working across Azure, AWS and Oracle migrations. We run Azure Migrate discovery, Database Migration Service cutovers and staged migrations for SMBs and startups that need it done right the first time, not re-architected a year later. With teams in India, Canada and the USA, we plan around the Azure region and data rules that apply to you.