Move Proxmox VMs and containers between nodes
NexoVirt moves a VM or container from one Proxmox node or cluster to another, even when they are not in the same cluster. Running VMs move live, a pre-flight check runs first, IPs and port forwards come along, and the original stays as a stopped safety copy until you are sure.
What it does
Move guests between separate nodes and clusters, live, with a safety copy.
-
Across clusters
Move guests between separate nodes and clusters that NexoVirt manages, not only inside one Proxmox cluster.
-
Live when it can
Running VMs move live, containers restart on the target, stopped guests move offline.
-
Pre-flight first
Storage and bridge mapping, free VMID, versions, reachability and guest settings are checked before anything moves.
-
IPs and port forwards
Keep the IP or take a new one from a zone on the target, and port forwards move with the guest.
-
A safety copy
The original stays stopped and locked for a few days (seven by default), then it is removed. Delete it earlier with one click.
-
Evacuate a node
Put a node into maintenance and move its guests away one at a time, with a progress page for the whole run.
Why not just use the Proxmox web UI?
Proxmox VE runs the virtualization. NexoVirt adds the layer around it. Migration & evacuation, task by task:
| Task | Proxmox web UI | NexoVirt |
|---|---|---|
| Move a VM to another cluster | Back up, copy, restore and fix the network by hand | Pick the target, review the pre-flight, start |
| Watch a transfer | Task log text | Step tracker, live log and an estimate |
| Empty a node for maintenance | Migrate guest by guest | One evacuation run |
How to use it
Up and running in 4 steps, all in the panel.
-
Open a guest and choose Migrate.
-
Pick the target node, check the storage and bridge mapping, the IP plan and the pre-flight.
-
Start: the live page shows the transfer, then the guest runs on the target.
-
Delete the safety copy when you are sure, or let it expire.
See it in the panel
Real screenshots from NexoVirt, with demo data.
Migration & evacuation FAQ
Do both nodes have to be in the same Proxmox cluster?
No. NexoVirt migrates between separate nodes and clusters it manages, using Proxmox remote migration. Both sides need Proxmox VE 7.3 or newer.
What happens to the original guest?
It stays as a stopped, locked safety copy on the source for a few days (seven by default) and is then removed. You can delete it earlier.
Start running NexoVirt today
Free for homelabs with unlimited VMs on up to 2 nodes. Running a hosting business? Upgrade in place when you grow, no migration.