The VMware Shift
Broadcom’s takeover of VMware changed the landscape for HomeLabbers overnight. With the sudden death of the free ESXi license and a pivot toward expensive subscriptions, many of us are looking for a way out. Proxmox VE has become the go-to refuge. It offers enterprise-grade features like built-in backup and clustering without the licensing fees. But the big question remains: how do you move your existing VMs without spending a whole week rebuilding them?
I remember the old way of doing things. Migrating a single VM meant exporting massive OVF files, running qemu-img convert on the command line, and crossing my fingers that the network drivers wouldn’t trigger a Blue Screen of Death (BSOD). It was a tedious process that often took four or five hours per machine just to get a successful boot.
Thankfully, the Proxmox team released a significant upgrade: the native ESXi Import Wizard. This tool talks directly to your ESXi host and pulls data over the network. It handles the format conversion on the fly. If you want to keep your HomeLab flexible, mastering this tool is a massive time-saver.
Why Migrations Usually Fail
The friction comes down to how each platform handles virtual hardware. VMware relies on VMDK disk formats and specific virtual hardware like the E1000 network adapter. Proxmox is built on KVM and performs best with QCOW2 disks and VirtIO drivers.
When you move a disk file, the guest OS—whether it’s Windows 11 or Ubuntu—suddenly wakes up in a different “body.” It sees a new CPU type, a different disk controller, and a strange network card. If the OS doesn’t have the right drivers pre-installed, it can’t find its own boot drive. This hardware mismatch causes about 90% of migration failures.
Comparing Your Options
Before the wizard arrived, we had two main paths. Here is how they compare to the modern method:
- Manual CLI Conversion: This involves using
qemu-imgto change VMDK to QCOW2. While reliable, it is incredibly slow. Converting a 500GB disk can take over an hour depending on your storage speed. - OVF/OVA Export: You export the VM from VMware and import it into Proxmox. This often breaks because of version mismatches in the XML descriptor file.
- The Proxmox Import Wizard: This is now the gold standard. It treats your ESXi host like a storage backend. You simply browse your VMs from the Proxmox GUI and click “Import.” The system automates the disk conversion and maps the hardware settings for you.
Using the Proxmox Import Wizard
You need Proxmox VE 8.2 or later to use this feature. This version includes the pve-esxi-import-tools by default. Follow this workflow for a smooth transition.
Step 1: Prepare the ESXi Host
You don’t need a vCenter server; a standalone ESXi host (version 6.7 to 8.0) works fine. Enable SSH on your ESXi host, even though the wizard primarily uses the API. Most importantly, shut down the VM you want to move. If the VM is running, Proxmox cannot get a clean lock on the VMDK file, leading to data corruption.
Step 2: Connect Proxmox to ESXi
Open your Proxmox web interface and head to the Datacenter view:
- Go to Datacenter > Storage > Add > ESXi.
- ID: Name it something clear, like
ESXi_Main. - Server: Enter your ESXi IP address.
- Credentials: Use your ESXi root login.
- Skip Certificate Verification: Check this if you haven’t installed custom SSL certificates on your ESXi host.
After you click add, your ESXi host will appear in the sidebar just like any other storage volume.
Step 3: Run the Import
Select the new ESXi storage entry in the sidebar. You will see a list of every VM on that host. Choose your target VM and click Import at the top of the screen.
A configuration box will pop up. This is where you map the old VMware environment to Proxmox:
- Target Storage: Choose your Proxmox ZFS pool or local-lvm.
- Network: Map the VMware Port Group to a Proxmox Bridge, usually
vmbr0. - Format: Use
QCOW2if you want to use snapshots later.
# If the ESXi option is missing, run a quick update
apt update && apt install pve-esxi-import-tools -yStep 4: Fix the Hardware Mismatch
Don’t start the VM immediately after the import finishes. We still need to address the driver issue. A Windows VM will likely fail to boot because it lacks VirtIO drivers for the Proxmox disk controller.
I usually set the SCSI Controller to “VMware PVSCSI” for the first boot if that’s what the original VM used. Alternatively, set the disk to IDE or SATA just to get into the OS. Once you are logged in, install the virtio-win drivers. After the drivers are active, you can switch the controller to “VirtIO SCSI” for much better performance.
Linux VMs are usually easier. The kernel typically includes VirtIO drivers. You might only need to update your network config if the interface name changes from ens192 to something like enp0s1.
Common Troubleshooting
Even with a streamlined tool, you might hit a few speed bumps. Here is how to handle them:
The “Locked Disk” Error
If the import fails instantly, check if a backup tool like Veeam or Synology Active Backup is currently running. These tools create snapshots that lock the VMDK files. Delete any stray snapshots in ESXi before trying again.
Slow Transfer Speeds
The transfer happens over your management network. On a standard 1Gbps link, expect a maximum transfer rate of about 112 MB/s. If you are moving a 1TB database, it will take roughly two and a half hours. If speeds are slower, check if your Proxmox CPU is maxing out on compression tasks.
Windows Activation
Moving a VM changes its virtual hardware ID. Windows will likely detect this as a “new computer” and ask for re-activation. Keep your license keys handy, especially for Windows Server instances.
Wrapping Up
The Proxmox Import Wizard has removed the biggest hurdle to leaving the VMware ecosystem. It turns a complex command-line chore into a few clicks. This allows you to focus on running your services rather than fighting with disk formats. By following this structured path, you can migrate an entire HomeLab to Proxmox in a single evening. It is a vital skill now that the virtualization market is shifting so rapidly.
