Import is three jobs that get sold as one button. Inventory, disk conversion, and cutover are different. Mixing them up is how a weekend plan becomes a quarter.
Inventory
kcore-migrate inventories vCenter or Proxmox and can write Terraform for kcore, plus a gap report. The gap report tells you which guests do not map. Read it before you tell anyone the date. Provider 0.5.0 does not inventory VMware or Proxmox by itself. The migrate tool writes guests.tf. After convert, set image_path and image_format on kcore_vm.
Convert
convert takes an exported disk and writes qcow2 or raw with virt-v2v or qemu-img. It does not pull the disk bytes straight from vCenter. Someone still exports, copies, and checks the image. That is a capacity and time problem. Size the pipe and the disk before you promise the window.
Cutover
Cutover is still a project. You choose the maintenance window, the DNS or VIP change, the test that says the guest is up, and the backout. Live migration inside kcore does not move a guest off VMware. The guest is created on kcore from the converted disk. Shared Ceph matters after it is already a kcore VM, if you need to move it between kcore hosts without copying blocks.
Checklist
- Inventory and gap report, with an owner.
- An export path and a tested convert for one Windows guest and one Linux guest.
- An image format that matches what kcore_vm or kctl expects.
- A network plan: which NIC, which address, and what breaks if the old MAC changes.
- A backup of the source that you have restored once.
- A backout that does not depend on the new platform being healthy.
- A second guest only after the first one has run for a real workday.
The longer explanation of tool categories is Three kinds of VMware migration tool. The commands are in the import guide. Use the checklist in the project plan, not as a slide.
Questions: team@tacconiconsulting.com.