Step 1 of 5
What is the business reason for the change?
Start with the outcome: ageing hardware, remote access, resilience, application requirements or simpler operations. A destination is not a business case.
Step 2 of 5
What depends on what?
Bring applications, data, identity, network connections and integrations into the conversation. Ask application suppliers about support and licensing requirements.
Step 3 of 5
What is included in the operating cost?
Ask for an explicit cost model and its assumptions. Compare more than the virtual machine line item.
Step 4 of 5
How will the design be proved?
Define the tests before agreeing on the move. Include the people who use the applications and know when a process is genuinely working.
Step 5 of 5
Who owns the environment after the move?
A successful cutover is not the end of the project. Agree on documentation, monitoring, support and cost oversight before handing it over.
A planning worksheet, not an assessment of your environment. Avoid entering passwords or confidential information in general website tools.