KingWerx(TM) V2V Migrator for Proxmox VE   v0.1.1
KW Tech Solutions LLC  -  KingWerx(TM)
Migrate VMware vSphere / ESXi VMs to Proxmox VE.
================================================================

WHAT IT DOES
  Migrates VMware VMs to Proxmox VE. Connect to vCenter/ESXi, grade each VM's
  boot-readiness, then convert each disk to the format your Proxmox VE storage takes,
  fix guest bootability (the STOP 0x7B fix), upload the disks to the node, and build and
  start the VM. The source VM is COPIED, never moved or deleted. After a successful
  migration the source is quarantined (network disconnected, autostart disabled) - which
  is reversible.

  The free Proxmox VE import wizard gets the disks across but leaves Windows unable to
  boot. This tool does the part that makes Windows actually start: it arms the correct
  boot driver for the controller the VM will use, chooses that controller by guest age,
  corrects a mis-ordered boot disk, preserves every NIC's MAC address, and re-applies
  static IPs on first boot.

REQUIREMENTS
  - Run on a WINDOWS machine (Windows 10/11 or Server 2016+), as Administrator.
    Nothing is installed on the Proxmox VE nodes - they run Debian; this tool does not.
  - Network access to vCenter/ESXi (443), the Proxmox VE API (8006), and SSH (22) on the
    node that will receive the disks.
  - Proxmox VE credentials: a root@pam login, or an API token plus an SSH private key.
  - Free disk space on the working folder for the exported source disk and its converted
    copy (a Windows guest is converted twice; size the working drive accordingly).
  - Self-contained: qemu-img, govc, OpenSSH and PuTTY are bundled - no internet, no
    Install-Module, nothing to set up on the hypervisor.

YOUR RESPONSIBILITIES
  This tool builds, starts, deletes, and can roll back virtual machines on production
  systems. You review what will be migrated and you approve it.

  - You are responsible for maintaining a current, tested FULL SYSTEM BACKUP of every
    machine this software changes - the source hosts, the target nodes, and the virtual
    machines themselves. A VMDK copy, a VM snapshot, a converted disk, or any file this
    tool writes is NOT a backup.
  - Validate each migrated VM before you decommission any source.
  - If you enable "Replace an existing VM of the same name", the tool DELETES that VM and
    its disks. Make sure it is not a production machine and that you have a current,
    tested FULL SYSTEM BACKUP of it. This cannot be undone.
  - Run this tool only on systems you are authorized to migrate.
  - Support covers this program only - not VMware, Proxmox VE, the guest operating
    systems, or the outcome of any migration.

SESSION LOG
  Every run appends to kwx-migrate.log next to the application, as each line happens -
  what ran, by which user, on which machine. The file stays on that machine; nothing is
  transmitted anywhere.

HOW TO RUN
  1. Extract this whole folder onto a Windows machine that can reach both sides.
  2. Run KwxMigratorPve.exe as Administrator (it also self-elevates via UAC).
  3. Source    : enter vCenter/ESXi host + credentials  ->  Assess Inventory
  4. Assess    : review the grades, tick the VMs you want to migrate
  5. Target    : enter the Proxmox VE host + credentials  ->  Connect to target,
                 then choose the storage and the network bridge(s)
  6. Placement : (cluster, or several storages) choose where each VM lands
  7. Migrate   : Start Migration  ->  watch each VM export, convert, prep, upload, build

  The source VM must be POWERED OFF - this is a cold migration.

HOW THE VM IS BUILT
  - Firmware follows the source: BIOS -> SeaBIOS, UEFI -> OVMF with an EFI disk.
  - Boot controller follows the guest: modern Windows -> SATA, Windows XP / Server 2003
    and older -> IDE, Linux and other guests -> virtio-scsi.
  - Disk format follows the storage: file-backed storage (NFS / directory / CIFS) stores
    qcow2, block storage (LVM / ZFS / Ceph) stores raw. Proxmox VE decides this, not the
    tool. Note that raw pre-allocates each disk's full provisioned size.
  - Every NIC keeps its source MAC address, so DHCP reservations keep working and static
    IPs are re-applied to the correct adapter.

  Disk images are uploaded to the node over SSH, because the Proxmox VE API cannot accept
  VM disks. With a username and password the tool uses those same credentials; with an
  API token you must supply an SSH private key instead. The node's SSH host key is
  accepted on first use and pinned for the rest of the run.

TESTED GUEST OPERATING SYSTEMS
  Validated end to end in our lab: Windows Server 2019 (UEFI, multiple disks, four NICs
  with static IPs), Windows Server 2012, Windows Server 2003 x64, Ubuntu 26.04 - on a
  Proxmox VE cluster (shared NFS, qcow2) and on a standalone node (ZFS, raw).
  Other guests are expected to work on the same mechanisms but have not been tested here;
  the Assess screen says which is which for each VM you select.

LICENSING
  The free trial is ONE completed migration per computer, once. It does not renew, and
  re-downloading or re-extracting the tool does not reset it. After that migration the tool
  will not migrate again on that computer until a license key is entered (About -> Enter
  license key). A license is per technician and is non-transferable. ALL SALES ARE FINAL.

NO WARRANTY / LIABILITY
  This software is provided "AS IS" and "AS AVAILABLE", without warranty of any kind,
  express or implied. KW Tech Solutions LLC does not warrant that any migration will
  succeed or be reversible, or that any virtual machine or data will be preserved,
  converted, or bootable. You assume the entire risk of using it. IN NO EVENT is KW Tech
  Solutions LLC liable for any damages of any kind, including loss or corruption of data
  or virtual machines, downtime, or lost business. NOTHING in this README, the user guide,
  the website, or any other documentation creates a warranty - the full terms in
  LICENSE.txt govern.

  - License agreement: LICENSE.txt (governs your use of this software).
  - Third-party licenses + GPL/LGPL source written-offer: THIRD-PARTY-NOTICES.txt (master
    - covers qemu-img = GPLv2, govc = Apache-2.0 (c) VMware Inc., OpenSSH = BSD/ISC, and
    PuTTY = MIT; full texts in qemu/, govc/, openssh/ and putty/). All bundled tools run
    as separate processes.

TRADEMARKS
  KingWerx(TM) is a product brand of KW Tech Solutions LLC. Microsoft and Windows are
  trademarks of Microsoft Corporation. VMware, ESXi, and vSphere are trademarks of
  Broadcom Inc. Proxmox(R) and Proxmox VE(R) are registered trademarks of Proxmox Server
  Solutions GmbH. This is an independent product and is NOT affiliated with, authorized,
  sponsored, or endorsed by Microsoft, Broadcom/VMware, or Proxmox Server Solutions GmbH.

Copyright (c) 2026 KW Tech Solutions LLC. All rights reserved.
Support: support@kingwerx.com
  - v0.1.1 - code-signed by KW Tech Solutions LLC (Certum).
================================================================