Turn your RVTools export into an exit assessment
Every VMware exit starts with the same spreadsheet. Drop it here and get what a consultant would bill a discovery week for: your real licensing core count, estate totals, and the specific VMs that will fight the migration, RDMs, fault tolerance, USB dongles, shared-bus disks, open snapshots.
Privacy, in plain words: the file is parsed by JavaScript running in this tab. There is no upload, no server, no analytics event carrying its contents, and nothing persists after you close the page. This page works identically if you load it, disconnect from the network, then drop the file.
What the analyzer checks
RVTools (a free utility by Rob de Veij, effectively the industry standard for vSphere inventory) exports your estate as an .xlsx workbook. The analyzer reads the vInfo, vHost, vDisk, vSnapshot, vUSB, and vCD tabs and looks for the things that decide migration difficulty in practice:
- Licensing exposure. Total physical cores across hosts, the number vSphere's per-core subscriptions actually bill, pre-counted for the cost calculator.
- Hard blockers. Raw device mappings, shared-bus disks, and Fault Tolerance, the configurations no V2V conversion handles for you.
- Friction items. USB passthrough, independent-mode disks, open snapshot chains, and monster VMs that dominate cutover windows.
- Free wins. Powered-off VMs and mounted ISOs, scope you can delete from the project before it starts.
The output is a prioritized blocker list with affected VM names and a downloadable assessment you can paste into your migration planning doc. Pair it with the renewal planner to see whether the cleaned-up scope still fits before your renewal date, and with the per-path guides (Proxmox, XCP-ng, Hyper-V, Nutanix AHV, OpenStack) for the execution detail.
Limitations, honestly: the analyzer reads what RVTools captures. It cannot see application-level dependencies, backup-job coupling, or network micro-segmentation (NSX), those still need human discovery, and the guides cover how. vGPU and SR-IOV passthrough do not appear reliably in RVTools exports, check those by hand in vCenter.