CentOS end of life
Find the blockers before you migrate CentOS.
Assess a supported Linux workload, identify how its packages, services and configuration map to the target distribution, surface the items that do not map, and plan your team's next steps.
Benefits
See blockers early
Unresolved packages, repositories and configuration are listed before anyone schedules a cutover.
Mappings with provenance
Each package, service and account mapping records where it came from, so engineers can review the reasoning.
A plan your team can run
Output is an Ansible or Terraform starting point for rebuilding as a VM — your team reviews and executes it.
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 assessment of a supported source (VM image, live host or bare-metal server)
- Package, service, repository and account mappings to the target distribution
- A list of unresolved and caveated items that need a human decision
- Generated Ansible or Terraform plan as a starting point
What your team does
- Confirm the source/target pair is on the supported paths list
- Resolve flagged items and review every generated change
- Provision the target environment and run the migration
- Test applications and data, and own the cutover decision
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
- Is this an in-place CentOS upgrade?
- No. Virtual Move reads the existing workload and helps rebuild it as a virtual machine on a supported target distribution. Your source system is read, not modified.
- Which CentOS versions and targets are supported?
- Supported source and target combinations are maintained at vrtmv.com/supported. Confirm your exact source and target versions with us; the public list includes examples and some paths are scoped on request.
- What happens to packages that do not map?
- They are reported as unresolved items with the context available. Your engineers decide whether to replace, rebuild, or retire them — the tool does not guess silently.
- Do we need to install an agent on production?
- Assessment can run against a cold VM image without booting it, or capture a live host. Review the docs for the access each mode requires.
Run an assessment on a supported CentOS workload and review what blocks the move.
Your team runs the migration. Virtual Move helps assess, plan and verify supported Linux workloads.