Purpose and scope
Section titled “Purpose and scope”The Readiness Assessment evaluates whether the foundations required for cloud migration are in place. It covers technical, process, personnel, financial, and governance readiness. Its findings shape discovery depth, migration waves, staffing, platform prerequisites, and risk treatment.
Inputs from the readiness workshops
Section titled “Inputs from the readiness workshops”The STACKIT Cloud Readiness Assessment starts with a questionnaire and quality review, then uses joint expert workshops to validate the evidence and identify technical and organizational gaps. Its planning phase turns the findings into target architecture, migration-method, proof-of-concept, training, and roadmap decisions.
Bring these inputs into migration planning:
- the validated questionnaire and documented assumptions;
- the five-dimension readiness scorecard, including open items, owners, and target dates;
- workload criticality, dependencies, and initial R-strategy hypotheses;
- identified capability gaps and the resulting training needs;
- approved platform, governance, budget, and staffing prerequisites.
Apply the five dimensions to migration
Section titled “Apply the five dimensions to migration”| Advisory dimension | Migration planning question | Typical migration response |
|---|---|---|
| Technical | Are account structures, IAM, network, automation, guardrails, and observability ready for the planned workloads? | Add platform dependencies, proofs of concept, or landing-zone work before the affected wave. |
| Process | Can teams onboard, change, recover, and handle exceptions consistently? | Define runbooks, quality gates, escalation paths, and handover criteria. |
| Personnel | Are the CCoE, platform, application, security, and operations roles staffed and capable? | Assign role-based learning paths, coaching, and named owners before delivery starts. |
| Financial | Are funding, cost allocation, and value tracking approved? | Align wave scope with the business case, FinOps controls, and budget gates. |
| Governance | Are security, compliance, data protection, and reporting controls approved? | Record mandatory controls and evidence in designs, runbooks, and wave acceptance criteria. |
Migration outputs
Section titled “Migration outputs”Convert every unresolved finding into a migration artifact rather than carrying it as a general observation:
- Record the affected workloads and waves.
- Assign an accountable owner and a target date.
- Define the evidence required to close the finding.
- Mark the finding as a blocker, a pre-wave action, or an accepted risk.
- Recheck readiness at the relevant design or wave gate.
The resulting readiness backlog feeds Discovery, Migration Plan, Enablement, and Migration Factory Setup.
Detailed assessment guidance
Section titled “Detailed assessment guidance”Continue with the complete acceptance criteria, thresholds, scorecard, and formal go/no-go process.
5-Dimension Readiness Assessment Open page