Overview

This guide assumes you are familiar with cloud migration concepts and want a direct path through Clarity Migrate without the detailed explanations. Follow these five steps to go from zero to a running migration event.

New to Clarity Migrate? Read the module guides for Integrations, CMDB, and Migration Events first.

Prerequisites

  • Administrator or Project Manager role in Clarity Migrate
  • Network access to at least one data source (RVTools export, Nutanix Prism, or CSV)
  • Target infrastructure details (cluster names, network mappings)
  • Migration project scope defined (which VMs / applications move when)

1. Connect Your Data Sources

Import your infrastructure inventory using one or more integrations.

1
Go to Discovery → Integrations and select your source type (VMware / RVTools, Nutanix, CSV, or Azure/AWS).
2
Upload the exported file or enter your API credentials. Run the import. Clarity Migrate parses the data and populates the CMDB automatically.
3
Check the import summary for warnings. Resolve any duplicate hostnames or missing mandatory fields before proceeding.
Run multiple integrations to build a complete picture. RVTools covers VMware, Nutanix Prism covers compute, and CSV handles anything else.

2. Review CMDB Inventory

Validate your imported assets before building the migration plan.

1
Go to Discovery → CMDB → Devices. Confirm device counts match expectations. Filter by Import Source to see what came from each integration.
2
Open Applications and link applications to their host devices. Use bulk-edit for large estates.
3
Run the Data Quality workflow (Settings → CMDB Field Management) to catch missing owners, environments, or locations.

3. Set Up Governance

Create the project's governance artefacts before planning begins.

1
Governance → RAID Log: Add your known risks, assumptions, issues, and dependencies. Assign owners and target resolution dates.
2
Governance → Actions: Create any pre-migration tasks and assign them to team members.
3
Optionally add a Risk Register entry for each high-severity RAID item so it can be tracked on the migration dashboard.

4. Plan Your Migration

Group assets into move groups, create a migration event, and assign a T-Minus runbook.

1
Planning → Move Groups: Create logical wave groups (e.g. Wave 1 – Dev, Wave 2 – UAT). Add devices and applications to each group.
2
Planning → Events: Create a Migration Event. Set the scheduled date, select the move group, and assign the target cluster.
3
Planning → T-Minus Runbook Management: Attach a runbook template to the event. Review all T-Minus tasks and confirm owners are assigned.
4
Check Readiness → Capacity Planning to confirm the target cluster has sufficient CPU, memory, and storage headroom.
Do not proceed to execution until all T-Minus tasks in the Pre-Migration phase are marked complete and the event status shows Ready.

5. Execute & Monitor

1
Execution → Nutanix Move: Confirm migration jobs have been created in Nutanix Move and are synced back to Clarity Migrate.
2
Open the Execution → Command Centre on migration night. Use it as your single pane of glass — track task progress, mark T-Minus actions complete, and log issues in real time.
3
After the event, record outcomes in Governance → Lessons Learned and close any open RAID items.

Next Steps

Integrations
Deep dive into VMware, Nutanix, and CSV import options.
Migration Planning
Detailed guide to events, move groups, and capacity planning.
Command Centre
How to use the live execution dashboard on migration night.