VMCloudlinerWorkloads without borders.
Dansk · English · FlightDeck

FLIGHT MANUAL

From your first account to a planned migration

A simple guide to source, target and next steps. Updated 13 October 2026.

Pilot: download packages provide discovery. Continuous replication and full Windows migration are not yet generally released.

Get started in 6 steps

  1. Create an account and follow the confirmation email. Choose and repeat a password of at least 12 characters.
  2. Create a project in FlightDeck. Start with a test machine and keep a verified backup.
  3. Download the agent under Downloads. Create an agent enrollment code in FlightDeck and run the installer as administrator on the source.
  4. Create a separate target VM using the helper ISO, a 1 GiB state disk and empty target disks. Enroll the helper with a helper code.
  5. Check that source and helper are online. In Flight Plans select project, source and all required disks. Check disk identities and capacities.
  6. Open the Flight and follow the portal checks. Start sync only when the specific pilot job is approved. Missing actions mean the feature has not yet been released for that job.

One-time clone: copy without ongoing sync

  1. Choose One-time clone to helper in your Flight Plan if you want one copy and will handle the remaining work yourself. This is a limited pilot, not a publicly released conversion.
  2. Pair each selected source disk with the correct target disk in the portal. Check disk identity and capacity. Source and target CPU and RAM need not match. Preserve the helper state disk.
  3. The current OS clone pilot supports one physical BIOS/MBR disk with 512-byte sectors and NTFS. Multiple disks and GPT/UEFI require separately validated support. Use the approved pilot packages; the public discovery packages cannot perform the clone.
  4. Follow the Flight source and target checks and start copying through the portal. The copy comes from one retained snapshot. Later source changes are not included, even while the source keeps running. The pilot snapshot window totals at most 120 minutes.
  5. Wait for Copy ready for manual handoff. This requires full target readback and verification, release of the source snapshot and safe closure of helper writes. A completed transfer alone is not enough.
  6. Shut down the helper normally before changing attached disks or boot media. Start the clone isolated from the source. You handle boot, drivers, networking and validation of applications and data. A one-time clone does not perform live sync or cutover.

Source requirements

  1. The public Windows agent is a discovery release: it registers the machine and reports system information. It is not the private live-sync agent.
  2. The Windows package requires .NET Framework 4.6.2+, PowerShell 2+ and TLS 1.2. Server 2008 R2 SP1 has been tested in the lab. Other Windows versions require separate validation before migration.
  3. Install as administrator. The agent runs as a Windows service under LocalSystem. The source needs HTTPS access to the portal; the data connection to helper or transit must be validated separately.
  4. Select every disk required by the operating system and applications. Check capacity, application requirements and the agreed cutover window.

Target and helper requirements

  1. Use a separate VM and empty target disks. Targets can be overwritten during an authorized migration. Never select the helper state disk as a target.
  2. Each target disk must fit its selected source disk, not just its used files. Check the exact byte capacity in the portal.
  3. Hyper-V is the current lab platform. BIOS/UEFI and boot drivers must suit the future Windows VM. Other hypervisors and automatic VM creation are on the roadmap.
  4. The public helper ISO provides discovery. The private DATA live-sync pilot and OS boot acceptance are separate stages and are not generally released.

Understand status and cutover

  1. Online means the device sends heartbeats. It does not mean the data is synchronized.
  2. Take-off is the first full transfer with target verification. Progress percentage applies to this stage. Several TB may take days depending on bandwidth.
  3. Automatic snapshot sync runs repeated rounds. Continuous replication is a separate feature with queue, lag and received-data measurements. Waiting does not mean active transfer.
  4. At cutover, selected services must stop, the final consistent sync must be checked, and source shutdown confirmed before activating the target. Test in isolation first and validate applications and data. Follow the approved portal flow.

If something stops

  1. If offline, check power, networking and the agent service. Do not include enrollment codes or passwords in support messages.
  2. If paused or failed, read the requested action under Flights. Open Activity for details. Do not delete snapshots, journals or the state disk to force a job forward.
  3. Complimentary Flights only change your allowance. They do not bypass technical checks. Sandbox points are test points and are not real payment.