Migrating to SkyVirtHCI
The platform includes a migration connector that talks directly to your existing environment, lists its virtual machines, and imports the ones you choose — no export ceremony, no intermediate files to shuttle around.
Supported sources
| Source | How it connects |
|---|---|
| VMware vSphere | vCenter or standalone host, over the management API |
| Microsoft Hyper-V | Windows remote management |
| oVirt / RHV | Engine API |
| Linux KVM hosts | SSH |
| VirtualBox | SSH to the host machine |
Two ways to move a VM
Cold migration
The straightforward path: the source VM is powered off (or you let the connector power it off), its disks are copied, converted and imported, and the VM is recreated here. Right for workloads that tolerate a maintenance window, and the only option for some sources.
Warm migration — minutes of downtime, not hours
For workloads that can't sit in a window while terabytes copy, warm migration does the heavy lifting while the source VM keeps running:
- The bulk of each disk is copied live — hours of transfer, zero downtime.
- Changes that happened during the copy are synced in shrinking rounds.
- When the remaining delta is small, the migration parks and waits for you.
- At the moment you choose, the source VM shuts down, the last few hundred megabytes sync, and the VM starts here. Cutover downtime is typically measured in seconds.
If anything goes wrong before cutover — or you simply cancel — the source VM is untouched and keeps running as if nothing happened.
Mapping the details
- Networks: each source network card maps to a virtual network here, per NIC.
- Disks: each source disk can land on a different datastore.
- Retries: long transfers survive network blips; interrupted copies resume rather than restart.
A migration plan that works
- Inventory. Connect the source, look at what's actually there. Every estate has forgotten VMs — decide their fate now.
- Pilot. Move two or three low-stakes VMs cold. Verify boot, network, monitoring.
- Waves. Group related VMs and move them together — warm migration for anything with users on it, cutovers scheduled in minutes-long windows.
- Keep the exits open. Source VMs stay intact after migration until you decommission them; rollback is "switch back on", not "restore from backup".
Comparing platforms first? Start with the honest comparisons: VMware · Nutanix · Proxmox · oVirt.