VMware Conversion to Hyper-V
Due to a substantial and unsustainable increase in VMware license costs, Duke OIT will transition away from VMware as our primary virtualization platform starting in early September and concluding by April 1, 2026.
What You Need to Know
Transition Plan: Before April 1st, 2026, all virtual machines will be converted to Hyper-V. The functionality to convert VMs is currently available in Clockworks. A list of VMs that you own can be found here, and a list of VMs that your team owns can be found here. VM owners are able to work with Systems teams to schedule conversions, opt in to automated conversion windows, or create new Hyper-V VMs to migrate their existing VMs to. The conversions will occur during normal business hours and will involve some downtime. Please see links below for OS specific conversion information.
Exceptions: Virtual machines with documented requirements for VMware (due to dependencies or compatibility issues) may be exempt but first will need to be evaluated on a case-by-case basis in coordination with OIT. These dependencies or compatibility issues need to be determined ASAP so that proper planning can take place. NOTE: Any VMs that need to stay on VMware will incur a very significant increase in hosting charges.
We are committed to providing the support and resources needed for a smooth migration, working with support teams in advance to identify and work around critical business (administrative and academic) activities in scheduling the upgrades.
If you have any questions, please reach out to the OIT Virtualization team at ssi-vmware-admins@duke.edu.
Links
Preparing a Linux VM for Conversion from VMware to Hyper-V
Preparing a Windows VM for Conversion from VMware to Hyper-V
Article number: KB0038848
Valid to: December 4, 2026