From one workload to a clearer decision.

1. 01

   Your team + Virtual Move

   Establish source → target

   Confirm exact Linux versions and supported path. Agree what evidence the decision needs.

2. 02

   Virtual Move · access by your team

   Assess read-only + baseline

   Inventory packages, services, configuration and accounts. Source access choices depend on supported mode.

3. 03

   Your team / partner

   Review unresolved mappings

   Investigate blockers and unknowns. Decide how each exception should be handled.

4. 04

   Your team / partner

   Execute the migration

   Provide access, provision the target and own cutover. Virtual Move does not run your migration.

5. 05

   Virtual Move

   Measure against the baseline

   Compare measured target state. Keep differences and unavailable checks visible.

6. 06

   Virtual Move + your reviewers

   Sign scoped findings

   Keep integrity evidence and check scope. Your team owns application, data and performance tests.

Assessment and migration are different activities. Agree access and supported mode before running checks. Read the documentation →