← All guides

System migration guide

Discover and move an existing estate from A to B

Use Migrations when the source of truth is an existing provider, Kubernetes cluster or server—not an AnchorScape release. Source and destination are independent, so the intended model is cloud-to-on-prem, on-prem-to-cloud and cloud-to-cloud.

Result: A reviewed system inventory and migration plan with explicit data, cutover, verification and rollback work.

Discovery comes before movement

  1. 1Open Console → Migrations and choose the source and destination independently.
  2. 2Connect the source with least-privilege discovery credentials or an outbound runner.
  3. 3Run discovery across workloads, images, networking, configuration references, storage, databases, buckets and backup evidence visible to that identity.
  4. 4Review topology, unmanaged “cowboy” resources and unresolved dependencies.
  5. 5Generate the portable release and destination plan.
  6. 6Plan image copy, secrets, data movement, DNS, cutover, verification and rollback before execution.
Discovery cannot see resources the supplied identity cannot read, and a backup is not proven until it has been restored successfully.

Need help on the screen?

Open Anchorton and ask where a setting belongs. For runtime questions, open it from the deployment context so it can use the permitted status, event and log tools.