What we can work from.
An assessment is only as good as the data underneath it. We work from whatever you already have, and we publish what each of those tools can and cannot see before you rely on it.
Nobody else publishes this, and that is the point.
Every discovery tool has blind spots. A business case built without knowing them looks exactly as confident as one built with them.
"Tool agnostic" is a claim most partners make in a single bullet. We would rather show the work: a page for each tool covering what it collects, how it deploys, how long it takes to produce usable data, what we use it for, and the one thing about it we would want to know before choosing it.
If you have already run a discovery exercise with any of these, that is a reason to talk to us sooner rather than a reason to wait.
| Tool | Deployment | Agent | Utilisation | Dependencies | Time to data | Best for |
|---|---|---|---|---|---|---|
| RVTools | Utility against vCenter | No | Provisioning only | No | Hours | Fast directional sizing, Lite assessments |
| AWS Migration Evaluator | One Windows VM, agentless | No | Yes | Via Migration Hub | ~48h to first output | Expert-led business case, Microsoft licensing depth |
| AWS Transform discovery | Appliance into VMware, no cloud connectivity | No | Yes | Network connections | Days | Regulated and air-gapped estates |
| AWS Transform assessment | Console, ingests existing inventory | No | Source-dependent | Source-dependent | Same day | Fast self-service x86 modelling |
| Cloudamize | Agent, agentless or hypervisor | Optional | High resolution | Yes | Two weeks or more | Large estates, wave planning, SQL telemetry |
| CloudRays | PowerShell, Cloud Shell or desktop | No | Via Azure Monitor | Not established | Hours | Azure estates, cloud-to-cloud |
| NetApp DII | Observability collectors | No | Storage-focused | Storage-level | Weeks | Detached storage assessments |
| Matilda Cloud | Agentless platform | No | Yes | Application-centric | Days | Application-led assessments |
| CloudHedge CHAI | Platform, image on AWS Marketplace | No | Application analysis | Code and dependency graphs | Varies | Modernisation and containerisation |
| CMDB and flat files | Whatever you can export | No | If present | If present | Same day | Estates with existing inventory discipline |
AWS native
AWS Migration Evaluator
The expert-led business case service. The strongest AWS-native option where the licensing question is the expensive one, and the one with the failure modes worth knowing about.
Read the page →AWS Transform assessment
Self-service modelling for x86 estates, ingesting inventory you already hold. Gained what-if scenarios and customisable assumptions in 2026.
Read the page →AWS Transform discovery tool
An on-premises appliance that runs without cloud connectivity, which makes it the right instrument for regulated and air-gapped estates.
Read the page →Enterprise discovery platforms
Cloudamize
High-resolution collection with application dependency mapping and wave planning. Worth the two-week minimum where dependencies matter as much as the cost model.
Read the page →Matilda Cloud
Agentless and application-centric. The strongest of these on the application layer rather than the infrastructure layer.
Read the page →CloudHedge CHAI
Formerly OmniDeq. Modernisation and containerisation pathways rather than migration, and a natural next question after a large SQL Server footprint is found.
Read the page →Specialist
CloudRays
Read-only Azure inventory with utilisation metrics, maintained by AWS. An AWS-maintained instrument for measuring an Azure estate, which is exactly the credibility a cloud-to-cloud assessment needs.
Read the page →NetApp Data Infrastructure Insights
Formerly Cloud Insights. Storage and infrastructure analytics, and the usual starting point for a detached storage assessment.
Read the page →RVTools
Free, fast, and the quickest route to a directional answer. Also the one with the most important single limitation in this whole table.
Read the page →AWS discovery tooling changed in late 2025.
Application Discovery Service closed to new customers on 7 November 2025, and the Discovery Connector stopped accepting data ten days later.
AWS Transform is the named successor, and its discovery tool explicitly replaces the ADS Agentless Collector. Most organisations that ran a discovery exercise in the last two years are sitting on tooling that is now either deprecated or closed to new entrants, and most of them do not know it.
The useful part: your existing data is very unlikely to be wasted. Data already collected through ADS can still feed a Migration Evaluator assessment, and we would rather work from what you have than ask you to collect it twice.
Do not have any of this?
Most engagements start with an RVTools export or a read-only collector, and both are a short job. Tell us what you can get to and we will tell you what it will support.