Migrating from VMware to Proxmox: Effortless Migration with the Import Wizard

Is Broadcom Pushing Us Toward Proxmox?

Ever since Broadcom changed its licensing policies, the IT community has seen a massive shift toward open-source platforms. Proxmox VE has emerged as the top contender. In the past, migrating a virtual machine (VM) from ESXi to Proxmox was a grueling journey. You had to export the OVF, use qemu-img to convert the disk, and then manually recreate the VM.

But that’s a thing of the past. With the Proxmox Import Wizard introduced in version 8.2, everything is now just a few clicks away. I’ve been putting this feature through its paces for the past 6 months across both production clusters and a 12-node homelab. The result? A 100GB Linux VM took less than 15 minutes to ‘move house’ and run perfectly. Here is the standard procedure for a smooth transition.

Quick Start: Successful Migration in 5 Minutes

If you’re in a hurry, follow these steps. Prerequisite: Proxmox VE version 8.2 or higher. If you’re on 8.1, remember to fully update your packages.

Step 1: Connect Directly to ESXi

1. In the Proxmox interface, go to Datacenter > Storage > Add > ESXi.
2. Enter the following parameters:
   • ID: Use an easy-to-remember name like ESXi_Source.
   • Server: The IP address of your target ESXi host.
   • Username/Password: Use the root account for simplicity.
   • Skip Certificate Verification: Check this box since most of us use self-signed certificates.

Step 2: Click and Wait

1. On the left sidebar, click on the ESXi storage you just added.
2. A list of VMs will appear. Select the VM you want to move and click Import.
3. Choose the target storage (Local-LVM or Ceph) and click OK. That’s it!

# Check if the system is ready
pveversion -v | grep esxi-import

Why is this method superior to the old way?

The Import Wizard doesn’t use intermediate tools like Clonezilla. It communicates directly with the VMware API via the HTTPS/VADP protocol.

The most valuable feature is Live Stream data migration. Proxmox downloads and converts the disk format (vmdk to raw/qcow2) in real-time. You don’t need a buffer drive to store temporary files. This method saves 50% of your time and 100% of intermediate storage space.

Fixing Blue Screen of Death (BSOD) on Windows

Linux VMs usually recognize VirtIO drivers immediately. With Windows, you might encounter a blue screen if drivers are missing. My secret: Always keep the virtio-win ISO file ready on your host.

# Quickly download the standard VirtIO drivers
wget https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso -P /var/lib/vz/template/iso/

Optimizing Configuration for Better Performance

Don’t stick with the default configuration. Tweak these three settings to boost performance:

1. CPU Type: Switch to ‘Host’

The default is kvm64 for easier migration between nodes with different CPU generations. If you’re running a single node, choose host. This allows the VM to use the full instruction set of the physical CPU, resulting in a noticeable performance gain of about 10-12%.

2. Network Card: Always use VirtIO

When importing, make sure to select the VirtIO (paravirtualized) network model. If Windows doesn’t detect the network, just mount the VirtIO ISO and update the drivers in Device Manager.

3. Enable Discard for SSDs

If you’re using SSD/NVMe, check the Discard option in the Disk section. This helps Proxmox reclaim free space when you delete files inside the VM, preventing the virtual disk from appearing full unnecessarily.

3 Crucial Lessons to Avoid Data Loss

After migrating dozens of systems, I’ve gathered a few practical tips:

• Delete Snapshots First: This is a mistake 90% of people make. Snapshots fragment data and can cause checksum errors during import. Commit all snapshots on the ESXi side beforehand.
• Prioritize Cold Migration: Although Proxmox allows importing running machines, I still recommend shutting down the VM. Migrating a live machine can cause database errors if applications are constantly writing data.
• Double-check UEFI/BIOS: The VM must use the same boot standard in Proxmox as it did in ESXi. If ESXi used UEFI, select OVMF (UEFI) and remember to add a small EFI Disk, otherwise the machine won’t boot.

In reality, the Import Wizard has been a total game-changer. No more late nights typing manual commands, and no more worrying about data discrepancies during conversion. Proxmox has done an excellent job of listening to its users.

Have you tried moving any of your systems yet? If you have any questions about Proxmox Backup Server (PBS) after migrating, feel free to leave a comment. Happy migrating!