We're retiring most of our VMware environment while migrating on-premises applications to SaaS. A few older applications have no replacement and may need to remain available for legal or records-retention requests for the next several years. Some of these systems are difficult to rebuild because the vendors no longer exist, installers and activation codes are missing, or the software contains custom code.
The environment consists of three relatively light virtual machines, each using about four vCPUs and 4 GB of RAM. I'm considering converting the VMDKs to VHDX files, storing them on a Windows 11 Pro laptop with a Core Ultra 7 processor, and powering them on only if access is ever required. The current VMware hosts use dual Xeon E5-2620 v4 processors.
Would it be better to archive the VMs in their original format, export them as OVF/OVA, use a backup product, or migrate them to Hyper-V? I'm also interested in recommendations for reliable long-term storage and ways to ensure the systems can still be recovered years from now.
5 Answers
I’d avoid treating a single laptop as the archive. Keep the VM files or proper image-based backups in several independent locations, such as two types of storage plus an offline copy. USB drives can work for a short retention period, but they should be checked periodically and replaced as they age.
For legal retention, document what was archived, the date, the source system, required credentials and licenses, and the steps needed to restore it. Also perform a test restore before decommissioning the original environment.
If you do move the machines to Hyper-V, use a supported conversion tool such as StarWind V2V Converter and test every guest afterward. Check application startup, network settings, time synchronization, licensing, database consistency, and any required domain services.
Also verify the licensing implications of the Windows host and any virtualization software. For occasional access, a documented restore process may be cheaper and more dependable than leaving a dedicated host powered down on a shelf.
A backup is usually a better archive than manually converting every disk. Veeam or another image-based backup platform can preserve the entire VM and often supports restoring it to a different hypervisor later. You can also browse the backup or recover individual files without keeping VMware running.
If you want maximum portability, retain the original VMDKs as well as an OVF or OVA export. That gives you a recovery path if a future hypervisor handles one format better than another.
You may not need to convert them at all. VMware Workstation can often open ESXi-created VMDKs, so keeping the original disks on a NAS or external storage may be the simplest emergency-access option. OVF exports are another good choice because they can generally be imported into Hyper-V, Proxmox, or other virtualization platforms.
Before switching hypervisors, remove VMware Tools if possible and record the VM configuration. Older Windows guests can have driver or boot problems after conversion, and VMware Tools has occasionally caused trouble when removed after the migration.
Think about the storage as an archival system rather than just a VM migration. Keep multiple copies in separate secure locations, include checksums or periodic integrity checks, and maintain at least one offline copy. LTO tape is worth considering if the retention period is long and the data volume justifies it; archival tape can remain readable for decades when stored properly.
A laptop can be useful as a temporary recovery host, but it should not be the only copy. Hardware, batteries, storage media, and operating-system compatibility can all become problems over several years.
The important part is testing the restore while you still have access to the original systems. A backup that has never been restored is only an assumption, especially with old operating systems and application dependencies.