VMware Migration Requirements: What to Look For in a VMware Alternative
StorageSwiss, Monday, October 19th, 2026
Five migration capabilities to demand from a VMware alternative so that cutover shrinks to little more than a reboot.
George Crump argues the ideal VMware migration reduces cutover to powering off a VM on VMware and powering it on under the new platform.
Teams should plan by workload, meaning groups of interrelated VMs, applications and data, rather than individual VMs.
He lists five requirements: initial data seeding of live VMs without interrupting production and as fast as VMware allows; maintaining the copied VMware state so a failed test does not force a reseed; multi-tenancy to isolate and clone workloads for parallel testing; incremental updates before final cutover; and independent snapshots for rollback without chain dependencies.