How to Migrate from VMware to Proxmox VE: Step-by-Step Guide

Planning Your VMware to Proxmox Migration

Migrating from VMware to Proxmox VE is one of the most common infrastructure transitions happening in 2026. Whether driven by Broadcom's licensing changes, cost reduction goals, or a desire to move to open-source, the migration process is well-understood and manageable with proper planning. This guide walks through the complete process from export to production.

Before You Start: Pre-Migration Checklist

Before touching any VMs, complete these preparation steps:

• Inventory your VMs: Document every VM's OS, resource allocation (CPU, RAM, disk), network configuration, and any special requirements (GPU passthrough, USB devices, serial ports).
• Identify dependencies: Map VM-to-VM dependencies, shared storage mounts, and external service connections.
• Install Proxmox VE: Have your target Proxmox environment ready with storage configured (ZFS, LVM-thin, or your chosen backend) and networking set up.
• Download VirtIO drivers: For Windows VMs, download the latest VirtIO ISO from the Proxmox website. You will need these for optimal disk and network performance.
• Plan maintenance windows: Each VM will have downtime during migration. For critical systems, plan accordingly.

Method 1: OVF/OVA Export and Import

This is the cleanest migration path and works well for most VMs.

Step 1: Export from VMware

In the vSphere Client, right-click the VM and select Export OVF Template. Choose the OVF format (multiple files) rather than OVA (single archive) if the VM has large disks, as OVF allows for easier troubleshooting. Power off the VM before exporting to ensure data consistency.

# If using ovftool from the command line:
ovftool vi://vcenter.example.com/Datacenter/vm/MyVM /export/MyVM.ovf

Step 2: Transfer Files to Proxmox

Copy the exported OVF and VMDK files to your Proxmox host using SCP or rsync:

scp -r /export/MyVM/ root@proxmox-host:/tmp/imports/

Step 3: Import Using qm importovf

On the Proxmox host, use the qm importovf command to create a new VM from the OVF file:

# Create VM with ID 200 from the OVF file, storing disks on local-lvm
qm importovf 200 /tmp/imports/MyVM/MyVM.ovf local-lvm

This command creates the VM configuration and imports the virtual disks. Review the resulting VM configuration to verify CPU, memory, and disk settings were imported correctly.

Method 2: Direct Disk Conversion

If OVF export is not available or practical, you can convert VMDK disk files directly.

# Convert VMDK to qcow2 format
qemu-img convert -f vmdk -O qcow2 MyVM-disk1.vmdk MyVM-disk1.qcow2

# Or convert to raw format for ZFS/LVM storage
qemu-img convert -f vmdk -O raw MyVM-disk1.vmdk MyVM-disk1.raw

After conversion, create a new VM in Proxmox with the desired configuration, then import the converted disk:

# Import the converted disk to the VM
qm importdisk 200 MyVM-disk1.qcow2 local-lvm

# Attach the imported disk to the VM (check the output for the exact disk name)
qm set 200 --scsi0 local-lvm:vm-200-disk-0

Post-Migration: Driver and Configuration Changes

Linux VMs

Linux VMs typically require minimal changes. The kernel includes VirtIO drivers by default. Key steps:

• Remove VMware Tools: vmware-uninstall-tools.pl or uninstall the open-vm-tools package.
• Install the QEMU guest agent: apt install qemu-guest-agent (Debian/Ubuntu) or yum install qemu-guest-agent (RHEL/CentOS).
• Update /etc/fstab if disk device paths changed (use UUIDs to avoid this issue).
• Reconfigure network interfaces if MAC addresses changed.

Windows VMs

Windows VMs require more attention:

• Install VirtIO drivers: Before changing disk controllers to VirtIO, attach the VirtIO ISO to the VM and install the drivers. The safest approach is to add a small temporary VirtIO disk, boot the VM with both the old IDE/SCSI disk and the new VirtIO disk, install drivers from the ISO, then switch the main disk to VirtIO.
• Network drivers: Install the VirtIO network driver from the ISO, then switch the network adapter model to VirtIO in the VM configuration.
• Uninstall VMware Tools: Remove VMware Tools from Programs and Features before or after migration.
• Install QEMU Guest Agent: Available on the VirtIO ISO under the guest-agent directory.

Network Reconfiguration

Review and update network settings for each migrated VM:

• Verify VLAN tags are correctly applied in the Proxmox VM configuration.
• Update static IP configurations if the network infrastructure changed.
• Test connectivity to dependent services (DNS, databases, file shares).
• Update firewall rules on the Proxmox host if using the built-in firewall.

Migration Strategy for Larger Environments

For environments with dozens or hundreds of VMs, a phased approach is essential:

1. Phase 1: Migrate development and test environments first to build team familiarity.
2. Phase 2: Move non-critical production workloads with generous maintenance windows.
3. Phase 3: Migrate critical systems with tested rollback plans.

Throughout the process, tools like ProxmoxR can help your team monitor the new Proxmox environment alongside existing VMware systems, providing mobile visibility during the transition period.

Cleanup

After confirming each migrated VM is running correctly, clean up temporary import files on the Proxmox host to reclaim storage space. Remove the source VMs from VMware only after a sufficient validation period — at least one full business cycle for production workloads.