Sales Chat - Click Here

Knowledge Base

Search by either entering keywords/KB_ID or by selecting a category.

KB ID: 6263

Product: TS5010 Series | TS6000 Series | TS5020 Series | TS71210 Series | TS3010 Series | TS3020 Series | TS-Essentials Series 2022 | TS3030 Series | TS Essentials Series 2025

Alternative Methods to Migrate VMware ESXi VMs to Proxmox VE

Last Updated: 11/03/2026


Purpose

This article describes three methods for migrating VMware ESXi virtual machines to Proxmox VE without using Veeam Backup and Replication.

Environment: VMware ESXi 7.0.3, Proxmox VE 9.2, Buffalo TeraStation TS51220 NAS.

Migration Methods

  • Method 1: Proxmox Built-in ESXi Import Wizard
  • Method 2: StarWind V2V Converter
  • Method 3: VMware OVF Export and Proxmox Import using Buffalo NAS

Before starting: Verify that a current backup is available. Shut down the source VM for the final migration when possible, and avoid unnecessary VMware snapshots.




Method 1 - Proxmox Built-in ESXi Import Wizard

Import VMware VMs directly into Proxmox through the Web UI without intermediate files.

1. Add the ESXi Host

  1. In Proxmox, navigate to Datacenter - Storage - Add - ESXi.
  2. Enter the ESXi server IP address and credentials.
  3. Enable Skip Certificate Verification if using a self-signed certificate.
  4. Click Add.

 

2. Select the VMware VM

  1. Select the newly added ESXi storage.
  2. Open Virtual Guests.
  3. Select the desired VM and click Import.

3. Configure and Import

  1. Verify the VM name, CPU, memory, and OS Type.
  2. Set Default Storage to local-zfs.
  3. Select the appropriate network bridge.
  4. Leave Live Import disabled for standard offline migration.
  5. Review disk controllers and firmware settings under Advanced.
  6. Click Import and wait for completion.

 

Notes:

  • VMware snapshot chains may significantly slow down imports. Consolidate unnecessary snapshots before migration.
  • Import performance may depend on the ESXi management network and datastore performance.
  • CD-ROM images may need to be reconfigured after migration.




Method 2 - StarWind V2V Converter

StarWind V2V Converter provides a Windows-based GUI for directly converting VMware VMs to Proxmox VE.

Software: StarWind V2V Converter 9.0.1.848

1. Connect to VMware ESXi

  1. Launch StarWind V2V Converter.
  2. Select Remote VMware ESXi Server or vCenter as the source.
  3. Enter the ESXi server address and credentials.
  4. Select the VM to convert.

 

2. Select Proxmox as Destination

  1. Select Proxmox as the destination platform.
  2. Enter the Proxmox management IP address and credentials.
  3. Continue to the VM configuration screen.

 

3. Configure the Destination VM

  1. Click Configure for the selected VM.
  2. Specify the VM name and VM ID.
  3. Select the destination Proxmox node.
  4. Select the target storage, such as local-zfs.
  5. Set the appropriate OS Type, CPU, memory, and BIOS or UEFI firmware.
  6. Click OK.

Important: Verify the OS Type. StarWind may default to Linux even when converting a Windows VM. Also ensure the target storage is a writable Proxmox datastore rather than the ESXi import-source storage.
 

4. Start Conversion

Click Convert and wait for the conversion to complete.

After conversion, open the new VM in Proxmox and verify its firmware, disk controller, and boot order before starting it.

Notes:

  • If conversion fails with Not enough space, verify destination storage selection and available capacity.
  • If conversion fails, check the StarWind conversion log for the detailed error.
  • Windows may require storage controller adjustments after conversion.




Method 3 - VMware OVF Export and Proxmox Import Using Buffalo NAS

Export a VMware VM through the ESXi Web UI, save the OVF files directly to a Buffalo NAS SMB share, and import them through the Proxmox Web UI.

Migration Flow: VMware ESXi - Windows browser - Buffalo NAS SMB - Proxmox local-zfs

1. Prepare Buffalo NAS Storage

  1. Create an SMB share on the Buffalo NAS, such as pve-import.
  2. In Proxmox, navigate to Datacenter - Storage - Add - SMB/CIFS.
  3. Enter the NAS IP address, share name, and credentials.
  4. Enable Import and Disk image content types.
  5. Click Add.

Proxmox creates an import directory within the SMB share. Map the share as a Windows network drive and use this directory for the VMware export files.
 

2. Export the VMware VM

  1. Shut down the source VMware VM.
  2. In the ESXi Web UI, right-click the VM and select Export.
  3. Select the OVF and VMDK files. Include the manifest and NVRAM files when available.
  4. Allow multiple automatic downloads if prompted by the browser.
  5. Save the files directly to the Buffalo NAS import directory.
  6. Verify all downloads finish successfully.

 

Typical exported files:

  • .ovf - VM configuration
  • .vmdk - Virtual disk
  • .mf - Manifest file
  • .nvram - EFI settings, if available

Important: Keep the OVF and its referenced VMDK files together. Large VMDK downloads may take considerable time and can be interrupted by browser or ESXi session timeouts.

3. Import OVF into Proxmox

  1. In Proxmox, select the Buffalo SMB storage.
  2. Open the Import tab.
  3. Select the OVF file and click Import.

 

4. Configure the Imported VM
 

Under General:

  • Verify VM ID, name, CPU, and memory.
  • Set OS Type to the correct operating system.
  • Set Default Storage to local-zfs.
  • Use RAW disk format for ZFS storage.
  • Select the appropriate network bridge.
  • Leave Live Import disabled for offline migration.

Under Advanced:

  • Verify the target storage for the OS and EFI disks.
  • Keep a compatible SCSI controller for the initial boot.
  • Leave Prepare for VirtIO-SCSI disabled if the required Windows drivers are not installed.
  • Review network adapter settings.

Under Resulting Config, verify the firmware, disk storage, and boot order.

 

5. Start the Import

Click Import and wait for the task to finish.

After importing, check the VM hardware and boot configuration before starting Windows.

Common Issues and Troubleshooting

1. Slow ESXi Import

VMware snapshots can significantly reduce import performance. Remove or consolidate unnecessary snapshots before migration. Also verify network and source datastore performance.

2. StarWind Not Enough Space Error

Verify that the destination storage points to a writable Proxmox datastore such as local-zfs and has sufficient free space. Check the StarWind conversion log if the error persists.

3. OVF Export Timeout

Large VMDK exports may exceed browser or ESXi session limits. Ensure all files finish downloading. For large VMs, consider using the direct Proxmox ESXi importer or the separate NFS migration procedure.

4. Windows Boot Loop or Startup Repair

Windows may fail to boot if the imported disk uses a storage controller without a compatible boot driver.

Solution: Shut down the VM, detach the OS disk without deleting it, reattach it as SATA0, and set SATA0 first in Boot Order. Install VirtIO drivers before optionally changing back to VirtIO SCSI.

5. No Bootable Device or UEFI Boot Failure

VMware EFI boot entries may not be preserved during migration.

Solution: Verify the original BIOS or UEFI mode, the Proxmox EFI Disk, and the boot order. If necessary, recreate the Windows Boot Manager entry or repair the EFI boot configuration.

6. Additional Post-Migration Checks

  • Verify the correct OS Type, CPU, RAM, and disk configuration.
  • Keep the migrated VM network disconnected while the original VM remains active.
  • Install VirtIO drivers and QEMU Guest Agent as needed.
  • Check Windows activation and static IP configuration.
  • Verify application services before production cutover.
  • Shut down the original VMware VM before connecting the migrated VM to the production network.

Additional Migration Option

For larger VMs, another option is to clone the VMware VM directly to a Buffalo TeraStation NFS datastore and import the VMDK from the same NAS into Proxmox. This avoids browser downloads and Windows intermediate storage.

Refer to the separate KB: Migrate VMware VM to Proxmox Using TeraStation NFS Share.

Related Articles

X