VPSie home
Services

Migrate from VMware

Import your virtual machines from vCenter or ESXi without agents, test each one beside the original, and switch when you are ready.

vCenter and ESXiHostHostHostKVM clusterNodeNodeNodeAgentlessWay backTestSwitchKeep sourceVerifyvCenter and ESXiKVM clusterAgentlessHostNodeHostNodeWay backHostNodeTestSwitchKeep sourceVerify

Leave VMware without leaving your workloads behind

VPSie Private Cloud runs on KVM with native VMDK support. Your virtual machines move across with their disks, and the services around them (backup, firewall, chargeback, object storage) come in the same console instead of as separate add-ons.

  • Agentless import from vCenter 7.0 and later, or from ESXi, through a read-only user
  • Nothing to install on the source machines
  • The old platform stays as a fallback until you decide to switch it off
  • Runs connected or fully air-gapped, see VPSie Private Cloud
VMwareweb-01.vmdkdb-01.vmdkapp-01.vmdkImportVPSie Private Cloudweb-01db-01app-01BackupFirewallChargebackObjectsSame console for servers and the services around themVMwareVPSie Private Cloudweb-01Backupweb-01.vmdkImportdb-01Firewalldb-01.vmdkapp-01Chargebackapp-01.vmdkObjectsSame console for servers and theservices around them

Where each VMware product lands

The parts of a VMware estate, and the VPSie service that takes over each job.

VMware productWhat it doesVPSie service
vSphere and ESXiRuns virtual machinesCloud servers on KVM, with native VMDK support
vSANStorage on the same hostsHyperconverged storage in VPSie Private Cloud, plus STaaS volumes
NSXNetworks and firewallTenant networks, the Secure Utility Network (SUN) and firewall, encryption and access control
VMware Cloud DirectorTenants, catalogs and billingTenants, plans, price lists, invoices and the reseller view, built in
Third-party backup toolsBackups and restoresBackup and Disaster recovery in the same console
Object storage add-onsS3 bucketsBuckets with Object Lock

How a move runs

Cold migration, one server or one group at a time, with a test before every switch.

Connect

Add your vCenter (7.0 or later) or ESXi host with a read-only user. VPSie reads the inventory: machines, disks, networks.

Pick

Choose the machines to move first. Small, well-understood workloads make the best first wave.

Import

Each machine is copied while it is powered off (cold migration). A failed attempt is cleaned up, so nothing half-built is left behind.

Test

Start the imported machine beside the original, check the application and the network, and fix anything before users notice.

Switch

Move users and DNS to the new machine. Keep the VMware copy until you are sure, then retire it.

ConnectvCenter or ESXi, read-onlyPickSmall workloads firstImportCold, failures cleaned upTestBeside the originalSwitchUsers and DNSOne server or group at a time, a test before every switchConnectvCenter or ESXi, read-onlyPickSmall workloads firstImportCold, failures cleaned upTestBeside the originalSwitchUsers and DNSOne server or group at a time, a testbefore every switch
One server or one group at a time, with a test before every switch.

Supported sources and known limits

Read these before you plan the first wave. They are the same limits the migration tool enforces.

Sources

Sources

VMware vCenter 7.0 and later and ESXi hosts, plus disk images. Nutanix, Hyper-V, Proxmox and others are covered on the Migration page.

Limit

Disk size

Disks up to 1 TiB each are imported by the tool. Larger disks need a planned approach; ask us before the first wave.

Limit

Secure Boot and vTPM

Secure Boot state and vTPM contents are not carried across. Machines that depend on them need to be re-enrolled after the move.

Guests

Guest tools

VMware guest tools are not needed on the new platform. Plan to remove them and to check drivers inside each guest after import.

VPSieVMwareMove inMove outVMDKqcow2RawOVAOpen disk formats, no lock-in either wayVPSieVMwareMove inMove outVMDKqcow2RawOVAOpen disk formats, no lock-in either way

Keep a way back

A move is easier to approve when nobody is locked in, in either direction.

  • Your VMware environment keeps running until you switch each machine, so you can go back to it
  • Export any stopped server from VPSie as RAW, QCOW2 or OVA
  • Everything in the console is also in the API, so your scripts and tools keep working
  • One license covers the platform modules, see Licensing

What changes for your team

Most daily tasks look familiar. These are the differences people notice first.

One console instead of many

Servers, storage, networks, backups, firewall rules and billing sit in one console and one API, instead of separate products with separate logins.

Tenants and billing included

Each department or customer can be a tenant with its own plans and invoices, which is what Cloud Director was often bought for.

Training included

The platform license includes 10 hours of base training, delivered in sessions, so your administrators learn it on your own setup.

Questions about leaving VMware

Do I need to install anything on my virtual machines?

No. Import is agentless. VPSie reads from vCenter or ESXi through a read-only user.

Is the migration live?

No. Machines are copied while powered off (cold migration). Plan a short window per machine or group.

Can I move back to VMware if it does not work out?

Yes. VMware keeps running until you retire it, and VPSie exports stopped servers as RAW, QCOW2 or OVA.

What about disks larger than 1 TiB?

The tool imports disks up to 1 TiB. Tell us about larger disks early so they get their own plan.

Can we run VPSie air-gapped?

Yes. VPSie Private Cloud runs fully offline, and the license activates air-gapped.

Is exporting a server charged?

Export from VPSie Cloud is charged once, per exported GB. See Pricing.

Learn more: Migration overview · VPSie Private Cloud · Licensing

Plan your move off VMware

Send us the size of your estate. We will propose the first wave and a test plan.