No. Clarity plans, sequences and governs the migration, then drives execution through the tooling you already own: Nutanix Move, VMware HCX, AWS MGN and Transform, Azure Migrate, Veeam, Rubrik and Carbonite. It never replicates workloads itself, so there is nothing to rip out and replace.
FAQ
Questions we get asked
The questions that come up most often in first conversations, answered plainly. If yours isn't here, ask us.
About the platform
No. It is toolchain-neutral. Sources include your CMDB and ITSM, vCenter, Prism, SCVMM, Pure Storage, OpenShift and Kubernetes; targets include Nutanix AHV, VMware, AWS EC2, Azure, Hyper-V, Red Hat OpenShift and Kubernetes.
Your CMDB or ITSM platform (ServiceNow, Device42 or CSV import) for applications, owners, business units, dependencies and maintenance windows; your platforms and landing zones for inventory, configuration and utilisation; and a ClarityLite assessment for estate scanning and sizing. Every record keeps the source it came from.
Only if you want it to. Clarity can update your CMDB or ITSM records and write tags and categories to your platforms, so the target environment stays labelled consistently as the migration proceeds. Write-back is optional and configured per source; by default Clarity reads.
It holds one version of the estate that everyone works from, it generates the runbooks rather than transcribing them, it enforces sequencing so dependent workloads cannot be split across waves, and it records every decision and action with an audit trail.
Yes. Most programmes begin with a ClarityLite assessment: an agentless scan of your VMware, Hyper-V or Nutanix estate that produces a sizing and readiness report the moment the scan completes, with no commitment. From there, many customers run a single wave or environment before expanding.
A lightweight discovery tool from the Clarity team. It scans your estate without agents, produces a shareable sizing and readiness report, and its output loads straight into Clarity as the first discovery source.
Inside your own environment, never as a shared cloud service. Your estate data stays within your network, under your security controls and access policies.
Working with Clarity
Programme leads for status, risk and decisions; migration engineers for move groups, runbooks and execution; application owners to approve, schedule and see what happens to their systems; delivery partners to run their own programmes with their own roles and reporting.
Yes. Delivery partners run programmes on Clarity as the shared orchestration layer, with their own roles, permissions and reporting.
No. Owners see a simple view of what is moving, when, and what they need to approve.
Two options: export everything and close the platform down, or retain Clarity as your CMDB.
Get in touch
Still have a question?
Ask us directly and we will come back to you.