Toil-Less

← VMware Exit Readiness Report

VMware Exit Readiness Report

by Toil-Less · Version 0.3

Find out what stands between your VMware environment and Proxmox VE or Hyper-V before you start moving anything.

One PowerShell script reads your vCenter or ESXi host and produces a clear HTML report. It rates every VM as ready, needing preparation, or blocked, and explains why. The report also lists the networks and placement rules you will have to rebuild and estimates how long copying the data will take. A short summary at the top can go straight to your manager.


Read-only by design

The script never changes anything in your environment. It only reads configuration data through VMware PowerCLI.

  • It runs safely against production with a read-only vCenter account.
  • No data leaves your network. The script makes no internet connections and collects no telemetry. The report is a local HTML file.

What you get

File Contents
MigrationReadiness_<date>.html The report: a plain-language summary, key figures, ratings per VM, findings, networks and placement rules. It is a single file that opens in any browser and can be emailed or printed.
MigrationReadiness_<date>.csv Every VM with all collected data and findings, for Excel or your own tooling.

Each VM gets three ratings:

Column Question it answers
Proxmox Can this VM move to Proxmox VE?
Hyper-V Can this VM move to Hyper-V?
Veeam Will a Veeam backup capture this VM completely, so a backup-and-restore migration is possible?
Rating Meaning
🟢 Green No known blockers.
🟡 Yellow Preparation needed before migration.
🔴 Red Blocker. This VM needs its own plan.
⚪ Skip VMware infrastructure (vCenter, vCLS, other VMware appliances). It is retired together with vSphere, not migrated.
Info Good to know. Does not affect the rating.

What it checks

Blockers (Red)

  • Physical-mode RDMs. These cannot be converted to a virtual disk and are not included in Veeam image backups.
  • Shared multi-writer disks, typical of guest clusters. These need a redesign on the target.
  • PCI and GPU passthrough devices.
  • Encrypted VMs (vSphere VM Encryption). These must be decrypted first.
  • Fault Tolerance, which has no direct equivalent on Proxmox or Hyper-V.
  • Independent disks. Veeam does not back these up, so the Veeam rating is Red.

Preparation needed (Yellow)

  • Snapshots, with their age. Consolidate them before migrating.
  • Independent disks, which are excluded from snapshots.
  • Virtual-mode RDMs. These become regular virtual disks, so check the storage capacity on the target.
  • Disks larger than 2 TB. These need a long copy time, so plan a separate window.
  • USB devices, such as licence dongles.
  • Serial and parallel ports.
  • vTPM. TPM contents do not migrate, so have your BitLocker recovery keys ready.
  • Mounted ISO images.
  • Memory limits below the configured RAM. This is usually a leftover misconfiguration that should not be carried over.
  • Operating systems out of vendor support, or ending within 12 months. These are candidates for replacement rather than migration.
  • VMware Tools missing, or installed but not running.
  • Generic guest OS types ("Other Linux") where the real operating system is unknown.
  • Outdated VMware Tools. Application-aware Veeam backups may fail, so this affects the Veeam rating.

Good to know (Info)

  • Emulated network cards (E1000/E1000e), which are replaced on the target.
  • Windows guests: install VirtIO drivers before moving to Proxmox, document static IP settings, and uninstall VMware Tools before migrating, because removing them afterwards is often difficult.
  • BIOS firmware: these VMs become Generation 1 VMs on Hyper-V and use SeaBIOS on Proxmox.
  • CPU and memory reservations and CPU limits.
  • DRS rules (keep together, keep apart, VM-to-host) that need equivalent rules on the target.
  • CBT status for Veeam.

Inventory sections

  • Networks to recreate: every port group in use, its VLAN, and which VMs depend on it. The report warns when a port group has different VLANs on different hosts.
  • Placement rules to recreate: all DRS rules per cluster.
  • Per VM: guest OS (the exact distribution and version where vSphere provides it), hostname, IP addresses, CPU, RAM, used and provisioned storage, firmware, Secure Boot, hardware version and estimated copy time.

Requirements

  • Windows PowerShell 5.1 or PowerShell 7.x
  • VMware PowerCLI. Install it once with: powershell Install-Module VMware.PowerCLI -Scope CurrentUser Newer releases are also published as VCF.PowerCLI. Either works.
  • vCenter Server or a standalone ESXi host. Developed and tested on vSphere 8.0. DRS rules are only available through vCenter.
  • A read-only account. The built-in Read-only role is sufficient.

Quick start

  1. Unzip the package to a folder, for example C:\Tools\ExitReadiness.
  2. Windows blocks scripts downloaded from the internet. Unblock it once: powershell cd C:\Tools\ExitReadiness Unblock-File .\Get-MigrationReadiness.ps1
  3. Connect to vCenter: powershell Connect-VIServer vcenter.example.local
  4. Run the report: powershell .\Get-MigrationReadiness.ps1 -OutputFolder C:\Reports -Open

The HTML report opens in your browser when the script finishes.

Tip: Run the report with your VMs powered on. Hostnames, IP addresses and exact OS versions come from VMware Tools, which only reports them while a VM is running.


Parameters

Parameter Default Description
-OutputFolder Current folder Where the HTML and CSV files are written. The folder is created if it does not exist.
-VMName * (all VMs) Name filter, wildcards allowed. Example: -VMName 'SQL*'
-LinkGbps 1 Network speed for the copy-time estimate, in Gbit/s. Example: -LinkGbps 10
-Open off Opens the HTML report when finished.

Examples:

# Whole environment, 10 Gbit/s migration network
.\Get-MigrationReadiness.ps1 -OutputFolder C:\Reports -LinkGbps 10 -Open

# Only the SQL servers
.\Get-MigrationReadiness.ps1 -VMName 'SQL*' -OutputFolder C:\Reports

Limits: what the report does not do

The report is a planning tool. Before relying on it, keep these limits in mind:

  • It does not migrate anything. It tells you what to prepare. The migration itself is done with your tools of choice, such as the Proxmox import wizard, Veeam restore or Microsoft's migration tools.
  • It does not look inside the guest. Application dependencies, software licences tied to hardware IDs, and in-guest configuration are outside its view.
  • Copy times are pure transfer estimates. They assume 70% of the given link speed and count used storage only. Testing, cut-over and downtime are not included.
  • Exact Linux versions need vSphere 7.0 U1 or later with current VMware Tools or open-vm-tools in the guest. Otherwise the report shows the OS family, such as "Ubuntu Linux (64-bit)".
  • OS support dates are the vendors' end-of-support dates as of this version. Paid extensions such as Microsoft ESU may still be available.
  • Powered-off VMs are analysed from their configuration only.

Troubleshooting

Message Cause and fix
Not connected to vCenter/ESXi Run Connect-VIServer <server> first, in the same PowerShell window.
... is not recognized as the name of a cmdlet You are not in the script's folder, or the file was renamed when you downloaded it, for example to Get-MigrationReadiness (1).ps1. Check with Get-ChildItem *.ps1.
... cannot be loaded ... not digitally signed Run Unblock-File .\Get-MigrationReadiness.ps1, or start PowerShell with -ExecutionPolicy Bypass for this session.
A VM shows no hostname or IP VMware Tools is not installed or not running in that VM, or the VM is powered off. The report flags this.
Your vCenter shows a rating instead of Skip Please report it, ideally with the VM's guest OS line from the report.

Support

Email: [email protected]

When reporting a problem, please include: - the PowerShell version ($PSVersionTable.PSVersion) - the PowerCLI version (Get-Module VMware.* -ListAvailable | Select Name, Version) - your vSphere version - the full error message

Please do not send the report itself unless you have removed internal names and IP addresses.


Licence

Each purchase includes a licence: Standard covers one organisation with any number of vCenters, hosts and VMs; Service Provider allows use in any number of customer environments. Updates for the current major version are included. The full terms are in LICENSE.txt in the download.


Changelog

0.3 - Plain-language summary for decision-makers - Operating system end-of-support check - Copy-time estimate per VM and in total (-LinkGbps) - Networks to recreate, with a warning for VLANs that differ between hosts - DRS rules, reservations, limits, and memory limits below configured RAM - Disks larger than 2 TB - Hostnames and IP addresses from VMware Tools, plus exact OS versions where available - VMware infrastructure (vCenter, vCLS, Photon OS appliances) detected and excluded from ratings, sizing and copy time - Warning when VMware Tools is installed but not running

0.2 - Emulated network cards reduced from Yellow to Info

0.1 - First version: per-VM ratings for Proxmox VE, Hyper-V and Veeam; HTML and CSV output


VMware, vSphere, vCenter and ESXi are trademarks of Broadcom Inc. Proxmox is a trademark of Proxmox Server Solutions GmbH. Hyper-V is a trademark of Microsoft Corporation. Veeam is a trademark of Veeam Software. Toil-Less is an independent product and is not affiliated with or endorsed by any of these companies.