---
title: Readiness Assessment
description: Use Advisory readiness evidence to expose migration constraints, assign remediation actions, and decide when workloads can enter detailed migration planning.
sidebar:
    label: Overview
    order: 0
source_url: "https://framework.stackit.cloud/migration/assess/readiness-assessment/overview/"
source_file: "docs/migration/assess/readiness-assessment/overview.mdx"
---

## 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.

<Aside type="note" title="Establish the baseline first">
    Complete the readiness questionnaire, validate the evidence in expert workshops, and record open
    findings before applying the results to migration scope and sequencing.
</Aside>

## 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.

<LinkCard
    title="Cloud Readiness Assessment Workshop Series"
    href="/advisory/transition-to-adoption/workshops/"
/>

## 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

Convert every unresolved finding into a migration artifact rather than carrying it as a general
observation:

1. Record the affected workloads and waves.
2. Assign an accountable owner and a target date.
3. Define the evidence required to close the finding.
4. Mark the finding as a blocker, a pre-wave action, or an accepted risk.
5. Recheck readiness at the relevant design or wave gate.

The resulting readiness backlog feeds [Discovery](/migration/design-and-mobilize/discovery/overview/),
[Migration Plan](/migration/design-and-mobilize/migration-plan/overview/),
[Enablement](/migration/design-and-mobilize/enablement/overview/), and
[Migration Factory Setup](/migration/design-and-mobilize/migration-factory-setup/overview/).

## Detailed assessment guidance

Continue with the complete acceptance criteria, thresholds, scorecard, and formal go/no-go process.

<LinkCard
    title="5-Dimension Readiness Assessment"
    href="/advisory/transition-to-adoption/readiness-assesment/"
/>