KVM servers only; OpenVZ, Xen and Virtualizor-managed Proxmox guests are not imported by this path.
What carries over
- Customer accounts (matched by e-mail address)
- Plans
- IP blocks, with each server's IPv4 addresses kept
- MAC addresses
- Disks, copied from the KVM host over SSH
What does not
- Snapshots and backups
- UEFI settings (servers are imported as BIOS)
- Extra network cards
- Disks on Ceph or ZFS in the source panel
- Passwords: customers sign in with a password reset or through your billing system
Step by step
-
01
Install VMStack and a nodeInstall the panel on its own server and at least one node with enough free disk. The trial covers the whole migration.
-
02
Connect to the sourceGive the import wizard the source panel's database access and SSH access to its KVM hosts.
-
03
Dry runThe wizard lists what it would create and what it cannot carry, and exports it as CSV. Nothing changes yet.
-
04
Import accounts, plans and addressesCustomers, plans and IP blocks are created in VMStack, with each address reserved for its server.
-
05
Move the serversBy default the source server is shut down, its disks are copied, and it starts on the VMStack node with the same IPv4 addresses and MAC. Or import "records only" and move disks yourself later.
-
06
Switch billingPoint your billing module at VMStack, or keep the old SolusVM module working through the SolusVM-compatible API while you change over.
Downtime
Each server is down while its disks are copied: roughly the disk's used size divided by the copy speed between the hosts. Servers move one at a time or in batches, so you plan the window per customer.
Test the move during the free trial
Install the panel on your own server, add a node and run real servers. No card, no feature limits. Purchases after the trial are final, so the trial is the time to test.