We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

How to Migrate VMware Workloads to the Cloud

For the IT head or infrastructure lead in India or the GCC, this guide sets out ten steps in four stages for moving VMware workloads to AWS or Azure. They cover inventory and dependencies, a route for each VM, target and region, the landing zone, a pilot, waves worked back from the renewal date, a cutover with a way back, and switching off the old hosts. No prices and no tool vendors.

This guide shows how to migrate VMware to cloud on AWS or Azure: list and map the estate, give each VM a route, prepare the target, move in tested waves, cut over with a way back, then switch off the old hosts. The two route families are rehost to cloud VMs and, instead, relocate to VMware run by the cloud.


Last reviewed 2026-11-16 by Manish Sharma.

A VM is a server that runs as software, whereas a hypervisor is the layer that runs many VMs on one host. A VMware cloud migration starts from a renewal date, but why the VMware renewal now forces a decision has its own guide. Scope here is AWS and Azure only, so no prices appear. For help with planning a VMware move to AWS or Azure with us, see the use case page.

How to Migrate VMware to Cloud: 10 Steps in Four Stages

The ten steps fall into four stages, while each step has an output and an owner. Teams that ask how to migrate VMware workloads should read the table first, then the detail.

Step Output Owner
1. List every VM, host and owner Inventory Infrastructure lead
2. Map which servers talk to each other Application groups Infrastructure lead
3. Give each VM a route Route per VM Application owners
4. Pick the target service and region Target decision IT head
5. Build the landing zone Ready network, identity and logging Cloud engineer
6. Run a pilot wave Signed pilot Application owner
7. Plan the waves back from the renewal date Wave calendar Infrastructure lead
8. Replicate and test each wave Test record per wave Cloud engineer
9. Cut over with a way back Live workloads Application owner
10. Switch off hosts and shrink the renewal Retired hosts Infrastructure lead
1
Stage 1, know the estate

Steps 1 to 3 list the VMs, map the servers and give each VM a route.

2
Stage 2, prepare the target

Steps 4 and 5 pick the service and region and build the landing zone.

3
Stage 3, pilot and waves

Steps 6 to 8 test the route, plan waves from the renewal date and test each wave.

4
Stage 4, cutover and switch-off

Steps 9 and 10 cut over with a way back and retire the old hosts.

Ten steps in four stages to migrate VMware to cloud: know the estate, prepare the target, pilot and waves, then cutover and switch-off
Ten steps in four stages.

Stage 1: Know the VMware Estate Before You Migrate to Cloud

Three steps give you the facts the rest of the plan depends on, before any build starts.

Step 1: List Every VM, Host and Owner

Export the list from vCenter: each VM with its power state, operating system, size and owner. Add core counts as an inventory field only, because a counting method is a topic for the licensing guide.

Azure Migrate runs a lightweight VMware VM appliance for discovery, assessment and agentless migration, as the Microsoft Learn tutorial Migrate VMware VMs agentless the Migration and modernization tool, dated 16 June 2026, says. We read the three linked pages on 16 November 2026. A page date appears beside each link, unless the page shows none.

  • Output: one list of every VM and host.
  • Owner: the infrastructure lead.
  • Done when: every VM has a named business owner.

Step 2: Map Which Servers Talk to Each Other

Servers that call each other must move together, otherwise the application breaks. Ask each application owner which servers their application calls, then record the answer. AWS Transform MGN lets you group servers into applications. It also works at the server, application or wave level, as the AWS page What Is AWS Transform MGN? says, though it shows no date.

  • Output: application groups.
  • Owner: the infrastructure lead.
  • Done when: every VM sits in an application group.

Step 3: Give Each VM a Route

Give each VM one of these five routes:

  • Retire: switch it off.
  • Retain: leave it where it is.
  • Rehost: move it as it is to a cloud VM.
  • Relocate: move it to VMware run by the cloud.
  • Rebuild: rewrite it for the cloud.

Five routes are enough for this plan. The longer list of migration routes and how each differs has its own post. Which path suits the estate as a whole is a separate topic.

  • Output: one route for every VM.
  • Owner: application owners.
  • Done when: no VM is left without a route.
One route per VM

The route decides the target, the test and the owner of each move, so settle it before you build anything.

Stage 2: Prepare the Cloud Target Before VMware Workloads Migrate

Two steps set up the place the workloads will land.

Step 4: Pick the Target Service and Region

Rehosted VMs land on Amazon EC2 or Azure VMs. Relocated VMs, in contrast, land on Azure VMware Solution or on Amazon Elastic VMware Service. AWS also says the latter runs VMware Cloud Foundation inside your Amazon VPC. Azure VMware Solution gives a private cloud on dedicated hosts. However, Microsoft Learn says every provisioned private cloud has VMware vCenter Server, vSAN, vSphere and NSX, in its page Introduction: Azure VMware Solution, dated 3 November 2026.

Choose the region first, because in Azure Migrate you can’t change the target region and storage account after the first replication of a VM starts. Ask your compliance owner where your data may sit, but name no law here.

  • Output: target service and region per route.
  • Owner: the IT head.
  • Done when: the compliance owner agrees the region.
Region cannot change later

In Azure Migrate, you can’t change the target region and storage account once the first replication of a VM starts.

Step 5: Build the Landing Zone

A landing zone is the network, identity, logging and backup that you set up before the first VM arrives. Plan a private link to your own site, for the period when some VMs have moved and others have not. Running on premises and cloud together is a normal state during a move.

The same Microsoft page also lists network extension with VMware HCX among the customer’s tasks on Azure VMware Solution. For AWS-only steps, however, see the AWS side of a legacy move, check by check.

  • Output: a landing zone ready for the pilot.
  • Owner: the cloud engineer.
  • Done when: the pilot VMs can sign in, log and back up.

Key Takeaway Finish the landing zone and the region decision before any VM replicates.

Stage 3: Migrate VMware to Cloud in a Pilot, Then in Waves

Three steps test the route on a few VMs, then repeat it for the rest.

Step 6: Run a Pilot Wave

Pick two or three low-risk VMs. Test the move in an isolated network, because Microsoft Learn says to use an isolated Azure virtual network to avoid affecting production. The test also leaves replication running and can repeat.

  • Output: a signed pilot.
  • Owner: the application owner.
  • Done when: the owner signs that the pilot VMs work.
Pilot in isolation

Use an isolated network for the test, so the pilot cannot touch production.

Step 7: Plan the Waves Back From the Renewal Date

A VMware migration plan starts from the date the old hosts must go, then works backward. Signisys’s working view is that the last wave should finish before the renewal or hardware date with a margin. Waves should group by application and not by host, and the riskiest wave should not come last. We reach this order because a late wave leaves you renewing for hosts you meant to retire.

We give no date or figure here, because yours come from your contract and hardware.

  • Output: a wave calendar.
  • Owner: the infrastructure lead.
  • Done when: every application group sits in a dated wave.

Step 8: Replicate and Test Each Wave

Replicate the wave, test it and get sign-off. Azure Migrate allows up to 500 replications at once. In AWS Transform MGN, however, each new test replaces the last one.

  • Output: a test record per wave.
  • Owner: the cloud engineer.
  • Done when: the application owner signs the test.

Stage 4: Cutover and Switch-Off Once VMware Workloads Migrate to Cloud

Two steps finish the move and retire what is left.

Step 9: Cut Over With a Way Back

For a planned move with no data loss, shut down the source VMs, as Microsoft Learn describes. A cutover instance in AWS does not receive changes made on the source after it launches, so freeze the source. Finalizing an AWS cutover stops data replication, so do it last.

Keep the source VM until sign-off. Name who decides on rollback, and by when.

  • Output: live workloads and a rollback owner.
  • Owner: the application owner.
  • Done when: the owner signs and the rollback date is set.

Step 10: Switch Off Hosts and Shrink the Renewal

Back up the new VMs, for example with Azure Backup on Azure. Power off the old hosts, wait out the agreed period, then retire hosts and storage. The renewal then covers only what is left.

  • Output: retired hosts and a smaller renewal.
  • Owner: the infrastructure lead.
  • Done when: no live workload runs on a host you plan to retire.
Cutover checks for a VMware move: freeze the source, name a rollback owner, get sign-off and keep the source VM until then
A way back is part of the cutover.

Five Mistakes When You Migrate VMware to the Cloud

Five mistakes repeat across moves. Each one has a cause, but the fix is short.

  1. Moving hosts instead of applications. Group by application.
  2. Choosing the region after replication starts. Decide it in Step 4.
  3. Having no rollback owner. Name one in Step 9.
  4. Leaving the source VMs running and changing them after cutover. Freeze the source.
  5. Renewing for hosts that you will switch off. Plan Step 10 before you sign.

Key Takeaway Group by application, fix the region early, name a rollback owner and freeze the source.

Before You Migrate VMware to the Cloud: Strategy, Readiness and Path Choice

Three questions sit outside this guide.

Pricing stays out of this guide.

For this work Signisys offers our AWS and Azure migration solution and cloud platform engineering services, and it works with AWS and Microsoft. A working session covers your VM list, routes and wave plan, with no promised result and no price. No charge, with a fixed scope.

Book a consultation
Plan your VMware waves with us

How to Migrate VMware to Cloud: FAQ

Do VMs keep their IP addresses after the move?

On the relocate route, ask the provider whether an HCX network extension keeps them for your VMs. On rehost to cloud VMs, plan new addresses or ask the provider. We make no promise here.

How long should we keep the source VMs after cutover?

Until the application owner signs off. Set the rollback owner and date in Step 9.

Who should sign off each wave?

The application owner and the infrastructure lead, with the security owner for data location. Signisys’s working view is that two signatures beat one, because the second reader catches what the first assumed.

Does rehosting to cloud VMs end the VMware renewal?

It ends only for hosts you switch off, so the renewal covers what remains. See Step 10.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.