A Practical VMware to Proxmox VE Migration Checklist

Most VMware-to-Proxmox migrations fail long before the first VM is imported. They fail because nobody built an inventory, nobody agreed on a rollback plan, and the first import was attempted on a Friday afternoon. Here is the checklist we use in our migration workshops.

1. Inventory everything first

List every VM, its disk sizes, its network, and — critically — what it depends on. A VM with a database that another VM talks to cannot be migrated in isolation. Sort the estate into waves: low-risk, testable workloads first, business-critical systems last.

2. Map networks and storage before touching VMs

Proxmox uses Linux bridges where vSphere uses vSwitches, and local ZFS or shared storage where you may have used VMFS datastores. Draw the mapping on paper first. It is far cheaper to find a mismatch in a diagram than during a cutover window.

3. Use qm importovf, but plan the conversion

The qm importovf command imports OVF/OVA images cleanly in most cases. The two things that consistently need attention are disk controller types and network interface names. Import one sample VM and inspect it carefully before batch-processing the rest.

4. Replace VMware Tools with the QEMU guest agent

The VMware guest tools do not belong in a Proxmox guest. Remove them and install the QEMU guest agent so snapshots, backups and shutdown behave correctly.

5. Decommission with a paper trail

Only retire the old platform once the new estate has run in parallel long enough to prove itself. Keep the old hosts powered off but reachable for a defined period, and document the final shutdown decision.

Migration is a process, not a script. Follow the checklist, rehearse one wave, and the rest becomes routine.