Migration Plans & Steps

Once the Migration Blueprint is approved, the Control Plane translates it into a Migration Plan — a live, auditable record of every step being executed in real-time.

Idempotent Steps

Every step in a Migration Plan is designed to be idempotent. This is a critical engineering guarantee: if a step fails halfway through due to a network disruption or a temporary cloud provider outage, the system can safely retry it from the beginning of that step without corrupting the overall state of either the source or target server.

A standard migration plan is composed of steps like:

Step	Description
Verify Capacity	Checks that the target server has sufficient free disk space for the incoming data.
Provision Dependencies	Installs the required application runtime and system packages on the target.
Issue SSL Certificate	Provisions and validates the SSL certificate on the target before the cutover.
Open Secure Tunnel	The source and target Agents negotiate an encrypted peer-to-peer data channel.
Initial Data Sync	Begins the background bulk transfer of files or database snapshots over the tunnel.
Delta Cutover	Syncs only the changes that occurred since the initial sync, then executes the DNS switch.

Live Progress Tracking

As the migration runs, the RasnuOS dashboard displays the Migration Plan as a live, interactive checklist. Each step transitions through states: Pending → Running → Completed (or Failed).

You can click on any individual step that is currently executing and watch the raw command output stream line-by-line via WebSocket in real-time. You have total visibility into exactly what the system is doing at every moment — without SSH access, without log files, and without guessing.

Pausing & Resuming

For planned maintenance windows, you can manually pause a running migration at the end of any step. The source server continues to operate normally. When you are ready to resume — even days later — the Migration Plan picks up exactly where it left off.