VMware Exit Readiness Report
See what blocks your VMware exit before you move a single VM.
One read-only PowerShell script checks every VM in vCenter and rates it for Proxmox VE, Hyper-V and a Veeam restore. You get the blockers, the preparation work, the networks to rebuild and a copy-time estimate in one HTML report.
| VM | Proxmox | Hyper-V | Veeam |
|---|---|---|---|
| SQL01Windows Server 2019Physical-mode RDM: cannot be converted, not in Veeam backups | Red | Red | Red |
| ERP-APPWindows Server 2012 R2USB licence dongle, 47-day-old snapshot, OS out of support | Yellow | Yellow | Yellow |
| WEB02Ubuntu 24.04.3 LTSNo known blockers | Green | Green | Green |
| vcsa01VMware Photon OSvCenter appliance, retired with vSphere | Skip | Skip | Skip |
What it checks
The things that turn a weekend migration into a month.
Each finding says what it is, which target it affects and what to do about it. Info notes never change a rating, so the colours stay meaningful.
Needs its own plan
- Physical-mode RDMs
- Shared multi-writer disks from guest clusters
- PCI and GPU passthrough
- VM encryption and Fault Tolerance
- Independent disks that Veeam skips
Fix before you move
- Snapshots, with their age
- USB dongles, serial ports, mounted ISOs
- vTPM and the BitLocker keys it implies
- Memory limits below the configured RAM
- Operating systems out of vendor support
- VMware Tools missing or not running
Rebuild on the target
- Port groups and VLANs, with a warning when a VLAN differs between hosts
- DRS affinity, anti-affinity and VM-to-host rules
- Reservations and limits
- Hostnames and IP addresses per VM
- vCPU, memory and storage to provide
For the meeting
A summary your manager can read.
The report opens with a few plain sentences: how many VMs are ready, what blocks the rest and how long the data copy takes. The table and the details sit underneath for the people who do the work.
10 VMs analysed for migration, using 2716 GB of storage. For Proxmox VE: 1 can move without preparation, 8 need preparation and 1 has blockers that need a plan. 4 VMs run an operating system that is out of vendor support or will be within 12 months. 2 VMs have disks that Veeam does not back up. Copying all data takes roughly 8.6 h at 1 Gbit/s.
How it works
Three commands, a few minutes.
Install PowerCLI once
If you manage vSphere from PowerShell, you probably have it already.
Install-Module VMware.PowerCLI -Scope CurrentUser
Connect read-only
Use an account with the built-in Read-only role.
Connect-VIServer vcenter.example.local
Run the report
Set your migration link speed for the copy-time estimate.
.\Get-MigrationReadiness.ps1 -LinkGbps 10 -Open
Pricing
Pay once. Run it as often as you like.
For your own organisation.
- Unlimited vCenters, hosts and VMs in one organisation
- Free updates for the current major version
- Support by email
For consultants and MSPs who run it at customers.
- Use for any number of customer environments
- Free updates for the current major version
- Support by email
Prices include VAT where applicable. Checkout is handled by our payment provider, which also issues the invoice. You get a ZIP with the script, documentation and an example report.
Questions
Before you buy
Does it change anything in vCenter?
No. It only reads configuration data. You can run it with a read-only account and check the code yourself, since it is plain PowerShell.
Does it send data anywhere?
No. The script makes no internet connections. The report is a local HTML file that only you decide to share.
Which vSphere versions work?
It was developed and tested on vSphere 8.0. It needs vCenter for DRS rules; a standalone ESXi host works for everything else.
Does it migrate my VMs?
No. It tells you what to prepare. The move itself happens with the Proxmox import wizard, a Veeam restore or Microsoft's tools.
Why are exact Linux versions sometimes missing?
They come from VMware Tools. The VM must be running, with open-vm-tools installed, on vSphere 7.0 U1 or later.
What does the Veeam column mean?
Whether a Veeam image backup captures the whole VM, so restoring it onto Proxmox or Hyper-V is a realistic migration path.