VMware vSphere Migration to eEVOS

eEVOS migration workflow

Move VMware vSphere virtual machines to eEVOS with a guided import.

Discover workloads through vCenter or a standalone ESXi host, select destination storage, map networks and follow every import from the eEVOS web interface.

vCenter or ESXiUse the source model that matches the estate
Per-VM host discoveryResolve the current host for every selected VM
Explicit mappingChoose target storage and destination networks
Visible jobsTrack queued, active, successful and failed imports

Controlled transition

Replace a chain of manual steps with one administrator-led workflow.

vSphere Import brings source discovery, VM selection, storage placement, network mapping, conversion and registration together. The administrator retains control over what moves, where it is placed and when it is validated.

01ConnectUse vCenter or ESXi
02DiscoverRead VM and host inventory
03SelectChoose VMs and target drives
04MapMatch source and eEVOS networks
05ImportExport and convert virtual disks
06ValidateBoot, test and approve

Source flexibility

Use vCenter for a managed estate—or connect to one ESXi host directly.

VMware vCenter Server

Discover virtual machines across a datacentre. eEVOS resolves the current ESXi host separately for every VM, so one batch can include workloads from multiple managed hosts.

  • Saved and testable connection
  • Datacentre-wide inventory
  • Current owning host shown per VM

Standalone ESXi host

Limit discovery to the virtual machines registered on a specific host. This is suitable for independent hosts or a deliberately host-specific migration wave.

  • Direct host connection
  • Host-specific inventory
  • Same storage, network and job workflow
eEVOS in operation

Make the migration choices in the GUI—without assembling a separate conversion toolchain.

Saved sources, network mapping and persistent job history keep the project visible. Click a screenshot to inspect the interface at full size.

Operational control

Keep important decisions explicit.

The import wizard does not hide destination choices. Each VM receives a target drive; existing destination names trigger an overwrite decision; every source network must be mapped.

Encrypted saved credentialsPasswords for saved connections are encrypted at rest and not shown in lists or job history.
Graceful shutdown handlingA running source VM receives a shutdown request. If it does not stop within the defined window, the import fails visibly instead of exporting an active VM.
Automatic guest preparationeEVOS detects the guest operating system and automatically installs the required paravirtualised drivers for supported guests.
Persistent status and historyPreparing, exporting, converting, queued, successful and failed phases remain available for operational review.
Migration planning

A successful import ends with application validation—not with disk conversion.

Before the import During the workflow Before cutover
Confirm capacity, credentials, connectivity, downtime and destination networks. Select each target drive, verify overwrite decisions and monitor job status. Validate firmware mode, CPU, memory, disks, NICs, guest boot, services and external connectivity.

Plan the migration around workloads, downtime and recovery.

We can review the source estate, application dependencies, target storage, network mappings and validation sequence and turn them into a staged migration plan.

Trademark notice: VMware, VMware vSphere, VMware vCenter Server and VMware ESXi are trademarks or registered trademarks of their respective owners. These names are used solely to describe technical interoperability. This page does not imply a partnership, endorsement or certification. Supported functionality and qualified configurations depend on the current euroNAS software version.

Expanded software screenshot
Scroll to Top