Migrating virtual machines (VMs) from VMware ESXi to Proxmox Virtual Environment (VE) can seem daunting — especially if you’re moving production workloads. But with recent improvements to Proxmox’s tools and clear strategies, you can complete this migration methodically, with minimal downtime and risk.

In this guide, you’ll learn why migrate to Proxmox, the best migration paths, and a step-by-step walkthrough optimized for reliability and performance.

Why Migrate from VMware to Proxmox VE

Proxmox VE is a powerful, open-source virtualization platform based on Debian Linux that combines KVM (for VMs) and LXC (for containers) in a single web interface. It supports flexible storage options (ZFS, Ceph, LVM), built-in backup and replication, clustering, and advanced networking — without the proprietary licensing costs of VMware. (Wikipedia)

Organizations migrate from VMware to Proxmox to:

• Reduce licensing costs
• Gain open-source flexibility
• Use built-in features like snapshot scheduling and backup
• Simplify infrastructure with a unified UI

Preparation Before Migrating VMware VMs to Proxmox VE

Proper preparation is one of the most overlooked — yet most critical — parts of a successful VMware to Proxmox migration. Taking the time to clean up the source VM and document key settings will dramatically reduce post-migration issues and downtime.

Before starting any migration method, complete the following steps:

Clean Up Guest Tools and Drivers

Before migrating, remove any guest tools or drivers that are specific to the old hypervisor, such as VMware Tools. These components can cause conflicts after migration and may be difficult to remove once the VM is running on Proxmox VE.

Removing them in advance ensures a cleaner transition and avoids unnecessary boot or driver issues later.

Document Network Configuration

Carefully note down the existing guest network configuration.

Windows-Specific Network Considerations

For Windows virtual machines, consider removing any static IP configuration before migration. After the VM is imported into Proxmox, the network adapter will change, and Windows treats it as a new device.

If you attempt to reuse the same static IP on a “new” adapter, Windows may display warnings or block the configuration — even though the old adapter no longer exists.

DHCP Reservations and MAC Addresses

If your environment relies on DHCP reservations:

• Update the reservation to match the new MAC address of the Proxmox VM NIC
• Or, manually assign the original MAC address to the target VM’s network interface in Proxmox

Doing this ensures the VM receives the correct IP address immediately after boot.

Full-Disk Encryption and vTPM Considerations

If the VM uses full-disk encryption and stores encryption keys in a virtual TPM (vTPM):

• Consider disabling encryption before migration
• Proxmox VE currently cannot import or migrate vTPM state from VMware

Always ensure you have manual recovery keys available in case the VM needs to be decrypted after migration.

Power Down the Source VM

For a clean and consistent migration, fully power down the source VM before starting the import process.

Migration Methods: Choose What Fits Your Environment

There are generally two migration paths:

1. Automatic Import Using Proxmox ESXi Import Wizard

The easiest and fastest method — ideal for most environments running ESXi 6.5+ connecting directly from Proxmox.

How it works:

1. Proxmox VE version
   Ensure your Proxmox VE is running version 8 or newer and that all available system updates have been applied.
2. Add ESXi as storage
   In Proxmox VE web UI: Datacenter → Storage → Add → ESXi. Enter your ESXi host IP/credentials.
3. Launch the Import Wizard
   Once connected, the wizard lists all VMs on the source host. Select the VM(s) you want to import. (Proxmox)
4. Configure and Import
   The wizard maps configuration and migrates disks. Some tools allow Live Import — meaning the VM boots while data continues copying (great for minimizing downtime).
5. Final Steps
   After import, verify VM settings (disk controllers, bridges, storage) and ensure networking works correctly.

This method is recommended for most users where ESXi is accessible and VMs don’t rely on exotic storage like vSAN, which often must be moved first. (Facebook)

2. Manual Migration (Powerful + Controlled)

Steps include:

Restore from Backup

If you already maintain reliable VM backups, this is often the cleanest option.

• Check whether your backup solution supports direct restores to Proxmox VE.
• If not, you can boot the VM from a live medium and perform an in-place restore — similar to restoring onto bare metal.

Clone Disks Directly (Clonezilla)

Tools like Clonezilla allow you to clone VM disks directly from the source VM to the target VM.

How it works:

• Boot both the source and target VM using a Clonezilla live meduim.
• Clone the disk directly over the network, or
• Store the disk image on a network share and restore it to the target VM.

Import OVF Exports

If the VM is exported from VMware as an OVF, Proxmox VE can import it either via GUI or the command line.

Exporting with ovftool

One of the most flexible ways to export a VM from VMware is using ovftool, available directly from VMware. Ensure the version supports your ESXi release.

On Proxmox VE, install the required utility:

apt install unzip

Extract ovftool and run it using one of the following examples:

• From an ESXi host

./ovftool vi://root@<ESXi-IP>/<VM-name> /path/to/export/

• From vCenter

./ovftool vi://<user>:<password>@<vCenter-IP>/<Datacenter>/vm/<VM-name> /path/to/export/

If you are unsure of the VM path, running ovftool with list available locations.

Once exported, you should have an .ovf file and matching .vmdk disk files.

Importing into Proxmox VE

Use the following command to import the OVF:

qm importovf <vmid> <VM-name>.ovf <target-storage>

Example:

qm importovf 100 Server.ovf local-zfs

Notes:

• Choose a free VMID (Tab auto-completion helps).
• Target storage must allow Disk Image content.
• If target storage is used, you can specify (qcow2 is recommended for KVM):

--format raw|qcow2|vmdk

Import Disk Images Directly (qm disk import)

Another flexible approach is importing .vmdk files directly.

Requirements:

• Proxmox VE must have access to both the .vmdk and *-flat.vmdk files.
• This is easiest when both clusters share a network-accessible storage location.

Workflow:

1. Complete the preparation steps on the source VM.

2. Create a new VM in Proxmox VE (remove the default disk).

3. Access the Proxmox host shell.

4. Navigate to the directory containing the .vmdk files.

5. Run:

qm disk import <vmid> <disk.vmdk> <target-storage>

6. Attach the imported disk and to the correct bus.

7. Configure boot order if the disk image is the OS disk.

Final Steps After Migration

Once VMs are imported and booting:

1. Update Network Configuration
   The virtual network adapter name will almost certainly change after migration.
2. Install Missing Drivers (Especially for Windows)
   Windows virtual machines often require additional drivers after migration:
   • Download and attach the VirtIO driver ISO to the VM.

Conclusion

Migrating VMware VMs to Proxmox VE in 2025 is more streamlined than ever, thanks to the built-in ESXi Import Wizard and flexible manual options. Whether you’re migrating a homelab or a production environment, following structured steps and best practices will help you achieve a smooth, reliable transition.

By combining official guidance from the Proxmox wiki with real-world tools and workflows, this migration can be both efficient and low risk — empowering you to unlock Proxmox’s open-source flexibility without losing momentum. (Proxmox VE)