Skip to main content

​
Overview

Before a new source can be registered or a new migration can run, the operator must satisfy a small number of platform-side, project-side, and source-side prerequisites. This page lists them in the order you should check them.

​
Platform Prerequisites

nxtMove is enabled on the NxtSight platform

The Migration panel must be visible in the NxtSight Dashboard and the nxtMove CLI subcommand must be installed on operator workstations. If neither is available, nxtMove is not enabled on the deployment — contact NxtSight support.

Identity service is healthy

nxtMove validates every API call against the platform identity service. If identity is unhealthy, source registration and job submission will fail. Confirm the platform health dashboard reports identity as reachable.

Block Storage and Compute are healthy

nxtMove writes migrated data through block storage and launches target instances through compute. Both must be healthy before any migration can run.

​
Project Prerequisites

Each target NxtSight project that will receive migrated workloads needs:
For multi-wave campaigns, create a dedicated target project per wave. This keeps quota accounting simple and isolates waves from each other.

​
Source Environment Prerequisites

​
VMware vCenter

​
Standalone ESXi

Standalone ESXi is supported for lab, edge, and small-site migrations. The same transport library and pipeline apply — the only differences are:
  • Endpoint is the host address instead of a vCenter
  • Username is typically root or a local ESXi user
  • Datacenter is auto-detected as ha-datacenter

​
Guest-Side Requirements

​
Operator Access

The operator installing or maintaining nxtMove typically needs:
  • Administrative role on the NxtSight platform (for installing, updating, and scaling nxtMove)
  • Read or admin role on every target project that will receive migrations
  • Credentials to register source environments (either shared service accounts or per-source accounts)
  • Access to platform monitoring to track nxtMove health

​
Pre-Onboarding Checklist

Use this checklist before onboarding a new source:
  • Identity service reachable and healthy
  • Block storage reachable and healthy
  • Compute reachable and healthy
  • nxtMove visible in the NxtSight Dashboard
  • nxtMove CLI installed and authenticated
  • Target project exists in the correct domain
  • Compute quota covers the expected wave footprint
  • Volume quota covers the expected wave footprint (+20% buffer)
  • Volume type published for the intended storage tier
  • Target networks and subnets exist
  • Users who will submit migrations have the right role
  • vSphere endpoint reachable from nxtMove
  • Service account created with the recommended role
  • Role assigned at the datacenter scope
  • TLS fingerprint or CA chain available if TLS verification is required
  • CBT enabled on every VM in the warm migration wave

​
Next Steps

Source Credentials

Build the service account and role for nxtMove

Network Ports

Open the right ports between nxtMove, source, and target

Register Source

Add the source to nxtMove once prerequisites are met