VMware exit planning
Know what your Linux workload needs before leaving VMware.
Changing hypervisors and modernizing the operating system are two different decisions. Virtual Move helps you understand what a supported Linux workload actually runs, so you can plan the rebuild on the target platform.
Benefits
Separate the two problems
Moving a VM to a new hypervisor keeps its OS as-is. Modernizing rebuilds the workload on a supported distribution. Know which you are doing.
Inventory what really runs
Packages, services, configuration and accounts are read from the workload itself, not from stale documentation.
Hand partners a clear plan
Mappings, unresolved items and generated Ansible or Terraform give your partner something concrete to review and execute.
Process
Three steps, with clear operators
01
Assess the source
- Virtual Move
- Reads the supported workload read-only and maps packages, services, configuration and accounts.
- Your team
- Grant access to an image or host and confirm the path is supported.
02
Review the plan
- Virtual Move
- Produces mappings, unresolved items and Ansible or Terraform output.
- Your team
- Resolve flagged items, review every change, approve the plan.
03
Run and verify
- Virtual Move
- Compares the rebuilt system with the baseline and signs the report.
- Your team
- Provision, execute, test applications and data, and decide on cutover.
What you get / What your team does
What you get
- Read-only capture of the workload from a VMDK image, live host or bare-metal server
- Mappings from the source distribution to a supported target
- Unresolved items flagged for human decision
- Ansible or Terraform output to rebuild the workload as a VM
What your team does
- Choose the target hypervisor or platform and provision it
- Decide per workload: lift as-is, or modernize the OS
- Review and run generated automation (in-house or via partner)
- Validate applications, networking and data after cutover
Illustrative report structure
What a report covers
Illustrative report structure only — not a real case study and not results from any customer. See the live demo for actual tool output.
Measured checks
- ☐ Packages present vs. baseline
- ☐ Services and enabled state
- ☐ Carried configuration files
- ☐ Accounts and groups
Unresolved gaps
- ☐ Items with no mapping
- ☐ Differences found on the rebuild
- ☐ Unknowns the checks could not measure
Verdict
- ☐ Result scoped to the checks performed
- ☐ Coverage of source items stated plainly
Report signature
- ☐ Signed attestation of checks run
- ☐ Re-check against baseline for later drift
Frequently asked questions
- Does Virtual Move convert VMs between hypervisors?
- That is not its focus. It helps modernize the Linux workload and rebuild it as a VM on a supported platform. Hypervisor conversion and provisioning remain with your team or partner.
- Is there an OpenShift integration?
- Automated OpenShift deployment is in development and not available today.
- Can our migration partner use it?
- Yes. The assessment output and generated plans are designed to be reviewed and executed by whoever runs the migration — your engineers or a partner.
- Which source platforms are supported?
- See vrtmv.com/supported for current source and target paths. Confirm your workload there before committing a timeline.
Assess one supported Linux workload before you commit your VMware exit plan.
Your team runs the migration. Virtual Move helps assess, plan and verify supported Linux workloads.