Workload Assessment
Record each application’s data flows, dependencies and technical debt to select its target and migration method.
A good migration does not start by copying workloads, but with dependencies, identity, network, data, cost and a defensible target operating model.
A cloud migration starts by deciding where each application fits and how it will operate there. Dependencies, data, licensing and cost determine the sequence. Each wave needs tests, approval criteria and a workable rollback.
Record each application’s data flows, dependencies and technical debt to select its target and migration method.
Standardise accounts, subscriptions, networks, policies, logging and guardrails before the first production deployment.
Plan identity federation and Entra or IAM roles alongside DNS, routing, VPN and private connections. Test required access paths.
Criticality and dependencies determine migration waves. Assign each wave owners, testing windows, rollback points and approval criteria.
After migration, maintain budgets, tags, reservations, rightsizing and operational routines. Assign clear cost ownership.
Use the Planning a cloud migration checklists in workshops and reviews to record missing information and decisions.
CALCExplore Planning a cloud migration in the planner through users, systems, coverage and operations. The result remains a cost indication.
QUOTEFor a Planning a cloud migration enquiry, describe affected systems, starting point and goal. We clarify responsibilities together afterwards.
For Planning a cloud migration, review scope, dependencies and ownership with us, then define next steps including future operations.