Build the runbook
Decide on each machine’s actions before launching the wave.
Three phases around the cutover
The runbook is the list of steps each machine goes through. It is the first tab of a wave’s page, Runbook. The How the migration runs, and what the runbook is for box sums it up as a timeline:
| Phase | When | Examples |
|---|---|---|
| A · Before the source is shut down | The source is still running | Record the network settings, install the VirtIO drivers on Windows, remove the VMware Tools last, application owner’s go-ahead, backup verified |
| Cutover | Naoshift shuts the source down, the destination imports its disks | The source is never deleted |
| B · Before the first boot | The machine is imported, powered off | Destination hardware fitted to the guest, offline actions on its disk |
| C · After the first boot | The machine runs on the destination | Guest agent answers, network settings re-applied, destination guest tools, VMware Tools gone, final check |
Naoshift proposes the steps each machine’s inventory calls for, each with its reason: system, network adapters, destination. It never decides from a platform’s name.
Who does each step
Each step carries a badge:
- Naoshift checks: Naoshift reads what it already knows, without touching anything;
- Naoshift: Naoshift does it, and keeps the proof;
- Inside the guest: the step runs inside the machine, with its account;
- You: you do it, then you tick it.
The steps
- In the wizard, the Runbook step already shows what Naoshift will propose, phase by phase. When a step is yours, or runs inside the guest, the wizard recommends Prepare the runbook first, launch later.
- On the wave’s page, review the proposed steps. Keep, remove, reorder within a phase, or add a manual step with Add a step.
- Make a step blocking if the migration must wait until it is ticked, optional otherwise.
- If steps run inside the guests, fill in the account under Account inside the guests of the source.
- The What is left to do card, at the top of the page, says what is still missing. Once nothing is, launch the wave: the runbook is frozen at that moment, and each machine leaves with its own list.
The account inside the guests
Phase A steps that run inside the guest need an administrator account, or root (or sudo without a password) on Linux. Set it for the whole wave, or for one machine. It is encrypted, never shown again nor written to a log, and erased at the end of the wave.
Access goes through SSH from your collector. The password only goes to a pinned host key: the first step run without a pin is refused, and reports the key to pin. The VMware Guest Operations way is offered, but not proven yet.
After the first boot, actions go through the destination’s guest agent, when it has one. What they are missing shows under What the runbook is missing.
To Proxmox VE, some actions are done offline, on the imported machine’s disk, with no account inside the guest. When your installation allows it, the screen offers them instead of the equivalent actions inside the guest.
During the wave
The Machines and phases grid shows where each machine stands, phase by phase. A Waiting for you cell flags a blocking manual step to tick: Done or Failed, with a comment if it failed. A blocking step that fails before the shutdown stops the migration with nothing touched.
Overriding a blocking step, with Waive, takes a company administrator and a reason, kept in the audit trail. So does exempting a machine from a step, with Exempt.
If you get stuck
The runbook says something is missing
The What the runbook is missing list says what, and who lifts it: Naoshift, you in this wave, or a company administrator.
A useful step is not available
Under Also relevant, not available yet, the screen lists what would help without being offered yet. Meanwhile, do it by hand, and add it as a manual step.
Do I need a runbook to migrate?
No. Without actions, the machine is imported as is, and most often boots. The runbook makes the cutover predictable: network, drivers, approvals, backup.
Go further
Try it on your estate
Naoshift Core, 30-day free trial. No credit card, no commitment.
Start my free trial