Guide G9 Cloud & virtualization
Retiring a server or moving to Azure is a project, not a support ticket.
“The server is slow” is a support ticket. “Should we still own this hardware” is a project decision that needs an inventory, a dependency map, and a downtime tolerance before anyone can propose a credible plan. This guide separates the two.
G9 · Entry 01 Name the actual decision
A slow server and a platform decision are not the same question.
A specific server or VM is misbehaving
Support needs the host, VM name, error, and any recent change - not a migration plan.
Aging hardware needs an ownership decision
Warranty end dates and repeated failures often reveal a missing recurring-ownership conversation first.
You're deciding whether to move to Azure or consolidate hosts
This is a scoped project: inventory, dependencies, downtime tolerance, and a rollback plan come before a quote.
G9 · Entry 02 Decision matrix
Match the situation to the right first route.
| Observed need | Best first route | Useful evidence | Boundary |
|---|---|---|---|
| One VM or application is failing | Support | Host, VM name, error, recent changes | Not a migration plan |
| Physical hardware is aging with no replacement decided | Scoped project | Server age, workload list, warranty status | Not free hardware disposal |
| You want workloads moved to Azure or another cloud | Scoped project or advisory | Application inventory, dependencies, downtime tolerance | Not a cost estimate without discovery |
| Hyper-V/VMware licensing or consolidation is undecided | Scoped project or advisory | Host count, VM count, current licensing terms | Not a vendor price negotiation |
G9 · Entry 03 Plan before you propose
What a credible migration or virtualization project defines first.
- Step 01
Inventory
Every server, VM, and application, with its business owner and current resource use.
- Step 02
Dependency mapping
What breaks if this workload moves, or a server is retired, including integrations and scheduled jobs.
- Step 03
Downtime tolerance
How much planned interruption the business can accept, and during which hours or days.
- Step 04
Rollback plan
What happens if a migration or virtualization step does not go as planned, and who decides to reverse it.
G9 · Entry 04 What this covers
What this guide covers, and what it does not.
- In scope
- Separating a one-off server issue from a bounded migration or virtualization project, and the planning evidence it needs.
- Out of scope
- Specific Azure pricing quotes, licensing negotiation, and hands-on migration execution steps.
- Possible next decision
- A scoped migration or virtualization project, or ongoing infrastructure ownership once the environment is stable.
G9 Next
Scope the project, then decide who owns what remains.
Compare specialist and project routes, or see what ongoing infrastructure ownership covers once the migration is complete.