VMware to OpenShift

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.

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.

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.

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.

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.

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.

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.