What Happens to Your Data? Understanding Our Aggregated Reporting Process

A comprehensive guide to the inventory data collected by Migration Advisor and what each field means for your migration planning.

The Migration Advisor tool collects data about your VMware environment to help you plan your migration to OpenShift Virtualization. This document describes all the data fields included in the aggregated inventory report.

Applies to: V0.4.0
Last update (dd-mm-yyyy): 02-02-2026

The data fields and structure described in this document may vary between releases. New fields may be added and deprecated fields may be removed based on the version of the Migration Advisor tool.

Report Structure Overview

The inventory report is organized hierarchically:


Virtual Machine Data

The vms section contains statistics about all virtual machines discovered in your environment.

VM Counts

FieldDescription
totalTotal number of virtual machines discovered
totalMigratableNumber of VMs that can be migrated without issues
totalMigratableWithWarningsNumber of VMs that can be migrated but have warnings to address

Resource Breakdown Fields

For each major resource (CPU, RAM, Disk), the report provides a detailed breakdown:

CPU Cores

FieldDescription
totalTotal vCPU cores allocated across all VMs
totalForMigratablevCPU cores for VMs that can be migrated
totalForMigratableWithWarningsvCPU cores for VMs migratable with warnings
totalForNotMigratablevCPU cores for VMs that cannot be migrated

RAM

FieldDescription
totalTotal RAM (GB) allocated across all VMs
totalForMigratableRAM (GB) for migratable VMs
totalForMigratableWithWarningsRAM (GB) for VMs migratable with warnings
totalForNotMigratableRAM (GB) for non-migratable VMs

Disk Storage

FieldDescription
totalTotal disk storage (GB) across all VMs
totalForMigratableDisk storage (GB) for migratable VMs
totalForMigratableWithWarningsDisk storage (GB) for VMs migratable with warnings
totalForNotMigratableDisk storage (GB) for non-migratable VMs

Disk Count

FieldDescription
totalTotal number of virtual disks across all VMs
totalForMigratableDisk count for migratable VMs
totalForMigratableWithWarningsDisk count for VMs migratable with warnings
totalForNotMigratableDisk count for non-migratable VMs

Distribution Metrics

These fields help you understand how your VMs are distributed across different resource tiers:

CPU Tier Distribution

Distribution of VMs across CPU tier buckets:

  • 0-4 vCPUs
  • 5-8 vCPUs
  • 9-16 vCPUs
  • 17-32 vCPUs
  • 32+ vCPUs

Memory Tier Distribution

Distribution of VMs across memory tier buckets:

  • 0-4 GB
  • 5-16 GB
  • 17-32 GB
  • 33-64 GB
  • 65-128 GB
  • 129-256 GB
  • 256+ GB

NIC Count Distribution

Distribution of VMs by network interface count:

  • 0 NICs
  • 1 NIC
  • 2 NICs
  • 3 NICs
  • 4+ NICs

Disk Information

Disk Size Tiers

For each disk size tier, the report provides:

FieldDescription
totalSizeTBTotal disk size in TB for this tier
vmCountNumber of VMs in this tier

Disk Types

For each disk type (e.g., thin, thick, RDM), the report provides:

FieldDescription
vmCountNumber of VMs with at least one disk of this type
totalSizeTBTotal disk size in TB for this disk type

Power States

A breakdown of VMs by their power state.

Operating System Information

For each detected operating system, the report provides:

FieldDescription
countNumber of VMs running this OS
supportedWhether the OS is supported for migration by MTV
upgradeRecommendationRecommended OS upgrade path for unsupported operating systems that can be upgraded to a supported version

Migration Issues

Not Migratable Reasons

A list of issues that prevent VMs from being migrated:

FieldDescription
idUnique identifier for the issue type
labelHuman-readable description of the issue
assessmentAssessment category (e.g., “error”)
countNumber of VMs affected by this issue

Common reasons include:

  • Unsupported disk types (RDM, shared VMDK)
  • Unsupported guest operating systems
  • VMs with snapshots
  • VMs with USB devices attached
  • VMs with NVRAM encryption

Migration Warnings

A list of issues that don’t block migration but should be addressed:

FieldDescription
idUnique identifier for the warning type
labelHuman-readable description of the warning
assessmentAssessment category (e.g., “warning”)
countNumber of VMs affected by this warning

Common warnings include:

  • Changed Block Tracking (CBT) not enabled
  • VMware Tools not installed or outdated
  • VMs with more than 4 NICs

Infrastructure Data

The infra section contains information about the physical infrastructure supporting your VMs.

Summary Counts

FieldDescription
totalHostsTotal number of ESXi hosts
totalDatacentersNumber of vSphere datacenters
clustersPerDatacenterCluster count per datacenter

Overcommitment Ratios

FieldDescription
cpuOverCommitmentCPU overcommitment ratio (allocated vCPUs ÷ physical cores)
memoryOverCommitmentMemory overcommitment ratio (allocated memory ÷ physical memory)

These ratios help you understand how heavily your current infrastructure is utilized and plan appropriate sizing for your OpenShift cluster.

Host Information

For each ESXi host:

FieldDescription
idUnique identifier for the host
vendorHardware vendor (e.g., Dell, HPE, Cisco)
modelServer model
cpuCoresNumber of physical CPU cores
cpuSocketsNumber of CPU sockets
memoryMBTotal host memory in MB

Host Power States

Breakdown of hosts by power state:

  • poweredOn
  • standby
  • maintenance

Network Information

For each network in your environment:

FieldDescription
nameNetwork name
typeNetwork type: standard, distributed, dvswitch, or unsupported
vlanIdVLAN identifier
dvswitchName of the distributed vSwitch (if applicable)
vmsCountNumber of VMs connected to this network

Datastore Information

For each datastore:

FieldDescription
typeStorage type (VMFS, NFS, vSAN, etc.)
totalCapacityGBTotal capacity in GB
freeCapacityGBAvailable free space in GB
vendorStorage vendor
modelStorage model
diskIdDisk/LUN identifier
protocolTypeStorage protocol (FC, iSCSI, NFS, etc.)
hardwareAcceleratedMoveWhether VAAI/XCOPY is supported
hostIdIdentifier of the host where this datastore is attached

Data Report Generation

The data report can be generated through two methods:

1. Discovery Agent (OVA installation in the VSphare environment)

When using the Discovery Agent:

  • Data is collected directly from vCenter APIs
  • Provides the most accurate and complete information
  • Updates automatically as your environment changes
  • Requires deploying the OVA appliance to your vCenter

2. RVTools Upload

When uploading an RVTools export:

  • Data is parsed from the Excel file
  • Quick assessment without deploying any agents
  • Data accuracy depends on when the RVTools export was generated
  • Some fields may be unavailable depending on RVTools configuration