Migration Planning¶

This workflow follows the planning screens under the Plan menu in Clarity Transform, from reviewing planning gaps to tracking approvals for each move group. Each stage names the screen, the actions that matter for planning, and the page that documents the screen in full.

The stages follow the order of the Plan menu. Where one stage depends on another, the stage says so.

Stage 1: Review planning gaps¶

Go to Plan → Planning Dashboard. The screen header is Migration Planning Dashboard, with the subtitle "Planning readiness, gaps, and migration status across all CI classes".

The cards NO MOVE GROUP, NOT READY, NO STATUS SET and NO APPROVAL each show a percentage of devices. There is also a CONTAINERS - NO MOVE GROUP card.
The charts include Planning Gaps, Devices by Event and Move Group Distribution.

See Planning Dashboard.

Stage 2: Check migration readiness¶

Go to Plan → Readiness → Migration Readiness. The screen header is Nutanix Migration Readiness, with the subtitle "Assess VM and database compatibility for Nutanix migration".

The Device Readiness tab shows the cards TOTAL VMS, READY TO MIGRATE, REMEDIATION REQUIRED and BLOCKED, the Top Migration Blockers cards and the VM Readiness Details grid.
The Migration Ready column takes the values Ready, Requires Remediation and Failed. The BLOCKED card counts the Failed group.
The SQL Server (NDB) tab gives the equivalent view for databases.

See Migration Readiness.

Stage 3: Check container readiness¶

Go to Plan → Readiness → Container Readiness. The screen header is Container Namespace Readiness, with the subtitle "Assess container namespace migration complexity across OpenShift and Nutanix NKP clusters".

The cards are TOTAL NAMESPACES, LOW RISK, MEDIUM RISK and HIGH RISK.
In the Namespace Readiness Details grid, Migration Readiness takes the values Ready, Complex and Requires Planning, and Migration Risk takes Low, Medium and High.

See Container Readiness.

Stage 4: Check target capacity¶

Go to Plan → Readiness → Capacity Planning. The subtitle reads: "Compare source VMware clusters with target Nutanix clusters, then run a Move Group what-if scenario against a selected target cluster. CPU planning uses the configured max CPU overcommit ratio on target clusters, while RAM and storage remain physical-capacity checks."

Use the EVENT and MOVE GROUP SCENARIO selects to run the what-if scenario for a move group. Reset Scenario is next to them.
The VMware Clusters and Nutanix Clusters panels show each cluster as a card. The table with Name, CPU, RAM (GB) and Storage (GB), and the cluster's own capacity figures, appear only after you expand the cluster's card.
The target cluster is chosen in the scenario. It is not stored on the move group. There are no fixed capacity thresholds: CPU is checked against each target cluster's Max Cpu Overcommit Ratio, and RAM and storage against physical capacity.

See Capacity Planning.

Stage 5: Map source networks to target networks¶

Go to Plan → Source To Target → Network Mappings. The grid columns are Source Cluster Name, Source Network Name, Source Vlan Id, Source Provider Name, Target Cluster Name, Target Network Name and Target Vlan Id.

No button on this screen creates Nutanix Move plans. Plans are created on Execute → Migration Operations → Migration Jobs, from a move group.

See Network Mappings.

Stage 6: Create migration events¶

Go to Plan → Events. The screen header is Migration Events. The subtitle reads: "A migration event represents a scheduled window or task during which specific applications, servers, or workloads are moved from their current environment to a new one."

To create an event, select the add icon on the grid toolbar. The Create new entry form opens with Name, Start Date (required), End Date (required), Status and Notes. Status offers Completed, In Planning and In Progress. Select Save.
The grid includes Name, Start Date and End Date. Completed events are hidden until you select Show completed. Each row has the row actions View Details and View T-minus Runbook.
Select an event's Name to open Plan → Move Groups filtered to that event's move groups.
Automation Wizard opens the Event & Move Group Automation dialog, with the fields First event start date, Event end day, Cadence (weeks), Number of events, Name pattern, Target events, Grouping strategy, Distribution, Move group name pattern and Rule sets.
Target Mapping and Missing S2T Networks are downloads for the selected events. Select the event rows first.
Lock Event opens a dialog that reads "You are about to lock N event(s).", with the checkbox Send the migration confirmation email to migration contacts (unchecked) and the buttons Cancel and Lock Event.
Unlock Event is also on the toolbar. It asks for no confirmation: it unlocks the selected events at once and clears Locked By and Locked On.
Lock Event, Unlock Event and the downloads act on the event rows you clicked. Clear selection does not reset them; click a row again to deselect it, or reload the page.
View T-minus Runbook opens the event's T-Minus runbook page. Create the event's T-Minus runbook here: select Generate Runbook from Template, choose a Template and set the Target Cutover Date (T=0). Generating creates the runbook and its tasks. The T-Minus Runbooks screen has no Create New; it is where you track the runbooks across events afterwards. You can also work the event's tasks on this page, with Start Task and Mark as Complete. See Generate a T-Minus runbook for an event and Work an event's T-Minus tasks.

Move groups and cut-over runbooks are linked to an event by their own Event Name field.

See Events.

Stage 7: Build move groups¶

Go to Plan → Move Groups. The screen header is Move Groups Summary. The subtitle begins: "A move group is a collection of assets that are planned to be migrated together as a single batch."

To create a move group, select the add icon on the grid toolbar. The Create new entry form opens with Move Group, Description, Event Name, Migration Date (required), Workflow Stage and Notes, and below them the guard-rail rule builder with six locked system default rules. Event Name lists the migration events, so the event must exist before a move group can be linked to it. Select Save.
The grid includes Move Group, Event Name and Migration Date. Move groups with the Status Migrated are hidden until you select Show Migrated on the Actions menu.
The Actions menu holds Refresh Stats, Sync Migration Data, Show Migrated, Mark Ready to Migrate, Mark Migrated, Check Dependencies and Send Approval.
Mark Ready to Migrate validates the move groups first. If validation fails, the status is unchanged and Migration Readiness Issues lists the problems.
Send Approval opens the Send Approval Request dialog, which has no fields, lists the selected move groups, and has the buttons Cancel and Send Approval Request. Select the move group's row first: Send Approval and Check Dependencies are greyed out until a row is selected.
Send Approval needs an SMTP profile or Teams notifications, set up on Settings → Communications. Without one it is greyed out, with a message that refers to Settings → Notifications.
Kanban Board shows the move groups as a board, one lane per workflow stage. Drag a card to another lane to change its Workflow Stage.

The grid remembers its Search: text, column filters, sort order and page size between visits. If the grid shows fewer rows than you expect, clear the Search: box and the filter row.

A device is placed in a move group through its Move Group field. In the device's Edit entry form, Move Group is a list of the move groups. To add assets in bulk, select the move group's name in the Move Group column: the move group's page opens, and its add button opens a picker. This is not available for a move group whose event is locked. See Add assets to a move group. You can also edit several devices at once on Discover → CMDB: select the Device card and use Enable spreadsheet editing. The Device grid has no Import CSV button.

See Move Groups.

Stage 8: Track business approvals¶

Go to Plan → Business Engagement. The subtitle reads: "Track approval emails, read receipts, and meeting bookings per application owner across your migration event."

Approvals are sent from Plan → Move Groups first, using Send Approval under Workflow on the Actions menu. Until then, the screen shows "No approval requests found. Send approvals from the Move Groups page first."
Use the Event select to choose All Events or one event.
To record a decision by hand, select the rows still awaiting a decision, then Record Approval or Record Rejection in the grid toolbar. A Note is always required, and a rejection also needs a Rejection Reason.
To arrange a meeting with an owner, use the row button Schedule Meeting (it needs an SMTP profile), or Mark Booked when the meeting was arranged without an invite.

The Business Engagement and Approvals workflow covers this stage in full, from the email set-up to locking the event.

See Business Engagement.

Runbooks: runbooks built from move groups, under Execute → Migration Operations → Runbooks.
T-Minus Runbooks: the T-Minus runbook linked to each event.
Migration Jobs: create Nutanix Move migration plans from a move group.
Event Command Center: monitor an event's progress.
RAID Log: risks, assumptions, issues and dependencies across migration events.