Moving from Virtualizor to VorticPanel
VorticPanel is a self-hosted KVM VPS control panel. Point an import at Virtualizor's API and it brings your servers, IP addresses and customers across, onto your own packages. A dry run shows what will happen to each server first.
Per node, unlimited VMs
List prices per node per month, October 2026.
On 10 nodes, against Virtualizor Professional
$1,320 a year less
Every license includes resellers, backups, DNS, the API and imports, and paying yearly gets two months free. There's also $4 for nodes with up to 5 VMs and $1 for a node with one.
All pricing →How moving from Virtualizor works
A copied server's original disk stays on the old hypervisor, and an adopted server's original definition is kept. Either can be rolled back.
- 1
Connect
Enter your Virtualizor address and an admin API key and pass from API Key Pairs. The import only reads Virtualizor's API.
- 2
Map
Choose which of your packages, node groups and IP pools each Virtualizor package, hypervisor and range becomes.
- 3
Dry run
Every server is checked from the node that will move it, and anything it can't bring is marked with the reason.
- 4
Move
Copy servers to your nodes, or adopt them where they are. Each one is a job with a live log.
- 5
Check
Each server is checked to run and answer on its address. Roll back any one of them for up to 14 days.
Copy or adopt
| Copy | Adopt | |
|---|---|---|
| Ends up | On one of your nodes | On the same machine, now one of your nodes |
| Needs | SSH as root from your node to the Virtualizor hypervisor | The agent installed on the Virtualizor hypervisor |
| Downtime | A last pass of what changed, after copying while it runs | One restart |
| Rollback | The copy goes and the original starts again | The original definition is put back |
- Its certificate, pinned
- Virtualizor's API usually has a self-signed certificate. The import shows its SHA-256 fingerprint for you to compare, and keeps to that certificate from then on.
- Adopt in place
- Install the agent on a Virtualizor hypervisor and it becomes one of your nodes. Its servers keep their LVM, ZFS or qcow2 disks, those in /home/vms included, and restart once.
- Removing Virtualizor
- Once a node's servers are adopted, the panel stops Virtualizor and its cron jobs there and moves its files aside. If a server stops or loses its bridge afterwards, everything is put back.
- The master goes last
- Connect the import to the master, and move other hypervisors in later batches if you like. Virtualizor stays on the master until the servers on every other hypervisor have moved.
What you get once you're over
- Nodes connect out
- Agents connect out to the controller over HTTPS, and consoles, jobs and stats travel over those connections.
- Moves between nodes
- Live, with a brief pause to switch over, or with one restart where live can't work, such as between Intel and AMD nodes. Emptying a node moves its servers off two at a time.
- Resellers under their brand
- Quotas, packages and locations per reseller, with their own customers, brand and billing link.
- WHMCS and Blesta modules, and an API for the rest
- The modules create, suspend, unsuspend, terminate and upgrade servers. Other billing panels make the same API calls, with idempotency keys and signed webhooks.
- Encrypted backups off the node
- Full or incremental, deduplicated, to S3 or SFTP. Customers restore their own.
- Customer self-service
- Console, reinstall, firewall, reverse DNS, DNS hosting and team access.
Questions about moving from Virtualizor
How long is each server offline?
An adopted server is off for one restart. A copied server keeps running while its disk is copied, then shuts down for a last pass of what changed. The copying node installs Python on the Virtualizor hypervisor for this when it's missing; if it can't, the server is shut down before its whole disk is copied. The dry run estimates each server's downtime.
Do my customers keep their IP addresses?
Virtualizor's IPv4 pools come across as pools of your own, or join ones you have. Adopted servers keep their addresses. A copied server keeps its own when the range is routed to its new node; otherwise it gets new ones from that node's pools, set inside the server through its guest agent, and the import can email each owner their new addresses.
What about Windows and UEFI servers?
Windows servers keep their chipset, disk bus, network card, clock and Hyper-V settings as closely as your nodes allow, so they boot with the drivers they have. UEFI servers bring their NVRAM. A server set to UEFI whose disk can only boot with BIOS starts with BIOS, and the other way round.
What doesn't come across?
OpenVZ, LXC and anything else that isn't KVM, disks that aren't raw or qcow2 or that read a backing file, and servers with more than 9 disks. They keep running on Virtualizor, and the dry run lists each one with the reason. A server that moves leaves behind its snapshots, backups, firewall rules, TPM and private networks; the dry run names the ones that had firewall rules.
Can I undo it?
Yes, one server at a time, for 3, 7 or 14 days after the last server moves. Rolling back a copy deletes it and starts the original, which stayed on the Virtualizor hypervisor. Rolling back an adopted server gives it back its original disk name and definition.