# How a migration works

Know who does what during a migration, and what changes for each machine.

## Who does what

| | Its role |
|---|---|
| **The destination** | Imports the disks with its own import feature. Proxmox VE reads the machine's files on vSphere, and Xen Orchestra imports into XCP-ng. |
| **Naoshift** | Prepares and checks each machine, shuts the source down at cutover and starts the imported machine. It follows the import and records every action. |
| **Your collector** | Carries Naoshift's orders to vSphere and to the destination, with an action account on each side. |

Not a single disk byte goes through Naoshift: the data flows directly from vSphere to the destination, on your premises. The source is never deleted: it stays powered off in vSphere until you decide to remove it.

## A wave, one machine at a time

A **wave** groups machines that go from the same source to the same destination. Each machine follows its own operation within it, and one failure does not stop the others. The destination limits how many machines run at once: 4 to Proxmox VE, 2 to Xen Orchestra. The next ones wait their turn.

## Two modes

- **Cold**, everywhere: the source shuts down, then its disks are copied. The downtime lasts as long as the copy.
- **Live import**, to Proxmox VE and for Linux guests only: the machine starts while its disks are still being copied. I/O is slower meanwhile, and anything written is lost if the import fails. Measured: the downtime is no shorter than cold.

The wizard estimates the downtime of each machine from the size of its disks.

## What changes for the machine

| | To Proxmox VE | To XCP-ng |
|---|---|---|
| Hardware identifier (SMBIOS UUID) | Kept | New: licences bound to it must be moved |
| Virtual TPM | Not carried over: have the BitLocker recovery key at hand | Not carried over: same |
| UEFI boot | An EFI disk is created, boot entries do not follow | The machine is created in UEFI mode |
| Drivers and tools | VirtIO advised, VMware Tools to remove | Xen drivers advised, VMware Tools to remove |

Most of the time, the machine boots without touching its system. Actions inside the guest serve performance, management and networking. The wave's runbook proposes them, machine by machine.

## What does not migrate

The wizard says so before anything starts, machine by machine:

- a machine **encrypted by vSphere**: decrypt it first;
- an **RDM** disk: migrate its data separately;
- a disk on **vSAN** to Proxmox VE: move it to another datastore first;
- an **independent** disk to Xen Orchestra;
- a **template**: deploy from it on the destination.

> Torn between the two destinations? The **Steer and decide** path compares scenarios based on what your estate actually consumes.

### Do I need to install anything on the destination?

No. Import is a native feature of Proxmox VE and Xen Orchestra. Your collector only needs to be up to date.

### Do my machines stay reachable during the preparation?

Yes. Nothing stops before the cutover. Preparation and checks only read.
