VPSie home
Services

Move off VMware one server at a time

Copy virtual machines from vCenter, ESXi, Nutanix, Hyper-V or Proxmox to VPSie. Nothing is installed on the source, the original stays untouched, and you test the copy before you switch.

1DiscoverFind the machines2CopyDisk to VPSie3TestBoot and check4Cut overSwitch trafficVMwareNutanixHyper-VProxmoxDiscoverCopyTestCut overFind the machinesDisk to VPSieBoot and checkSwitch traffic1. VMware2. NutanixHyper-V4. 3. Proxmox

Move servers to VPSie without touching the source

VPSie Migrate copies a powered-off server from VMware or from a disk image into the data center you choose. It installs the drivers and the VPSie agent on the new server, sets up the network and starts it. The original is read, never changed.

  • Nothing is installed on the source
  • A read-only user for VMware sources
  • Progress by phase and bytes on one page, cancel at any time
  • A failed attempt removes everything created for it
VMwareNutanixHyper-VVPSieCloud serverBare metalCopy first, cut over when you are readyVMwareCloud serverNutanixVPSieHyper-VBare metalCopy first, cut over when you are ready

Pick the card that matches where the server runs

The console shows the sources enabled for your account.

Where the server runsHow VPSie reads itStatus
VMware vCenter 7.0 or laterDedicated read-only user; you confirm the certificateAvailable
VMware ESXi host, or any disk imageOVA, VMDK, VHD, VHDX, QCOW2 or raw, uploaded from your browser or fetched from an https addressAvailable
Nutanix AHVThrough the VPSie Connect applianceAvailable by ticket
OpenStack projectAn application credentialAvailable by ticket
KVM host with libvirt, XCP-ng, XenServer, or any server you can start in rescue modeGuide in the console; provider guides for several hosting companiesGuide

Hyper-V and Proxmox servers come in as disk images (VHDX, QCOW2) or through the rescue-mode route. Public cloud servers move the same way, by exporting a disk image or booting in rescue mode.

Four steps, the same for every source

Cold migration: the source is off while its disks are copied.

Add the source

Choose the data center. For VMware, use Test connection first. Nothing is saved until you confirm.

Power off and start

Shut the machine down, then pick the plan, network options and an SSH key or password.

Watch it run

Phases and bytes done are on the Migrations page. Cancel any time.

Then VPSie builds the server: the disks, the drivers, the agent and the network. When it is ready you test it and switch your users over on your schedule. Delete the source once you are done.

Your sourceVPSieRunningPowered off while copiedTestDelete laterCopy disksphases, bytes doneBuilddrivers, agentSwitchyour scheduleCold migration, cancel any timeYour sourceRunningPowered off while copiedTestDelete laterVPSieCopy disksphases, bytes doneBuilddrivers, agentSwitchyour scheduleCold migration, cancel any time
The source stays off only while its disks are copied.

Know the limits before you plan

These come from the product, not from the sales pitch.

Downtime during the copy

The source is powered off while its disks are copied. Plan a window for each server, sized by disk size and link speed.

Guest support

Linux with systemd, and Windows versions with a VPSie driver set. Others are refused before the server starts.

What is not carried

Secure Boot and virtual TPM contents are not carried over. The new server cannot be powered, resized, deleted or restored until the migration finishes.

Size and uploads

Up to 1 TiB per image file unless your account is set lower, three uploads at once.

Cost shown first

If your account has a per-server migration fee, the console shows it before you start and charges it only when the server is handed over.

Where it lands

Into VPSie Cloud or into your private cloud. Work out sizes first with the cost view in Multi-cloud.

VPSie serverStandardformatsDisk imageExportYour data is not locked inDisk imageStandardformatsVPSie serverExportYour data is not locked in

You can leave later

Migration is not a one-way door. Stop a server and export its disks as files, then download them or save them into one of your buckets in the same data center.

  • RAW: works everywhere, as large as the disk
  • QCOW2: compact, holds only the used part
  • OVA: disks plus a server description for VMware and VirtualBox
  • Charged once per exported GB, only when an export completes

Where migration sits in Protect, Manage, Migrate

Many teams start with the first two and move when the timing is right.

Protect

Back up and replicate the platform you run today, so you are covered while you decide.

Manage

See every server across platforms and what each would cost on VPSie.

Migrate

Move workloads when you are ready, one server or a wave at a time.

  • Test the new server before cutover

Questions before you start

Is my source server changed?

No. VPSie only reads it. VPSie does not power your machines on or off, and a failed or canceled migration removes what it created.

Is there downtime?

Yes, for each server, while its disks are copied. We do not promise zero downtime. Plan windows per server.

Do I install anything on the source?

No. The VPSie agent is installed on the new server, not on the original.

Which sources work?

VMware vCenter and ESXi, disk images, Nutanix AHV, OpenStack, KVM with libvirt, XCP-ng, XenServer, or anything you can boot in rescue mode. Ask us if yours is not listed.

Can I get my servers back out?

Yes. Export any stopped server as RAW, QCOW2 or OVA.

Can you plan a larger move?

Yes. For a data center move, talk to us about assessment, design, waves and testing.

I am leaving VMware. Where do I start?

Read Migrate from VMware: it maps vSphere, vSAN and the rest to VPSie and walks through a first wave.

Learn more: Control panel: projects Server groups Buckets for exported images

Plan the move before you power anything off

Send us a server list and we will tell you which route fits each one.