Skip to content

Migrations

Leaving VMware? Priced per VM.

VMware, XenServer and OnApp environments moved onto Proxmox — on our cloud in Vancouver or Toronto, or your own hardware. $300 per VM for a compatible Linux virtual machine (VM), $400 per VM for Windows, fixed in your assessment before anything moves. We run our own hosting: the plan usually lands you on our cloud or on hardware we build for you, and if neither fits it says so. The original stays untouched until you sign off.

From
VMware, XenServer, OnApp
To
Proxmox, Vancouver or Toronto, or your hardware
Access
Your hosts, or the VM files
Support desk
North America

Why now

The platforms are leaving you first

  • vSphere 7 support has ended

    General support ended on October 2, 2025. vSphere 8 follows on October 11, 2027. Canadian renewal quotes under the new licensing are reported at 200% to over 1,000% higher.

  • Citrix Hypervisor 8.2 is no longer supported

    Since June 25, 2025. The old licence files stopped working on April 15, 2026. You now need a Citrix subscription to keep running it.

  • OnApp has no home of its own

    Its website now points to another company. It still runs, but we would not build anything new on it.

Proof

We moved our own cloud first

Our own platforms came off VMware and OnApp onto Proxmox, Windows VMs included. We wrote the step-by-step procedures on our own move. Your migration follows the same ones.

  1. Before we start: list every VM, take snapshots, collect logins, find anything that would block the move

  2. Add the drivers Windows VMs need on Proxmox

  3. Copy each VM across, with the original left untouched

  4. Import to Proxmox and start it the first time in compatibility mode

  5. After the move: drivers, network and applications checked

  6. Clean up and write it down, then your sign-off

6 phases, every VM, every time. A pair of representative VMs goes first as the pilot, including a Windows VM if you have any, at the per-VM rate.

Pricing

A fixed price per compatible VM, set in the assessment

Every migration starts with the assessment. That is where your price is locked in. The assessment fee is credited in full against the migration, or any idig.net job, booked within 60 days of your report. Ask before day 60 if purchasing needs longer.

Assessment

Migration assessment, up to 25 VMs
$499, one-time
Migration assessment, up to 100 VMs
$1,499, one-time
  • A scan and list of every VM from your hosts, what depends on what, Windows and Linux counted separately
  • Every VM sorted into compatible, legacy or no path, from the inventory data; the pilot confirms it
  • Storage and network layout, the order the machines move in, the batches, the pilot plan
  • The fixed per-VM quote, signed by a senior engineer. The prices in the report are the prices you pay
  • The report is yours to take anywhere

Migration

Compatible Linux VM
$300 per VM
Compatible Windows VM
$400 per VM
Compatible VMs, more than 50
A lower rate, set in the assessment.
Legacy VM
from $600 per VM
Minimum migration charge
$1,500, one-time
Large disk, used space over 500 GB
$150 per TB or part of one, per VM
After-hours or extra switch-over slot
$300 per hour
  • All six phases: a test start-up on our side, then a scheduled switch-over during our business hours
  • The original stays untouched until you sign off. If it goes wrong we switch back at no charge
  • One new IP address per VM if it needs one, and updates to DNS records we host
  • Access we need: admin access to your hosts (root on ESXi or the OnApp hypervisor, pool admin on XenServer), or a full disk image of each VM exported at that level (OVA or VMDK from vSphere, XVA from XenCenter, a block-level backup from OnApp), plus an admin login inside each VM for the driver work and the checks
  • Windows costs more because it takes more hands-on time: the old hypervisor's tools come out, the boot filters XenServer and VMware leave in the registry come out (they stop Windows starting anywhere else), the Proxmox drivers go in, and start-up is repaired
  • Windows usually asks to activate again after a move. Your report says which VMs need a new key or activation method; the keys stay yours
  • The VM is off from the start of its final copy until it starts on our side. How long depends on disk size and your link speed; we schedule it, we do not promise a number
  • Not included: changes inside your applications, firewalls we do not run, DNS at other companies, software licences.
  • A login inside the VM alone is not a VM move. That is a rebuild and a data migration, priced on the Environments page

Which VMs

Every VM is sorted before you pay

Your report puts each VM into a group, from the inventory data. The pilot pair confirms it. A VM that turns out to be legacy on the pilot is re-quoted before we go on, or you drop it at no charge.

Compatible

$300 per VM, Windows $400 per VM

The fast drivers our cloud needs are built in or in the current Windows driver pack, so it runs at full speed after the move. Windows costs more because the old hypervisor leaves boot filters in the registry that stop it starting anywhere else; ripping those out is hands-on work.

  • Windows 10 and newer, Windows Server 2012 and newer
  • Red Hat, CentOS, Rocky, Alma or Oracle Linux 6 and newer, Debian 6 and newer, Ubuntu 10.04 and newer, SUSE 11 and newer
  • FreeBSD 9 and newer

Out-of-support systems on this list move at the same price. The report flags them and says when a rebuild is the better spend.

Legacy

from $600 per VM

It still runs, but only on slow emulated hardware, with no fast drivers, no guest agent and no support from its maker. Quoted in hours in your report, with a stop point.

  • Windows 2000, XP, Server 2003, Windows 7, Server 2008, CentOS 3 to 5, Debian 5 and older

If it will not start on our side within the quoted hours, we stop, you pay nothing for that VM, and you choose a rebuild or leave it behind.

No path

Named in the report

It cannot run on our cloud, or cannot legally: macOS guests, AIX, HP-UX, Solaris on SPARC, VMware's own management appliances, and anything whose maker supports it only on ESXi.

  • Encrypted disks, BitLocker with a virtual TPM, USB licence dongles, GPU passthrough and raw LUNs all have a path. The report lists the step and its price.

For each no-path VM the report names the options: keep a small VMware island, rebuild it, or retire it.

A batch is the group of VMs we move in a single window; your report lists them. Each batch is billed in halves: when it starts, and at sign-off. Sign-off is you telling us it works, or 10 business days after the switch-over with no problem reported. Until then the original VM is untouched and we can switch back at no charge. Desk hours are 8 am to 6 pm Pacific, Monday to Friday (11 am to 9 pm Eastern); a switch-over outside them is an after-hours slot. A VM move needs admin access to your hosts or a full export of the VM files from that level. If all you have is a login inside the VM, that is a rebuild and a data migration: see environments.

Your hardware

Landing on your own servers

If the target is your rack, we build the cluster and can keep running it.

Proxmox build-out on your hardware

$999 per server

  • The cluster, storage (Ceph or ZFS), networking, a backup server, security lock-down, handover
  • Three servers minimum. On your hardware the cluster is built first, or is already running, before VMs move

Managed Proxmox

$199 per server a month

  • Patching, monitoring, backup checks, tickets

Start with the assessment.

A 30-minute call first, no cost. Then the assessment; its fee is credited in full against the migration.