Prepare the source and the destination
Prepare the accounts, flows and room that are most often missing.
Two action accounts, never the collection account
The collection account stays read-only and never leaves Naoshift. A migration uses the action account on each side: in Data sources, open the settings of the source, then fill in Action account.
Once both capabilities are ticked, Settings › Infrastructure actions › Write access gives the exact privileges for each platform, with a ready-to-paste script. In short:
| Side | What the account must be able to do |
|---|---|
| vSphere (the source) | Power the machine off (VirtualMachine.Interact.PowerOff), and let its disks be read (Datastore.Browse, VirtualMachine.Provisioning.GetVMFiles, VirtualMachine.Provisioning.DiskRandomRead). Naoshift hands it to the destination, which reads the disks with it. |
| Proxmox VE | Create and configure the machine (VM.Allocate, VM.Config.*), allocate storage (Datastore.AllocateSpace, Datastore.Audit), use networks (SDN.Use), read the guest agent (VM.GuestAgent.Audit, or VM.Monitor on Proxmox VE 8). It also needs Datastore.Allocate on /storage, for the temporary import storage. |
| Xen Orchestra | A Xen Orchestra administrator account: its VMware import feature requires it. |
Proxmox VE: an ACL set on
/storagereplaces, below it, what/grants. Give it the account’s main role too, otherwise storage disappears from its rights.
The flows
The destination reads the disks at the address of the source declared in Naoshift, vCenter or ESXi host.
| From | To | Port |
|---|---|---|
| Each Proxmox VE node | The vSphere source | TCP 443 |
| Xen Orchestra | The vSphere source | TCP 443 |
| Xen Orchestra | The ESXi host that carries the machine | TCP 902 |
Your collector already reaches both sides: it collects them.
The destination’s certificate
Following the import requires Naoshift to verify the destination’s certificate. Tick TLS verification on the Proxmox VE or Xen Orchestra source. If its certificate comes from an internal authority, install that authority on the collector’s machine, restart the collector, then run a collection again.
Room on arrival
- Storage: the wizard compares the size of each disk with the free space read by the latest collection. On Xen Orchestra, all the disks of a machine go to the same storage.
- Network: each network adapter of the machine plugs into a collected network of the destination. Check that your machines' VLANs exist there before the wave.
- Memory: the wizard adds up the memory of the wave’s machines on each landing host.
If you get stuck
All machines stay blocked, with two messages about accounts
The source has no action account and The destination has no action account: no action account is declared on one side or the other. Declare them, then open the wizard again.
The import starts, then the migration stops
Most often, TLS verification is not ticked on the destination: following the import is then refused. Tick it, after installing the authority that signed the certificate.
Proxmox VE’s import storage stays inactive
The source account cannot read the datastore, or the nodes cannot reach the source on port 443. The reason shown on the machine says which.
The source is a free ESXi
Its API refuses to power off a machine. The migration stops at that step and says so: power the machine off by hand on the host, then start it again.
Go further
Try it on your estate
Naoshift Core, 30-day free trial. No credit card, no commitment.
Start my free trial