Does a Stage-0 readiness baseline replace cloud migration suites?

No. Stage-0 is a vendor-neutral CSV baseline that delivers per-VM readiness with reasons and executive rollups. Cloud migration suites provide target assessment, replication, testing, and cutover orchestration.

What carries forward from Stage-0 into a cloud migration suite?

Deduped inventory and counts, OS/role mix, backup posture, uptime class, and cohort shortlists—plus thresholds and rules—carry forward to drive sizing, replication scope, and wave planning.

Why start with Stage-0 instead of onboarding the entire estate into a suite?

Starting with Stage-0 provides quick, vendor-neutral triage without access changes, so cloud migration suites can focus on the workloads that actually move—reducing time, scope, and noise.

VMware Migration Readiness (Google Sheets Tool) vs Red Hat Migration Toolkit for Virtualization (MTV)

Stage-0 baseline (vCenter + backup CSVs, local) and Red Hat MTV for OpenShift Virtualization: how they fit together.

TL;DR

Purpose: Stage-0 = fast, local readiness baseline; Red Hat MTV = assessment/migration tooling to move VMs from VMware to OpenShift Virtualization (KubeVirt).
Inputs: Stage-0 uses vCenter + backup CSVs; MTV connects to vSphere and OpenShift to define mappings, plans, and migrations.
Outputs: Stage-0 delivers per-VM readiness with reasons + exec rollups; MTV delivers inventory import, network/storage mapping, migration plans, and execution status for moves into OpenShift.

Looking for the page where you can download the VMware Migration Readiness (Google Sheets Tool) — Stage-0 readiness baseline? Click here.

What each does

Stage-0 Readiness Baseline (this tool)

Inputs: vCenter inventory CSV + backup job inventory CSV.
Runs locally: Google Sheets (and Excel) — no agents, no SaaS ingest.
Normalization: deduped VM names, OS family, any-tag production/critical/compliance, uptime class.
Backup posture: missing/stale backups, short retention, irregular frequency, no offsite.
Output: Per-VM readiness with reasons (only causes that apply) and exec-ready rollups by Cluster / OS family / Uptime / Backup posture.
Why first: quickly separates move-sooner vs stabilize/leave-for-now cohorts before onboarding a full migration stack.

Red Hat MTV (for OpenShift Virtualization)

Goal: plan and execute VM migrations from VMware into OpenShift Virtualization (KubeVirt).
How: discover/import VMs from vSphere, define network & storage mappings, create migration plans, and run test/cutover moves into OpenShift.
Output: Project/plan artifacts, mapping objects, run status & logs, and post-migration validation in the OpenShift target.

When to use each

Use Stage-0 when you need a vendor-neutral triage baseline in hours—no connectors—to brief stakeholders and scope what should move vs stabilize.
Use Red Hat MTV when you’ve chosen OpenShift Virtualization as a target and you’re ready to pilot & migrate shortlisted workloads with mappings and plans.

How they work together (handoff 1-2-3)

Stage-0 shortlist: Identify cohorts by cluster/OS/role with readiness + reasons, backup posture, and uptime class; mark leave-for-now anchors and likely rebuilds.
Focused MTV onboarding: Import only the shortlisted cohorts; define network/storage mappings and create migration plans in MTV.
Pilot & waves: Use MTV’s plan/run outputs to schedule pilots and waves; keep Stage-0 flags as your audit trail for what moved now vs later and why.

What carries forward from Stage-0 (not throwaway)

Deduped VM inventory with normalized names & OS family.
Any-tag normalization for production / critical (DB/AD/DNS) / compliance.
Backup posture flags informing RPO/RTO readiness and rehearsal depth.
Uptime class for change windows and stabilization tasks.
Cohort shortlist (move-sooner / stabilize / rebuild / leave-for-now) to limit MTV scope.
Assumptions register (thresholds) and readiness rules table for governance.
Optional CSV bundle (inventory + flags + cohorts) to align teams before MTV plans.

Can we continue guiding beyond Stage-0?

Yes. If OpenShift is your direction, we’ll help scope pilots, ensure Stage-0 artifacts are reused with MTV plans (no re-keying), and keep assumptions consistent from baseline through migration.

What this page is not

A product review or endorsement. This page explains how a Stage-0 readiness baseline complements Red Hat MTV for OpenShift Virtualization.

Micro-FAQ

No. Stage-0 provides a readiness baseline and shortlists cohorts; MTV plans and executes migrations into OpenShift Virtualization.
Deduped counts, OS/role mix, backup posture, uptime class, and cohort selection—plus thresholds/rules—feed mapping choices and migration plans.
Lower friction and faster signal; you avoid onboarding the entire estate and focus MTV on workloads that will actually move to OpenShift.

Legal & attribution

This page compares a Stage-0 readiness baseline with Red Hat Migration Toolkit for Virtualization (MTV) for OpenShift Virtualization (KubeVirt). Red Hat, OpenShift, and related marks are trademarks of Red Hat, Inc. We are not affiliated with, endorsed, or sponsored by Red Hat, Inc. Descriptions of third-party capabilities are based on publicly available information and typical deployments as of September 2025 and may change without notice.

Nothing here is legal, financial, or professional advice. Use of third-party products is governed by those vendors’ terms and privacy policies. Our tool runs locally in your Google Drive.

Last reviewed: September 8, 2025.