Addresses the finding that customers are not well-informed about the process and that the end-to-end process is complex.

Move existing content into a comprehensive end-to-end guide for self-service users, directly addressing the finding that the migration process is complex and customers are not well-informed. The goal is to produce a single, clear, prescriptive resource that maps the entire user journey.

We must integrate and clarify the relationship between the following major steps/concepts, creating a clear narrative flow:

Phase 1: Conceptual Clarity and Prerequisites (Planning)

• Migration Types: Consolidate the explanation of Cold Migration and Warm Migration (including Precopy and Cutover stages) into a single, highly visible section that clearly advises the user on which type is appropriate based on their job/VM characteristics (e.g., shortest downtime vs. shortest duration for large single disks).
• Environment Setup (Networking): Create a clear sequence of instructions for all network prerequisites, linking together the requirement to configure host networking (e.g., NFC service memory for ESXi) with the required network mapping and port requirements. This is a major area of complexity.
• Namespaces: Provide explicit explanatory text clarifying the relationship between Plan Project (where the plan/CRs reside), the Source Provider, and the Target Project (namespace). This directly addresses a critical learning curve issue.

Phase 2: Execution and Monitoring (Migrating)

• Starting the Job: Clearly connect the act of creating a Plan CR to the subsequent creation of a Migration CR to start the process.
• Status and Logs (Troubleshooting): Directly integrate information on interpreting migration status and accessing logs into the main workflow narrative, rather than segregating it purely in a troubleshooting chapter. Explain where and how to view the progress pipeline, logs (including the distinction between available and unavailable logs based on migration type), and how to use must-gather.
• Advanced Options in Context: Weave in guidance on key advanced options, like Preserve Static IPs and Hooks, at the relevant points in the workflow where the user makes these decisions.

To address the complexity identified in MTV-3894, the documentation must pivot from a "feature list" to a "pathway." By using the Job-To-Be-Done (JTBD) framework, we can shift the focus toward the user's goal of a successful, predictable migration.

Job-To-Be-Done (JTBD) Statement

"When I am tasked with migrating business-critical virtual machines from a legacy VMware environment to OpenShift Virtualization, I want a single, prescriptive end-to-end guide that clarifies the 'how' and 'why' of every phase—from network prep to log analysis—so that I can minimize downtime, avoid configuration dead-ends, and confidently move our workloads without manual trial-and-error."

Personas