We have about 25 older virtual machines, including Windows Server 2003 and Windows XP, that need to be moved off our VMware environment. What migration or hosting options should we consider, and are there practical ways to keep these systems running while we modernize or replace them?
3 Answers
It is possible to get Windows Server 2003 running in Azure as a proof of concept by converting the VM to Hyper-V locally, installing the necessary client tools, and uploading the resulting VHD to a storage account. However, this is not a supported production configuration. Running an old hypervisor or VMware Workstation inside another VM is technically conceivable, but Microsoft would not support troubleshooting failures involving those legacy operating systems.
Azure VMware Solution would probably be the simplest migration path because the existing VMware workloads could move with fewer changes, but it is likely expensive and excessive for only 25 VMs. Nutanix on Azure (NC2) is another possibility and includes tooling that may help with migration. Moving directly to Azure VMs is also an option, although the guests would need to be upgraded to supported operating systems.
The right choice depends heavily on what these VMs actually do. Some may be candidates for replacement, retirement, or application modernization rather than a straight lift-and-shift.
Before choosing a platform, inventory the workloads and every operating system version hidden in the “etc.” category. Very old systems such as Windows XP or Server 2003 may have hardware, driver, licensing, networking, and application dependencies that determine whether they can run in a cloud environment at all.
Treat that approach as temporary containment only. Isolate the machines, restrict network access, take reliable backups, and create a plan to retire or replace the applications that require them.