XMS (Xloud Migration Suite) moves virtual machine workloads from VMware vSphere and standalone ESXi hosts into Xloud with no agent installed in the source guest. Cold migrations power off the source VM and stream its disks in a single pass; warm migrations perform an online full sync followed by incremental block-level replication, keeping cutover downtime to minutes.Documentation Index
Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt
Use this file to discover all available pages before exploring further.
XMS — Migration Suite
Contact the Xloud team for XMS planning, sizing, and licensing
XMS Documentation
User Guide
Register VMware sources, discover workloads, run preflight checks, and
execute cold or warm migrations from the Xloud Dashboard.
Admin Guide
Deploy the migration service, configure network access to vCenter and ESXi,
plan storage capacity, and manage credentials for production migrations.
CLI Reference
Available command-line workflows and the scope of Dashboard-only operations.
Block Storage
Target volumes are provisioned through Xloud Block Storage — review volume
types, capacity, and quotas before planning a migration wave.
Key Capabilities
Xloud-Developed — XMS is developed by Xloud and ships with XAVS / XPCI.
Agentless Source Access
Connects to vCenter or standalone ESXi over the standard vSphere API.
No agent is installed inside the source guest and no changes are made to
the source VM before cutover.
Cold and Warm Migration
Choose single-pass cold migration for powered-off workloads or warm
migration with Changed Block Tracking for workloads that must stay online
until the cutover window.
Automatic Guest Conversion
VirtIO driver injection, boot loader repair, and removal of hypervisor-specific
tooling are applied offline against the target volume — no manual guest
preparation on the source side.
Preflight Assessment
Pre-migration compatibility checks for OS family, firmware type, disk
layout, and driver support. Risks are surfaced before the job starts.
Incremental Cutover
Warm migration repeatedly syncs only changed blocks since the last sync
using Changed Block Tracking. The final cutover replicates a minimal
delta and switches the workload to Xloud.
End-to-End Dashboard
Discovery, assessment, job submission, live progress, event streaming,
and post-migration reports are all available from the Migration panel
in the Xloud Dashboard.
Migration Workflow
Register a VMware source
Add a vCenter or ESXi endpoint to the Migration panel with the hostname,
port, credentials, and optional datacenter scope.
Discover workloads
XMS inventories all reachable VMs, disks, networks, and guest metadata
through the vSphere API. No agent is installed in the source guest.
Run preflight
Each candidate workload is scored for OS support, firmware type, disk
layout, and driver availability. Blocking issues are surfaced before
scheduling a migration.
Submit migration
Choose cold (single-pass) or warm (continuous sync) mode, pick the target
Xloud project, network, and volume type, and queue the job.
Sync and cutover
Cold migrations run end-to-end immediately. Warm migrations complete a
full sync and then incrementally replicate until you trigger cutover.
Supported VMware Environments
vCenter Server
Connect to vCenter to discover and migrate VMs across all managed clusters
and hosts from a single source entry.
Standalone ESXi
Connect directly to an individual ESXi host for smaller deployments or
edge sites that do not run vCenter.
vSphere 6.x – 8.x
Covers vSphere 6.0 through 8.0. The migration service bundles disk transport
libraries for each supported generation.
BIOS and UEFI Guests
Both BIOS and UEFI guests migrate to Xloud without firmware-specific
preparation. Secure Boot status is detected during discovery.
Related Services
Xloud Compute
Migrated workloads run as Xloud Compute instances with full lifecycle and
scaling features.
Block Storage
Target disks land as Xloud Block Storage volumes. Choose volume types to
place migrated workloads on the correct storage tier.
Infrastructure Monitoring
Monitor migrated workloads with XIMP dashboards, metrics, and alerting.