Workload and dependency review
Map application services, data stores, jobs and external connections. Name owners and identify requirements for availability, location and recovery.
Services
Connect architecture decisions to actual workload needs.
Start with one application or cost concern and the responsibilities around it.
Usage and cost attribution
Review resource use and billing categories for the agreed scope. Separate business growth, price or plan changes, repeated work and resources whose purpose needs investigation.
Capacity and sizing
Compare ordinary and peak demand with the required performance. Propose a limited sizing or architecture change with a way to verify the result and recover if needed.
Recovery and operating plans
Review backups, restore assumptions and dependencies before a move. Agree recovery goals and a suitable controlled exercise rather than assuming a backup exists because a job is configured.
Implementation and handoff
Make agreed scoped changes with documented ownership, release conditions and checks. Review vendor-specific options and current costs for the actual environment.
Discuss a first workload review. For a hosting move, see website and VPS migration.