Migration control and orchestration

Less risk.
More control.

Clarity is the orchestration platform that plans, executes and governs data center and cloud transformation, from the first discovery scan to the final cutover.

VMware exitData center migrationCloud migrationHybrid consolidationContainer platforms

The problem Clarity was built to remove

Large migrations fail on sequencing, not on tooling.

Spreadsheets as the inventory

Four versions of the server list. Nobody knows which is current, or where a row came from.

Disconnected trackers

Dependencies in one tool, risks in another, approvals in email. The picture only exists in someone's head.

Static runbooks

Typed up once, out of date by the second change. The document becomes a liability the night of the cutover.

One governed platform

Every team works from the same plan and every decision is visible.

Inventory one normalized record set, source kept on every asset

Dependencies move groups built on evidence

Runbooks generated from the data, regenerated on change

Execution through the migration tools you already own

Governance risks, approvals and audit attached to the workload

Deployment inside your environment, under your controls

How Clarity works

Six stages. One platform runs the whole program.

Discover

One normalized repository built from your CMDB, hypervisor platforms, existing discovery tools and the ClarityLite assessment. Every record keeps its source.

vCenterPrismSCVMMServiceNowDevice42CSV

Assess

Every application profiled by size, utilization, operating system and role, then given a disposition. Rationalize before you move; migrate only what earns its place.

RehostReplatformRefactorRetainRetire

Plan

Dependency mapping, move groups and waves, with what-if simulation so sequencing is built on how the estate actually behaves.

Network flowMove groupsWavesWhat-if

Execute

Generated runbooks with T-minus sequencing drive Nutanix Move, HCX, AWS MGN and Transform, Azure Migrate, Veeam, Rubrik and Carbonite through their APIs.

RunbooksAnsibleNutanix MoveHCX

Govern

RAID log, approvals, command center views and a full audit trail. Every decision visible; every action attributed to a person or a tool.

RAIDApprovalsAudit trail

Retain

Keep Clarity running after cutover as your CMDB. The validated inventory and dependency picture stay current instead of being thrown away.

CMDBContinuous update

Clarity plans, sequences and governs the migration and drives execution through the engines you already own. It never replicates a workload itself.

Stage 1Discover: data ingestion and aggregation

Know the estate before anything moves.

Sources of truth you already own

vCenterhosts, clusters, VMs, perf

Nutanix Prismcluster, workload inventory

SCVMMHyper-V hosts, guests, storage

OpenShift / Kubernetesclusters, namespaces

Pure Storagearrays, volumes, host maps

ServiceNow CMDBapps, owners, services

Device42discovered infra, deps

CSV / spreadsheetsestates outside a CMDB

ClarityLite scanagentless sizing & readiness

Citrix / Omnissadelivery groups, VDI pools

Connectors

API read-only pulls over each tool's native API
Refresh scheduled and on-demand re-collection
Agentless nothing installed on the workloads
In-network runs inside your environment; data stays put

Normalize and reconcile

1  Parse and map to CI classesschema
Server, Application, Database, Cluster, Host, Storage volume, Delivery group, Dependency.
2  Match and de-duplicateidentity
Keys: hostname, FQDN, IP, MAC, hypervisor UUID, serial. Same machine seen by three tools becomes one record.
3  Resolve conflictsprecedence
Per-attribute source precedence: platform for sizing and OS, CMDB for ownership, scan for utilization.
4  Detect gapsquality
Missing owner, environment, criticality or maintenance window flagged, not silently defaulted.
5  Keep lineagetrust
Every attribute records where it came from and when, so the inventory is trusted rather than argued over.

One normalized repository

0

servers and VMs

0

applications

0

databases

0

dependencies observed

Duplicates resolved0 records

Conflicting attributes reconciled0

Gaps flagged for follow-up0

Records with full source lineage100%

Continuously updated: a re-collection changes the record, not the plan built on it, unless a change is material.

Reconciled record srv-fin-app-013 sources · 1 conflict resolved · 1 gap

os = Windows Server 2016 ← vCenter

vcpu/ram = 8 / 32 GiB ← vCenter

p95 cpu = 23% ← ClarityLite

app = Finance Ledger ← ServiceNow

owner = j.patel ← ServiceNow (CMDB wins over CSV)

maint_win = missing → flagged

09:41:02 vcenter-dc1 pulled 2,318 VMs, 96 hosts, 11 clusters

09:41:19 servicenow pulled 637 apps, 512 owners, 88 services

09:41:44 claritylite loaded scan 2026-09-12 (30-day utilization)

09:42:03 reconcile matched 1,186 duplicates on uuid+fqdn

09:42:08 quality 418 gaps · notifications sent to 41 owners

Stage 2Assess: data quality, profiling and disposition

Rationalize before you move. Migrate only what earns its place.

Application data quality

637 applications

Completeness0%

Consistency across sources0%

Freshness (collected < 7 days)0%

Missing data by attribute

Operating system6 missing

Application owner51 missing

Environment (prod / non-prod)140 missing

Business criticality229 missing

Maintenance window376 missing

Gaps are surfaced here, at the stage where they are cheapest to fix, rather than discovered on the night of a cutover.

Workload profile

Every workload profiled on the same reconciled data.

Size: vCPU, RAM, disk

Utilization: p50 / p95

OS and version

Role: web, app, DB

Compliance constraint

Licensing footprint

Disposition by application

637 total

Rehost lift and shift, right-sized0

Replatform OS or DB upgrade in flight0

Refactor containerize or modernize0

Retain stays in place, documented0

Retire decommission, never migrate0

146 applications will never be migrated. That is scope, cost and cutover risk removed before a single wave is planned.

Component end-of-life risk

Surfaced from OS and database versions across the estate.

Windows Server 2012 R2

extended support ended

96

servers

RHEL 7

maintenance support ended

58

servers

SQL Server 2014

extended support ended

22

instances

Oracle DB 12c

out of premier support

9

instances

What the assessment produces

A defensible baseline before any plan is written
Sizing for the target platform with right-sizing applied up front
A disposition per application that the business has signed off
Risk removed at the stage where it is cheapest to fix

Stage 3Plan: dependency mapping and move groups

Understand what moves together.

Move group MG-14 · Finance Ledger

Wave 3

0

servers in group

0%

completeness score

10

unresolved inbound

Built from how the estate behaves: network flow, application configuration and infrastructure relationships combined.

Evidence behind each link

observed network flow configuration reference runs-on (infrastructure) loose link, spanned

Direction, protocol and frequency on every edge, so a 4,000-connection-a-day database link and a once-nightly batch feed are treated differently.

Unresolved inboundrpt-svc-03 → fin-db-01

An unclassified reporting service reads the ledger database 640 times a day. It is visible now, before the wave is fixed, not after. Owner asked to classify or add to MG-14.

What-if: Finance to Wave 2

simulating…2 consequences

· CRM platform depends on the Finance API in the same window: 3 CRM servers must join Wave 2 or the interim path is extended by 6 weeks.

· Wave 2 capacity on AHV-PROD-02 rises to 91% of planned headroom.

Decision Keep Finance in Wave 3. Recorded to the RAID log with rationale.

Toolchain integrations

Clarity sits at the center of the toolchain. It replaces nothing that works.

Sources of truth

where Clarity reads the estate

ServiceNowDevice42vCenterPrismSCVMMOpenShift / KubernetesPure StorageCSV import / exportClarityLite

Applications, owners and services arrive already mapped; performance data arrives with the VMs; storage dependencies sit alongside compute.

Automation brokers

carry out the runbook tasks

Red Hat AnsiblePuppetMicrosoft System CenterAltirisSpectro Cloud Palette

Playbooks fire as runbook steps; configuration state and compliance report back; target Kubernetes clusters are provisioned as tasks.

Migration engines

the movers Clarity sequences

Nutanix MoveVMware HCXAWS MGNAWS TransformAzure MigrateVeeamRubrikCarbonite

Replication, switchover and launch state tracked per workload. Backup and restore points confirmed before a workload is allowed to move.

Targets

where the workloads land

Nutanix AHVVMware vSphereAWS EC2AzureHyper-VRed Hat OpenShiftKubernetes

Each workload mapped to a cluster, instance type or namespace with right-sizing applied up front, including OpenShift Virtualization for workloads leaving VMware.

End-user computing

CitrixOmnissa

Delivery groups and VDI pools in the dependency map.

People and notifications

SMTPConfluenceSharePoint

Assignments, approvals and cutover alerts to owners.

A runbook step, as the tools see ittask 7 · MG-14 · fin-app-01

→ Nutanix Move POST /move/v2/plans/{id}/cutover { vm: "fin-app-01",target: "AHV-PROD-02" }

← 202 Accepted job 8841 · state: "seeding" · progress 0%

← 200 OK job 8841 · state: "cutover_complete"

→ Ansible POST /api/v2/job_templates/validate/launch { limit: "fin-app-01" }

← 201 Created job 5120 · status: runningsuccessful · 14 checks passed

→ ServiceNow PATCH /change_request/CHG0041873 { state: "implemented" }

Clarity task 7 complete · attributed to jobs 8841 / 5120 · audit written

Clarity moves nothing itself. The engines you already own do the replication. Clarity decides what, when and in what order, and records the outcome.

Stage 4Execute: two runbooks, one governed sequence

From an agreed plan to a completed migration.

1 T-minus runbook · the lead-up plan

passed · execution released

T-30

Wave confirmed · owners briefed · change raised

Program lead

T-14

Target sized on AHV · network design signed off

Migration engineer

T-7

Backup points confirmed · pre-checks run · initial seed

Automated

T-2

Comms sent · cutover window booked

Service desk

Go / No-Go

final checkpoint

✓ all predecessor tasks complete

✓ dependencies resolved (MG-14)

✓ approvals recorded · j.patel

✓ backups and rollback path confirmed

2 Execution runbook · generated task graph, every node has an action

tool trigger human acknowledgement automated check tracking · node by node complete plan change → only affected tasks regenerate

Stage 5Govern: RAID, approvals and the audit trail

Governance lives in the delivery data, not in a separate deck.

RAID log

attached to the workloads they affect

0

Risks open

0

Assumptions

0

Issues

0

Dependencies

R-031 Unresolved inbound from rpt-svc-03 to fin-db-01MG-14 · owner j.patel

I-009 Maintenance window missing on 376 serversWave 3 · owner PMO

D-018 CRM cutover depends on Finance API interim pathWave 3 → 4

Approvals

MG-14 go / no-go · j.patelapproved 21:14

Wave 4 scope change · steering boardpending

Retire 75 applications · business owners71 of 75 approved

Rules-based controls: a workload cannot enter a cutover window without its backup confirmed, its dependencies resolved and its owner's approval recorded.

Command center

one view for every stakeholder

Wave 1 · Non-production · 212 serverscomplete

Wave 2 · Shared services · 388 serverscomplete

Wave 3 · Finance and HR · 641 servers0%

Wave 4 · Customer platforms · 920 servers0%

Wave 5 · Remaining estate · 1,140 serversplanned

Program leads

Status, risk and decisions across every wave.

Migration engineers

Move groups, runbooks, execution through the tooling.

Application owners

Approve, schedule, and see exactly what happens and when.

Delivery partners

Their own roles, permissions and reporting on the same platform.

Audit trailevery action attributed

20:58:02 a.morgan opened cutover window RB-14-03

21:00:11 veeam restore point confirmed fin-app-01 (job 77120)

21:01:04 servicenow CHG0041873 → implement

21:03:40 ansible precheck.yml successful · 21/21 (job 5102)

21:04:02 nutanix-move delta sync started · 3 VMs (job 8841)

21:13:55 nutanix-move sync complete · rpo 0s

21:14:31 j.patel approved go / no-go MG-14

21:15:02 ansible quiesce.yml successful (job 5108)

21:33:18 nutanix-move cutover complete · 7 VMs on AHV-PROD-02

21:37:44 ansible network.yml successful · 7 records updated

21:46:10 ansible validate.yml successful · 14/14 (job 5120)

21:46:12 clarity task 41R rollback path released

21:46:20 smtp cutover notice sent · 41 recipients

21:46:21 clarity RB-14-03 closed · runbook template updated for Wave 4

Exported to SharePoint as evidence. Reusable as the Wave 4 template, so every migration is smarter than the last.

Stage 6Retain, and where to start

The inventory outlives the program.

Retain Clarity as your CMDB

After cutover the validated inventory, dependency picture and lineage keep updating from the same connectors. The most accurate view of the estate you have ever had is not thrown away at go-live.

Deployed inside your environment

1 Never a shared cloud service
2 Estate data stays within your network
3 Your security and access controls apply
4 No vendor access without consent

Start small with ClarityLite

An agentless scan of your VMware, Hyper-V or Nutanix estate. A sizing and readiness report the moment it completes, no commitment.

Less risk.
More control.

Built by the practitioners who run large-scale migration programs, and refined on them.

claritytransform.com

Request a demo · Request a ClarityLite assessment

Less risk.More control.

Large migrations fail on sequencing, not on tooling.

Spreadsheets as the inventory

Disconnected trackers

Static runbooks

Every team works from the same plan and every decision is visible.

Six stages. One platform runs the whole program.

Discover

Assess

Plan

Execute

Govern

Retain

Know the estate before anything moves.

Sources of truth you already own

Connectors

Normalize and reconcile

1 Parse and map to CI classes

2 Match and de-duplicate

3 Resolve conflicts

4 Detect gaps

5 Keep lineage

One normalized repository

Rationalize before you move. Migrate only what earns its place.

Application data quality

Missing data by attribute

Workload profile

Disposition by application

Component end-of-life risk

What the assessment produces

Understand what moves together.

Move group MG-14 · Finance Ledger

Evidence behind each link

What-if: Finance to Wave 2

Clarity sits at the center of the toolchain. It replaces nothing that works.

Sources of truth

Automation brokers

Migration engines

Targets

End-user computing

People and notifications

From an agreed plan to a completed migration.

1 T-minus runbook · the lead-up plan

2 Execution runbook · generated task graph, every node has an action

Governance lives in the delivery data, not in a separate deck.

RAID log

Approvals

Command center

The inventory outlives the program.

Retain Clarity as your CMDB

Deployed inside your environment

Start small with ClarityLite

Less risk.More control.

Less risk.
More control.

Less risk.
More control.