VMware to OpenShift Migration Guide
This guide is for VMware administrators and platform teams planning a move from vSphere to Red Hat OpenShift Virtualization. Follow the reading path below to assess your estate, design the destination, test virtual machines (VMs), and prepare for migration, recovery, and daily operations.
Start with the translation guide in the first stage, or jump to the decision in front of your team. Complete the testing and recovery rehearsals before the first production cutover.
Jump to: Assess · Design · Test · Migrate · Recover · Operate
The articles cover different product releases. Check the versions and support references in each guide against the environment you plan to run.
Assess the estate
Begin with what you own, what can move, and what the application needs. Give exclusions an owner before they become migration surprises.
- vSphere to OpenShift Virtualization: Translation Guide maps familiar inventory, permissions, resource pools, and placement rules to the decisions you need to make on OpenShift.
- OpenShift Migration Advisor: Rerun the Assessment explains how to refresh the inventory, track remaining blockers, and scope an application wave.
- 32-bit VMs Stay Out of OpenShift Wave 1 helps separate legacy guest operating systems from applications that can run on supported guests.
Leave this stage with: a proposed first wave, application owners, dependencies, and a list of workloads that need a different plan.
Design the destination
Agree on the cluster, storage, network, and access design before scheduling disk copies. Bring the teams that own those services into the review.
- How to Get Started with an OpenShift PoC puts prerequisites, installation, and the first workload in order.
- How Much Spare Capacity Does Your VM Cluster Need? works through CPU and memory budgets for maintenance, failures, and growth, with a calculator to adapt to your worker pool.
- vSAN-like Storage for OpenShift Virtualization Engine frames the choice between local-disk storage and an existing storage array.
- OpenShift Virtualization Networking: Pod to Localnet connects guest addressing and VLAN requirements to the host and VM network design.
Leave this stage with: an agreed destination design and named owners for storage, networks, access, and capacity.
Prove the platform
Use representative applications in non-production. Agree on the acceptance criteria before running the tests, including what happens during maintenance.
Use Is OpenShift Virtualization Ready for Your Production VMs? and its downloadable checklist to collect evidence, owners, and open issues for the go-live review.
- Benchmark OpenShift VMs Before the First Migration Wave builds a performance comparison around application demand and concurrent workloads.
- Windows VMs on OpenShift: Build a Repeatable Standard connects image preparation, guest identity, drivers, patching, and restore tests into a repeatable Windows Server build and operating standard.
- Hardening OpenShift Virtualization: First Priorities gives you an initial security baseline to validate with the platform team.
- Upgrading OpenShift While VMs Stay Running explains the drain and guest-migration behavior to rehearse before an upgrade window depends on it.
Leave this stage with: recorded performance, access, and maintenance test results, plus application-owner acceptance or a list of remaining fixes.
Plan the migration
Choose the copy method, dependency order, validation window, and decision to proceed or stop for each wave. Work through the recovery stage below before executing the first production cutover.
- VMware to OpenShift Virtualization: Copy Offload helps determine whether a storage-assisted copy path fits your environment and migration window.
- VDDK Off Broadcom’s Public Portal: MTV Migrations covers the access and packaging prerequisites when your Migration Toolkit for Virtualization (MTV) plan uses VMware’s Virtual Disk Development Kit (VDDK).
- Migrate Oracle Databases to OpenShift Virtualization is the additional design review for Oracle workloads, including the choice between a VM move and a database migration.
Leave this stage with: a migration runbook that names the owners, application checks, cutover window, and rollback decision point.
Rehearse recovery
Test how the service comes back when a migration, host, or recovery attempt fails. Include application data written after cutover in the rehearsal.
- Roll Back After Migrating to OpenShift Virtualization separates returning to an unchanged source from preserving transactions accepted on the destination.
- OADP for OpenShift VMs: Backup Is Not DR separates backup, restore, and disaster recovery, and explains what to measure in a restore exercise.
- Fence Gray Host Failures on OpenShift Virtualization examines the failure case where a host still responds to management requests while its workloads are stuck.
Leave this stage with: measured recovery times, verified application data, and an agreed point at which the VMware source can be retired.
Operate the platform
Assign ownership for alerts, maintenance, upgrades, and configuration changes before handing the platform to the operations team.
- What Replaces vRealize Operations for VMs identifies the monitoring questions to carry forward from the VMware environment.
- ACM as the Fleet Control Plane for OpenShift VMs covers inventory, policy, and operations when the estate spans multiple clusters.
- Park on 4.22 or Hop to 5.0 Before 4.22 Full Support Ends connects the release decision to support dates, compatible Operators, and the update path available to each cluster.
Leave this stage with: an operating plan that names who responds, who approves changes, and when maintenance and recovery rehearsals happen.
For more specific questions, browse the migration articles, storage articles, or the full archive.