This VMware migration checklist has 13 checks on the estate, dates, target, plan and people. Each scores 0, 1 or 2 against evidence. A high total with no zero on the four blocker checks means you can book the pilot wave.
Last reviewed 2026-11-16 by Manish Sharma.
The scope is VMware workloads moving to AWS or Azure, so facility work and single applications sit elsewhere. We last checked the three cited pages on 16 November 2026. Think of this as a VMware to cloud checklist for readiness. It asks what you can show, instead of what you believe. VMware migration readiness is a state you can score on a given day. Also, readiness work on a VMware estate with us is a service we offer.
VMware Migration Checklist: How to Score Each Check
Every check gets one number from 0 to 2, and the number depends on what a second person can open.
| Score | Meaning | What a second person can see |
|---|---|---|
| 0 | Not started, or unknown | Nothing |
| 1 | In progress | A statement or a draft that nobody can open |
| 2 | Evidence on file | An export, a diagram or a signed test |
The maximum is 26 points. Signisys’s working view is a pass mark of 22 of 26. It also sets no 0 on four named checks: 3, 5, 9 and 12. Call these the blockers. We set the mark by asking which gaps stop a wave from starting, and these four do.

An export, a diagram or a signed test earns a 2. A statement that nobody can open earns a 1 at best.
The Estate Part of the VMware Migration Checklist: VMs, Owners and Links
Four checks cover what you run today and how it connects, before any move.
Check 1: Every VM Listed With an Owner
Export an inventory from vCenter that lists, for every VM, the power state, operating system, size, application and owner. Azure Migrate’s discovery needs a vCenter read-only account. Microsoft Learn’s guide to discovering servers in a VMware environment (page dated 12 May 2025) says so. If you use another tool, ask its maker which account it needs.
- Score 2 if you have an export and an owner named for every VM.
- Score 1 if the export has owners missing for some VMs.
- Owner: the infrastructure lead.
Check 2: Powered-Off and Unused VMs Tagged
Mark each powered-off or idle VM as retire or keep, with the owner’s name beside it. We give no figure for how many to expect, because that depends on your estate.
- Score 2 if the owners agree the tags.
- Score 1 if the infrastructure team alone sets the tags.
- Owner: the infrastructure lead.
Check 3: Dependencies Mapped Into Groups
Map which servers talk to which, then group them by application. Microsoft Learn’s migration planning guidance (page dated 1 August 2025) says this: dependencies between workloads cause service disruptions if you do not migrate them together. This is a blocker.
- Score 2 if every VM sits in a named group.
- Score 1 if groups exist for some applications only.
- Owner: the infrastructure lead with application owners.
Check 4: Operating System and App Support Status Known
For each VM, ask the app owner whether the operating system and the application still have support from their makers. Also ask whether they run on the target. The Azure Migrate guide cited in check 1 says its discovered-server view shows an operating system support status. The status reads mainstream support, extended support or out of support, which gives a starting list to confirm.
- Score 2 when each application has a written answer.
- Score 1 when owners answer aloud for some applications.
- Owner: application owners.
Key Takeaway Score what a second person can open, not what the team believes.
The Dates Part of the VMware Migration Checklist: Support, Renewal and Core Counts
Two checks fix the dates that shape the whole move.
Check 5: Support and Renewal Dates on Record
Know your support and renewal dates for VMware, and for hosts and storage, with the contract owner named. The reasons behind the date pressure sit in the reasons behind the new VMware renewal terms. No figures appear here: read each date and term from your own contract. This is a blocker.
- Score 2 if the dates sit in a file with a named contract owner.
- Score 1 if one person knows the dates.
- Owner: the contract owner.
Check 6: Core Counts Recorded per Host
Record a core count for each host from the inventory. Treat it as an input only, while no amounts attach to it.
- Score 2 if each host has a count from the export.
- Score 1 if only some hosts have counts.
- Owner: the infrastructure lead.
Target Checks on a VMware Migration Checklist: Landing Zone, Network and Recovery
Three checks cover the place the workloads land, before the first wave.
Check 7: Landing Zone Built and Signed Off
In this checklist, a landing zone is the base the first VM lands on: network, identity, logging and backup. All of it should be in place early. Microsoft’s guidance lists an Azure landing zone as a prerequisite of the migration plan. For AWS, ask your cloud team to show the equivalent build record.
- Score 2 if a signed build record exists.
- Score 1 if the build is under way.
- Owner: the cloud engineer.
Check 8: Network Path and IP Plan Agreed
Confirm which connection to the cloud is in place, and which VMs keep or change addresses. Microsoft Learn says to check first which network connections you have available. You need no product names to answer this.
- Score 2 if you have a diagram and an address plan.
- Score 1 if you ordered a connection but have no plan.
- Owner: the network lead.
Check 9: Backup and Recovery Tested in the Target
Run a restore in the target instead of only on premises. Microsoft Learn says moving nonproduction environments before production lets teams test configurations, performance and recovery procedures without affecting users. This is a blocker.
- Score 2 if a signed restore test exists.
- Score 1 if you have planned a restore.
- Owner: the cloud engineer.
Pick one small application and restore it in the target, so the signed test shows a result.
VMware Migration Checklist, Plan: Data Location, Paths, Waves and Rollback
Three checks cover decisions you make before the first wave.
Check 10: Data Location for India and the GCC Confirmed
Name the region for each workload and have your compliance owner sign it. This is a question for that owner, and we name no law here.
- Score 2 if each workload has a region with a signature.
- Score 1 if you chose a region with no signature.
- Owner: the compliance owner.
Check 11: A Path Chosen for Each Workload
Give each workload one word: rehost, relocate, rebuild, retire or keep. Relocate means VMware run by the cloud, such as Azure VMware Solution or Amazon Elastic VMware Service. See the ordered move, from inventory to switch-off for how to do each path. Comparing paths is set out in the kinds of alternative to compare.
- Score 2 if each workload has a path that its owner signs.
- Score 1 if only some workloads have paths.
- Owner: application owners.
Check 12: Waves and Rollback Written Down
Group servers into applications and applications into waves, as the AWS Transform MGN overview says (no page date shown). Microsoft Learn also advises you to organize large portfolios into migration waves. Write the conditions that trigger a rollback, such as CPU limits, response times or error rates, and say who decides. A VMware cloud migration with no rollback owner has no way back. This is a blocker.
- Score 2 if you have a wave plan and a rollback rule with a named decider.
- Score 1 if you drafted waves but have no rollback rule.
- Owner: the infrastructure lead.
People on the VMware Migration Checklist: Skills and the Run Team
One check covers who does the work and who keeps it running.
Check 13: Skills for the Target and a Team to Run It
Review the team’s experience with the target cloud, the migration tools and the cutover, as Microsoft Learn advises. Name who runs the workloads after the move and who is on call.
- Score 2 if a skills review is on file and a run team has names.
- Score 1 if the review happened aloud.
- Owner: the IT head.
Reading Your VMware Migration Checklist Score
Add the 13 scores, then read the total with the blockers beside it.

- If you score 22 or more, with no 0 on checks 3, 5, 9 or 12, book the pilot wave.
- Below 22, or a 0 on any blocker: fix those items first, then score again.
A 0 on check 3 means groups may split, so an application may break mid-move. A 0 on check 5 means you set the move date without the contract dates. If check 9 scores 0, nobody has tried a restore in the target. Finally, a 0 on check 12 means no way back. We give no dates here, because yours come from your own contracts.
A 0 on check 3, 5, 9 or 12 stops the pilot wave, regardless of the total.
Key Takeaway Book the pilot wave at 22 points or more, with no 0 on a blocker.
What a VMware Migration Checklist Leaves to Other Pages
This list scores VMware readiness only. The facility side is in the facility side, from racks to leases. Checks for other applications are in checks for moving legacy applications. Choosing between paths is a separate topic.
Signisys offers the related services and works with AWS and Microsoft. See our cloud migration and modernization solution for the wider offer, and cloud services and platform engineering. In a working session we score your estate against the 13 checks together. No charge, with a fixed scope.
VMware Migration Checklist: FAQ
Who should fill in the checklist?
When should the score be run again?
What record earns a full score on a check?
Do the checks differ between AWS and Azure?
Security Insights, Delivered.
Practical, vendor-neutral analysis of threats, tools, and architecture decisions.
