Hyper-V / ESXi → Proxmox Migrator

Move Hyper-V and VMware ESXi/vCenter VMs to Proxmox VE — disks, firmware and all — in a few clicks.

$99 / year, per machine

Download

An exact clone, not a rebuild

The Migrator is a Windows desktop app that clones a Hyper-V or VMware ESXi/vCenter virtual machine — its configuration and full virtual disk data — and restores it as a QEMU/KVM VM on Proxmox VE.

The goal is a bootable, data-identical Proxmox VM without manual BIOS fiddling or post-processing in most cases. Firmware, disk controllers and network adapters are chosen for you from the source VM, so you never have to pick BIOS settings on the Proxmox side.

Firmware mapped automatically

Gen1 / BIOS → SeaBIOS. Gen2 / EFI → OVMF (q35).

Full disk data

Every virtual disk is copied and converted with qemu-img to qcow2 or raw.

One VM or a batch

Multi-select VMs and migrate them in a single run.

Features

Sources
  • Hyper-V hosts, local or remote, with your Windows login or explicit credentials
  • Hyper-V Generation 1 and Generation 2 VMs
  • VMware ESXi (standalone) or vCenter via VCF PowerCLI
  • Offline VHDX copy or live Export-VM (Hyper-V)
  • Offline VMDK download or live OVF export (ESXi)
  • Optional include-checkpoints toggle (Hyper-V)
  • Clean guest shutdown preferred; live export is available with a warning
Conversion & boot
  • qemu-img conversion of VHD/VHDX or VMDK to qcow2 (preferred) or raw
  • Automatic firmware mapping: Gen1/BIOS → SeaBIOS, Gen2/EFI → OVMF (q35 + EFI disk)
  • Secure Boot disabled for first boot by default
  • Compatible mode (default): SATA disk + e1000 NIC so Windows boots without VirtIO drivers
  • VirtIO + offline driver inject: DISM-injects virtio-win drivers before upload
  • Performance mode: VirtIO from the start for guests that already have drivers
  • Matching VM created for you: name, cores, memory, network bridge, optional MAC preserve, boot order
Reliability
  • Streaming upload through the Proxmox REST API with progress
  • SSH/SCP fallback for large disks when API upload fails, or prefer SSH for every upload
  • Resume a failed migration — disks already uploaded are skipped
  • Large exports are kept, never deleted, when you resume
  • Passwords stored with Windows DPAPI, never in plain text
  • Rotating log files plus a detailed in-app log pane
Tools
  • Batch migration: multi-select VMs and clone them in one run
  • Repair boot tool for a Proxmox VM that shows a blank console or “no bootable device”
  • Prerequisite installer downloads qemu-img and VMware PowerCLI for you (one-time)
  • Connection profiles for Hyper-V, ESXi and Proxmox (lab vs. production)
  • Optional start after create and temp-file cleanup
  • Dual progress bars and dark mode

How it works

1
Connect your source

On the Hyper-V or ESXi tab, enter the host and your login, then Test Connection and Refresh VMs.

2
Connect Proxmox

Enter your Proxmox host, user (e.g. root@pam) and password, then pick the node, storage and network bridge.

3
Choose VMs & options

Select one or more VMs, then the seamless mode, disk format, NIC model and shutdown or live export.

4
Clone to Proxmox

The app exports, converts, uploads and creates the VM, and can start it when it's done. Watch progress in the log pane.

Requirements

  • Windows 10/11 or Windows Server, with the app run as administrator (it requests elevation through UAC).
  • Nothing else to install for the app itself — it ships as a single signed .exe.
  • Proxmox VE 7 or 8+ with API access, using the same user@realm and password as the Proxmox web UI.
  • Hyper-V source: the Hyper-V role or RSAT Hyper-V tools (Hyper-V PowerShell module).
  • ESXi / vCenter source: VMware VCF PowerCLI. The built-in prerequisite installer can set it up for you.
  • qemu-img for disk conversion. The prerequisite installer can set it up, or point to it in Settings.
  • Free disk space of roughly 2× the source disk file size (export + convert).
  • Proxmox storage that accepts uploads (directory, NFS, etc.). LVM-thin and ZFS work well as the final storage.
  • Optional: Windows OpenSSH Client and SSH keys for the SCP upload fallback.

Licensing

$99 / year, per machine

  • Annual subscription that renews yearly.
  • One machine per license.
  • Moving to a new machine? Deactivate the license on the old machine, then activate it on the new one.
  • Cancel any time from the app's License > Manage billing.
Download

Frequently asked questions

In most cases, yes. The app picks the right firmware from the source VM, disables Secure Boot for the first boot, and by default uses Compatible mode (SATA disk + e1000 NIC) so Windows boots without VirtIO drivers. If a migrated VM still shows a blank console or “no bootable device”, the built-in Repair boot tool can fix it.

No. A Gen1 (BIOS) disk can't boot on OVMF, and a Gen2 (UEFI) disk can't boot on SeaBIOS, without repairing the bootloader. Instead the app maps firmware automatically from the source — Gen1/BIOS to SeaBIOS, Gen2/EFI to OVMF — so the clone boots the way the original did.

Yes, with live export (Export-VM on Hyper-V, OVF export on ESXi). A live export is crash-consistent only, so for databases and other busy servers we recommend letting the app shut the guest down cleanly first.

Re-run it with Resume. The converted files are kept, and disks that were already uploaded are skipped. Resume works per disk file, so a disk that was part-way through uploading starts that disk again.

No. You use the logins you already have: a Windows admin account for Hyper-V, root or administrator@vsphere.local for ESXi/vCenter, and your Proxmox user@realm and password. Passwords are stored with Windows DPAPI, never in plain text.

Each license covers one machine. To move it, deactivate the license on the old machine and activate it on the new one. The subscription renews yearly, and you can cancel any time from License > Manage billing in the app.

Questions before you buy? Email support@bridgeoc.com.