Why fragmented hardware and software tracking derails a cloud migration, and what has to be true of your asset data before you start retiring things.
First published in August 2019. Updated on migration so that what it says about CerteroX is true of the product today.
Data centre asset tracking with real automation makes a cloud migration programme faster and considerably less risky. Without it, you are making retirement decisions on data you cannot validate.
Data centres are dynamic and, from a records point of view, unpredictable. That makes precise tracking hard and makes it matter more — especially if you are preparing a migration programme to support a cloud-first strategy.
Many of the older tools on the market addressed hardware alone. They were manual and prone to human error, and they produced basic inventory data with nothing about the software running on top of it. For a CIO planning a migration, that is half an answer. You know a server exists. You do not know what it does, who depends on it, or what licensing follows the workload when it moves.
Software Asset Management tools emerged to close that gap, aimed at the data centre publishers that carry the most licensing risk — Microsoft, SAP, Oracle and IBM. They closed it only partly.
Most of those tools were developed independently, by different teams, over long periods. Layers of legacy technology accumulated across a collection of separate products. And a great many SAM tools carry no ITAM data at all, which means enterprises buy several products that do not integrate with one another. The result is a patchwork of tools and data sources rather than a record of what you own.
For a cloud-first programme, that fragmentation is expensive in a specific way. It forces slow manual work to produce low-value output. It lets human error into the analysis your migration decisions rest on. And it produces two failure modes that are hard to reverse: an uncontrolled cloud environment with costs nobody predicted, or old hardware and software that never actually gets retired, leaving security exposure and licence liability behind you.
The question is how you control data centre hardware and software together, in one place, well enough to drive a migration. That capability exists today.
One record across everything you run. CerteroX ITAM runs a native inventory agent across six operating system families — Windows, macOS, Linux, IBM AIX, HP-UX and Oracle Solaris — alongside agentless and command-line inventory for locked-down systems, standalone inventory for air-gapped ones, and network discovery that sweeps a class-C subnet in under five seconds. Ten discovery methods, one schema. There is no reconciliation project because there is nothing to reconcile.
Licensing depth on the publishers that bite. CerteroX SAM carries dedicated licence engines for Microsoft, Oracle, IBM, SAP, Adobe and Salesforce. For a data centre migration that depth is the difference between moving a workload and moving a liability: Oracle options and packs with evidence and override, processor types and core factors, licence pools with hosting rights and geographic rules; IBM PVU and Virtual Processor Core metrics with sub-capacity handling; Microsoft server core and processor licensing with cluster and virtualisation awareness. Certero is a verified third-party tool vendor with Oracle License Management Services, which means Oracle’s audit team can accept data from Certero during an official audit, as an alternative to installing Oracle’s own measurement tools.
The destination, not just the source. CerteroX Cloud Management covers twelve cloud and data platforms with a cost model built on FOCUS, the FinOps open cost and usage specification, and twenty-six named optimisation checks. Certero’s average cloud cost saving across environments under management is 38%.
The applications people bring with them. CerteroX SaaS Management discovers SaaS through three converging signals — identity provider sync, 47 vendor connectors and a browser extension — against a catalogue of more than 35,000 applications, including AI tools classified from catalogue feature tags rather than a fixed list.
All of it runs from one login, one interface and a single normalised data source, deployable as SaaS, on-premises or any hybrid combination.
With automation, one data source and analytics in the platform, the manual work between discovery and a decision largely disappears. That frees the people who understand your environment to work on the migration itself rather than on assembling spreadsheets about it. The return is faster and larger, and the data underneath it is better.
More concretely, if you are running a cloud-first strategy you get visibility of the whole picture at once — the hardware and software you have today, and the cloud resources replacing them. The data is gathered automatically and lands in one normalised source, so your teams can govern the migration end to end rather than auditing it afterwards.
That is what lets you retire legacy applications and hardware with confidence that no vulnerability and no licence liability is being left behind. And on the other side of the move, the three things that usually go wrong after a migration are addressable rather than theoretical:
Take an inventory of what you already have, and be honest about where it stops. Most programmes discover the gap is not the Windows fleet. It is the Unix servers, the virtualisation relationships that drive processor-metric licensing, and the cloud accounts opened outside procurement.
Then put your own awkward cases to any candidate platform. Ask it to discover one data centre VM, one cloud VM, one Unix server and one workload you are planning to retire — and to tell you what licensing moves with it.
Know what is in the rack before you decide what moves. Talk to us or book a demo.
Other posts covering the same ground.
FinOps was built for the cloud and stops at the data centre door. ITAM knows the assets and licences underneath. Neither is complete alone — and hybrid cost control needs both working from the same data.
Audit frequency went up, not down, as software moved to subscription. Meanwhile a fixed share of cloud spend is wasted every month. Both are real, and only one of them is a certainty.
Eight shifts reshaping ITAM through 2025 — from the gap between MDM and true lifecycle management, to multi-cloud visibility, compliance automation, security convergence and workflow orchestration. What each one means, and what to do about it.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.