Move Groups¶

Purpose¶

The Clarity Transform Move Groups screen (header Move Groups Summary) lists the move groups in the plan. Its subtitle reads: "A move group is a collection of assets that are planned to be migrated together as a single batch. Move groups help you organize, schedule, and track migrations, making it easier to coordinate activities and minimize risk during migration events."

Each move group belongs to an event through its Event Name, which takes its values from the events on Plan → Events. Assets are linked to a move group through their own Move Group field, whose values come from the move groups on this screen. Device, Database, Application Service, Container Cluster and Container Workload records in the CMDB have this field. To add assets to a move group in bulk, use the move group's own page (see Add assets to a move group).

Where to find it¶

Plan → Move Groups

What you see¶

Columns¶

Move Group: a link to the move group's own page, which lists its assets.
Event Name
Issues
Number Applications
Number Servers
Number Databases
Number Containers
Number Approved
Number Rejected
Migration Date
Status
Workflow Stage
Move Group Guard Rails: shows a guard-rail badge, for example Custom (2), with the tooltip "Click to view guard rail rules". Selecting the badge opens Guard Rail Rules ("All rules currently applied to this move group"), which lists each rule's Source (Default or Custom), Column, Operator and Value.
Description
Notes

The Issues column can show two badges. Select a badge to see the detail:

The gavel badge (tooltip "Guard rail rule violated") opens Guard Rails Violations, for a move group that breaks its guard-rail rules.
The target badge, with a count (tooltip "N device(s) missing target mappings"), opens Migration Readiness Issues ("Pre-migration validation results for the selected move group(s)").

The grid also has the hidden columns Id, Devices Missing Targets, Devices Requiring Remediation, Last Stats Refresh, Missing Targets Detailed, Missing Targets Device Names, Remediation Device Names, Rule Violated, Guard Rails Violation Details and the audit fields.

The date on a move group is Migration Date. A move group has no target cluster field: on Plan → Readiness → Capacity Planning, the target cluster is chosen in the what-if scenario.

Fields¶

The create form (Create new entry) has these fields, in this order. The edit form (Edit entry) has the same fields, filled in.

Move Group: text.
Description: free text.
Event Name: a list of the migration events on Plan → Events.
Migration Date: a date, required.
Workflow Stage: text.
Notes: free text.

Status and Move Group Guard Rails are hidden in the form, so they can't be set there. The form footer has Cancel and Save.

Guard-rail rules¶

Below the fields, the form has a guard-rail rule builder, with the buttons Add Exception Highlighting Rule and Unlock System Defaults. Each rule is one row with three parts:

a device field, chosen from a list of 108 device fields shown by their database names (for example approval_status or migration_status);
an operator: Equals, Not Equal, Contains or Not Contains;
a value, typed into a box with the placeholder "Value".

The form starts with six system default rules, which are locked (the lock icon's tooltip reads "System default rules are locked"):

approval_status Equals Rejected
migration_readiness Not Equal Ready
scope Not Equal In scope
migration_status Equals Migrated
migration_status Equals Decommissioned
migration_status Equals Dropped

Actions¶

The grid has the standard toolbar: Create New, Edit, Remove selected, Clear selection, Reload table data, Enable spreadsheet editing, Export CSV and Import CSV. It also has:

Actions menu, with its items in three groups:
- Data:
  - Refresh Stats
  - Sync Migration Data
  - Show Migrated: move groups with the Status Migrated are hidden when the page opens. Select Show Migrated to list them too; the item then reads Hide Migrated.
- Status:
  - Mark Ready to Migrate: validates the selected move groups first. If validation fails, the status is not changed and Migration Readiness Issues opens with the problems found. It does not check for pending approvals on Business Engagement.
  - Mark Migrated
- Workflow:
  - Check Dependencies
  - Send Approval: opens the Send Approval Request dialog for the selected move groups. It needs an outgoing channel (see Send Approval Request dialog).
Reports menu, with the downloads Target Mapping and Missing S2T Networks for the selected move groups. It is greyed out until a move group row is selected.
Kanban Board: opens the move groups as a board, one lane per workflow stage. See Kanban board.
Save columns, Load columns, Toggle columns, Validations and Row height.

Send Approval, Mark Ready to Migrate, Mark Migrated and Check Dependencies are greyed out until a move group row is selected.

Send Approval Request dialog¶

The dialog has no fields. It reads "Notify application and device owners for the selected move groups." and "This will send approval requests by email and, when configured, Microsoft Teams." It gives the number of move groups selected and lists up to five of them, followed by "And N more move group(s)." when there are more. The buttons are Cancel and Send Approval Request.

When the requests are sent, Clarity confirms it, for example "Approval requests sent successfully using 3 emails and 2 Teams notifications." Owner fields that are not valid email addresses are listed in an error message, and those items show as Skipped - invalid email on Plan → Business Engagement. The requests use the Migration Approval Request email template (see Email Templates). Contacts ticked for Include In Migration Approval Request on the Project Directory are also notified.

Send Approval needs an outgoing channel: an SMTP profile or Teams notifications, set up on Settings → Communications (see Communications). Without one, Send Approval is greyed out, and its tooltip or message reads "No communication channel configured. Set up SMTP or Microsoft Teams under Settings → Notifications to enable this." The setup screens are under Settings → Communications, although the message says Settings → Notifications.

Check Dependencies opens External Dependencies Analysis for the selected move groups: the cards TOTAL DEPENDENCIES, GROUPS WITH DEPS, INDEPENDENT GROUPS and HIGH RISK, then Detailed Analysis by Move Group. It is a report and changes nothing.

Each row has a View Details row action (the eye icon).

Move group page¶

Selecting a move group's name in the Move Group column opens that move group's own page, which lists the assets in it. The page reads "Select CI's to add to the Move Group." It has the tabs Devices, Databases and Container Workloads, a table view and a graph view, and a grid whose edit button's tooltip is Edit Device Move Groups.

The add button on its grid opens the Populate Move Group dialog, for adding assets to the move group in bulk. In Populate By:, choose whether to add items by application, device or database, then choose the items. Items blocked by the move group's scope guard rail stay visible but can't be selected. The buttons are Cancel and Apply.

If the move group belongs to a locked event, the add button can't be used, and it reads "This move group belongs to a locked event and cannot be populated." To lock or unlock an event, see Events.

Kanban board¶

Kanban Board opens the move groups as a board. The page has the buttons Table View (back to the Move Groups grid), Reset filters and Refresh board, and these filters:

Event (default All events);
Move group (default All move groups);
From date and To date;
Include migrated move groups: a tick box, unticked by default.

Reset filters clears all of them. A line below the filters reads "Showing N of N move group(s) in the board."

Each lane is a workflow stage, with a count of its cards. Each card is a move group, and shows its status, Event, Migration date, its counts as Apps / Servers / Containers / DBs, its Workflow stage, and its description and notes. The card's title opens the move group's page.

Drag a card to another lane to change the move group's Workflow Stage. The board shows "Workflow stage updated." and reloads.

Workflow Stage is a free-text field in the move group form, so a stored value may not match any lane. Such a card shows "Stored stage: " followed by the stored value. Moving the card to a lane replaces the stored value with that lane's stage.

Filters¶

Each column has a filter row, and a Search: box searches the grid.
The page-size selector offers 10, 25, 50 or All entries per page.

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.

Values¶

Status: the dropdown list on Settings → Field Management → Dropdown Lists allows In Planning, Ready to Migrate and Migrated. Records in this build also show Completed, In Progress, Pending Approval, Approved, Planned, Rejected and On Hold.

How to¶

Create a move group¶

Go to Plan → Move Groups.
Select Create New in the grid toolbar. The Create new entry form opens.
Enter the Move Group name, choose the Event Name and enter a Migration Date. Fill in Description, Workflow Stage and Notes if you need them.
To add a guard-rail rule, select Add Exception Highlighting Rule, then choose the field and operator and enter the value.
Select Save, or select Cancel to close the form without saving.

Find the move groups in an event¶

Go to Plan → Events.
Select the event's Name. Plan → Move Groups opens with the Event Name filter set to that event.

Or, on Plan → Move Groups, enter the event's name in the filter row of the Event Name column.

Move groups with the Status Migrated are hidden until you open the Actions menu and select Show Migrated.

Add assets to a move group¶

Go to Plan → Move Groups.
Select the move group's name in the Move Group column. The move group's page opens and lists its assets.
Select the add button on the grid toolbar. The Populate Move Group dialog opens.
In Populate By:, choose whether to add items by application, device or database, choose the items, then select Apply.

You can't add assets to a move group whose event is locked. To place a single device instead, set the Move Group field on the device's record in Discover → CMDB. The Automation Wizard on Plan → Events can also place in-scope, unassigned devices into move groups (see Events).

Change a move group's workflow stage¶

Go to Plan → Move Groups.
Select Kanban Board.
Drag the move group's card to the lane for the new stage. The board shows "Workflow stage updated.".

Send an approval request¶

Before you start, set up an SMTP profile or Teams notifications on Settings → Communications. Without one, Send Approval is greyed out.

Go to Plan → Move Groups.
In the grid, select the move group's row. You can select more than one.
Open the Actions menu and, under Workflow, select Send Approval.
The Send Approval Request dialog opens and lists the selected move groups. Select Send Approval Request to send, or Cancel to close it.
Track the responses on Plan → Business Engagement. See Business Engagement.

For the whole approval route, see the Business Engagement and Approvals workflow.

Mark move groups ready to migrate¶

Go to Plan → Move Groups.
Select the move groups' rows.
Open the Actions menu and, under Status, select Mark Ready to Migrate.

If the move groups pass validation, their status changes. If not, Migration Readiness Issues opens and lists the problems, and the status is left unchanged. Fix the issues and try again.

Events: the events that move groups belong to. Select an event's Name to see its move groups.
Communications: the SMTP and Teams setup that Send Approval needs.
Business Engagement: tracks the approval requests sent from this screen.
Capacity Planning: runs a move group what-if scenario against a selected target cluster.
Planning Dashboard: shows devices with no move group and the move group distribution.
Migration Jobs: a Nutanix Move migration plan is created from a move group.
Runbooks: runbooks are created for one or more move groups.
Event Command Center: progress per move group for an event.