Who built this, and why

Every VMware migration starts the same way: someone runs RVTools, exports twenty-odd spreadsheet tabs, and starts reading. The data is accurate and complete. It just doesn’t tell you anything on its own.

Somebody has to know that Raw Comp. Mode = physicalin the vDisk tab means that VM cannot be migrated by any automated tool. That a Linux guest on VMXNET3 will boot with a renamed interface and no address on it. That a snapshot chain four deep is a consolidation job before it is a migration job. That knowledge lives in a handful of engineers, and it gets applied by hand, VM by VM, at somewhere between $300 and $3,000 per VM in consulting time.

Gartner puts initial scoping alone at seven to ten full-time staff for a month on a mid-sized estate. That is the part that should not be manual.

It is the decision layer, not the execution layer. 48 rules encoding the migration blockers, network identity traps and capacity arithmetic that experienced engineers check for, applied to your RVTools export in the time it takes to read this paragraph.

It does not move VMs. Nutanix Move, Microsoft’s VM Conversion extension and Proxmox’s importer already do that, and they are free. PolyVirt tells you which VMs should go where, in what order, at what risk, and what it will cost — including the case where the answer is that staying put is cheaper.

Early. The analyzer is in final testing and the rule library is being published one rule at a time at /checks. We have no customers yet, so you won’t find testimonials or logos on this site — inventing them for an audience that would see straight through it seemed like a poor start.

If you are planning a migration and want to talk to whoever is building this, hello@polyvirt.com reaches us directly.