Modernize your virtual infrastructure! We explain how to migrate from the open source XCP-ng platform to the industry standard VMware ESXi in all its technical details, without any data loss. A step-by-step guide with 2026's latest virtualization technologies and migration tools.
XCP-ng (Xen Cloud Platform - next gen) is a great open source project based on Citrix Hypervisor. However, enterprise scalability 3. when it comes to party software support (Veeam, Zerto, etc.) and broad hardware compatibility VMware ESXi remains the industry leader. As of 2026 , ESXi is indispensable for businesses looking for performance and stability, despite the changing licensing models after VMware's acquisition by Broadcom.
In this guide, we will examine three different ways to move your virtual machines (Linux and Windows) on XCP-ng to the VMware environment while preserving data integrity.
Do you need a powerful physical server to migrate to?
Get Transportation ServiceVirtual machine migration is a risky process. Before you begin, be sure to complete the following steps:
Take a snapshot of VMs on XCP-ng or professional backup service Make a backup to an external area using .
"Xen Tools" or "Citrix Guest Tools" software in the VM be sure to remove it. These drivers may cause kernel panic or blue screen on ESXi.
Depending on your situation, you can choose one of the following 3 methods:
If you are not using Xen Orchestra or if it is faster to operate via CLI, you can export the VM by connecting to your XCP-ng server via SSH.
First, we need to find the identification number (UUID) of the virtual machine you want to move.
We will export the VM as a file. This process may take time depending on the size of the disk.
XCP-ng's `.xva` format is not directly recognized by VMware. To convert this file XenConvert or xva-img You can use the tool. However, the most practical way is to use the "Export to OVF" option directly via Xen Orchestra. If you do not have this opportunity, we will convert the disk to RAW format and use `qemu-img`.
If you don't want to deal with complex commands, Windows-based StarWind V2V Converter The tool is a life saver. This tool can connect to a running XCP-ng server and “stream” the VM directly to the VMware ESXi server.
If your virtual machine is running (Powered On) and you cannot shut it down, you can migrate it by acting as a "Linux/Windows Physical Machine" using VMware's own tool.
Install VMware Converter inside the VM or run it from a Windows machine on the network. Select "Powered on remote machine" as the source and give the IP address of the VM on XCP-ng. Show your ESXi server as the target. This method copies at the operating system level.
If you moved a Linux VM and are getting the "dracut" error at startup, the initramfs may need to be refreshed. Open it in Rescue mode and follow these commands:
Since the MAC addresses from XCP-ng will change, new names such as `ens192` may appear instead of `eth0` in Linux. Update the network settings to the new interface name under `/etc/netplan/` (Ubuntu) or `/etc/sysconfig/network-scripts/` (RHEL/CentOS).
Your Windows servers may need to be reactivated because the hardware IDs have changed. Have your license key ready.
Curious technical details about XCP-ng and ESXi migration.
You cannot move it directly. The snapshot chain is specific to the XCP-ng file system. Before moving, you need to consolidate all snapshots or move only the final version.
Yes, it is essential for performance and management. When you open the VM on ESXi after the migration, your first job should be to install VMware Tools (or open-vm-tools for Linux). This optimizes network and disk performance.
For security and performance updates as of 2026 ESXi 8.0 Update 3 or a newer version is recommended. If you have old hardware, you should check the compatibility list (HCL).
This depends on your data size and network speed. A VM of 100GB is transferred on average in 20-30 minutes over a 1Gbps network. When using tools like StarWind V2V, processing time depends on disk I/O speed.