Financial transparency
A first cost corridor and TCO perspective are available for investment decisions.
Last updated on
Comprehensive migration walkthrough from Assess through Design and Mobilize and Migrate to Run, using the framework's core visuals and decision models.
Open with the end-to-end framework and its visual model so the audience can place every following activity in the journey from Assess through Design and Mobilize and Migrate to Run.
The overview below summarizes the migration lifecycle from initial assessment to stable operations. It helps teams build a shared understanding of responsibilities, dependencies, and expected outcomes across all phases.
Frame Assess as the fast, low-commitment phase that builds an initial fact base and qualifies migration intent before deeper design work starts.
Assess is the first phase of the STACKIT Migration Framework. It creates a fact-based baseline for migration decisions before architecture design and wave delivery begin.
The phase combines technical discovery with commercial and organizational alignment so that later migration work starts with clear priorities and transparent assumptions.
Assess typically starts when a migration initiative has strategic sponsorship but no decision-ready baseline yet.
Assess is completed when stakeholders can approve moving into Design and Mobilize with a shared understanding of cost, risk, and delivery feasibility.
Assess reduces uncertainty early and aligns business and IT before large implementation effort is committed.
Financial transparency
A first cost corridor and TCO perspective are available for investment decisions.
Readiness clarity
Gaps in technology, governance, capabilities, and operating model are visible early.
Stakeholder alignment
Leadership, delivery teams, and technical owners align on goals, scope, and expectations.
Risk reduction
Key assumptions and migration constraints are documented before target design starts.
The following diagram shows why Rapid Discovery is performed: raw source data is processed by tooling into a decision-ready baseline that supports early price indication and initial target sizing.


CloudMent AI-Powered Cloud Advisor supports migration teams in Assess and Design and Mobilize. It combines CloudMent Deck for structured assessment artifacts with CloudMent Essential for interactive STACKIT advisory.
The solution helps architects and portfolio teams capture requirements, map source services to STACKIT options, select R-strategies, design target architectures, and estimate STACKIT run costs. Recommendations are grounded in STACKIT documentation and include citations for expert review.
A TCO analysis is not primarily a cost-reduction argument. It is a decision-making tool. Its purpose is to make visible all costs — including those that are currently invisible — so that a comparison between the current state and the cloud target state is honest and complete.
The most common mistake in TCO analysis is treating it as a budget exercise: comparing the invoice from the cloud provider against the invoice from the current hosting provider. That comparison is almost always misleading, because it ignores the majority of relevant costs on the on-premises side.
A complete TCO model covers sixteen categories across four groups.
Direct infrastructure costs include hardware acquisition and depreciation, data centre space (power, cooling, space), network infrastructure, and storage systems. These are the costs most organisations can already see — but even here, the fully loaded cost is often underestimated because hardware refresh cycles are treated as capital expenditure rather than operating cost.
Software and licensing costs include operating system licences, virtualisation licences (VMware, Hyper-V), database licences, monitoring and management tooling, and backup and recovery software. Licensing is often the category where the largest surprises occur in cloud migration projects: licences that were purchased once and amortised over many years appear as a large one-time cost when they must be replaced or renegotiated.
Operations and personnel costs include IT operations staff (system administration, network operations, storage management), on-call costs, and the opportunity cost of skilled staff spending time on infrastructure rather than on business-value work. Personnel costs are typically the largest single category in a complete TCO model — and the one most frequently omitted from cloud business cases.
Compliance and risk costs include security tooling and personnel, compliance audit preparation and execution, insurance, and the cost of maintaining certifications (ISO 27001, BSI IT-Grundschutz). These costs are frequently invisible in the current state because they are distributed across multiple cost centres and headcount — but they are real, and cloud platforms that provide compliance features as a managed service reduce them materially.
The Deepdive Workshop is a one- to two-day technical workshop for the people who will later build, migrate, operate, or support workloads on STACKIT. It provides an early introduction to the platform and creates a shared technical understanding before detailed design and migration activities begin.
The workshop introduces relevant STACKIT services and concepts in the context of the planned migration. Depending on the agenda and available environment, participants can also try out selected services directly during the workshop.
The workshop helps technical teams to:
The exact agenda is tailored to the migration scope and the participating roles. Typical topics include:
Invite the technical people who will work with the platform after the migration, for example application teams, infrastructure and platform engineers, operations, security, and network specialists. The workshop is most effective when the team brings an initial view of the workloads, technical constraints, and questions it wants to clarify.
Before the workshop, align the agenda, participating roles, available test environment, and any access requirements. This keeps the sessions focused on the services and concepts that matter for the migration.
After the workshop, the participants have:
The Deepdive Workshop is an orientation and collaboration format. It does not replace structured enablement or a complete technical training programme. Use the workshop results to plan the required role-specific training and enablement activities in the following phases.
Briefings and Workshops are focused exchanges between the customer and STACKIT before the contractual relationship begins. They are appropriate when self-registration alone does not provide enough clarity for the planned use of the platform, the migration scope, or the required commercial and operational setup.
The sessions create a common understanding of the customer’s objectives and requirements, as well as the services, responsibilities, and engagement model that STACKIT can provide. Their goal is a contract relationship that is clear, practical, and suitable for both parties.
Use briefings and workshops when the planned engagement requires coordination beyond a standard self-service setup, for example because it involves a larger migration, specific compliance needs, several customer organizations, or individual commercial and operational requirements.
The format can include a short briefing, a series of working sessions, or a joint workshop. The scope and participants should match the complexity and decision needs of the engagement.
The sessions establish a shared, documented basis for the following topics:
Include the people who can clarify the relevant business, technical, legal, and operational questions. Depending on the engagement, this may include customer sponsors, procurement, legal, security and compliance representatives, technical owners, and the corresponding STACKIT contacts.
Prepare the sessions with an initial description of the intended use, known requirements, expected scale, and open questions. This allows the discussion to focus on decisions and unresolved assumptions instead of basic fact finding.
At the end of the module, both parties should have:
Briefings and Workshops do not replace technical discovery, a Deepdive Workshop, or detailed solution design. They ensure that the commercial, organizational, and operational foundation is aligned so that those activities can proceed with clear expectations and an appropriate contractual basis.
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.
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:
| 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. |
Convert every unresolved finding into a migration artifact rather than carrying it as a general observation:
The resulting readiness backlog feeds Discovery, Migration Plan, Enablement, and Migration Factory Setup.
Continue with the complete acceptance criteria, thresholds, scorecard, and formal go/no-go process.
5-Dimension Readiness Assessment Open pagePosition Design and Mobilize as the phase carrying most of the framework's substance: it turns Assess signals into an executable, factory-ready delivery plan.
Design and Mobilize is the planning and enablement phase between Assess and Migrate. It translates baseline findings into executable target designs, governance, and migration factory readiness.
The phase ensures that migration delivery starts with clear architectural decisions, security controls, team setup, and wave planning.
This phase starts after Assess confirms migration scope, readiness, and commercial direction.
Design and Mobilize is complete when migration teams can begin wave run with stable inputs, controls, and responsibilities.
This phase turns strategy into delivery readiness and prevents uncontrolled migrations.
Architecture readiness
Target patterns and migration paths per workload are defined and validated.
Factory enablement
Roles, processes, tooling, and runbook governance are established before scale-up.
Security by design
Security and compliance requirements are integrated into design and planning from the start.
Execution confidence
Waves are sequenced with dependency awareness and operational feasibility.
Go deep here: Discovery turns the rapid assessment into migration-ready evidence about workloads, dependencies, constraints, and stakeholders.
The following diagram shows how Discovery transforms technical and stakeholder input into decision-ready outputs for the downstream modules.
Discovery intentionally combines two evidence streams that complement each other:
Neither stream is sufficient on its own. Technical evidence without owner context can misclassify critical workloads, while human input without technical grounding can hide coupling and capacity risks. Discovery quality depends on reconciling both streams into one decision-ready view.
During Discovery, tooling commonly applies the following analysis patterns:
These analyses establish the technical fact base. The human-driven stream then validates, prioritizes, and contextualizes these findings for executable migration decisions.
Go deep here: use the R-strategy graphic as the anchor for explaining how each application's migration approach is chosen and justified.
The R-strategy model is the core decision framework in this module. For each application, the selected R-strategy must be justified with architecture, business, risk, and operability evidence.
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Application runtime migration
Migration of complete application runtimes across VM and platform targets, including dependencies, cutover behavior, and operating handover.
Container platform migration
Migration between Kubernetes platforms with separate treatment of stateless and stateful workload profiles.
Data migration
Migration of large file volumes, databases, and data platform workloads with explicit consistency, performance, and integrity boundaries.
Identity and access migration
Migration of IAM foundations such as SSO, federation, roles, service accounts, and permission models.
Network and connectivity migration
Migration of routing, DNS, firewall rules, segmentation, private connectivity, and cross-environment communication paths.
Integration and API migration
Migration of API contracts, messaging, eventing, and integration endpoints across source and target estates.
Security and compliance controls migration
Migration of controls, evidence chains, key material, and audit requirements required for regulated production readiness.
Operations and observability migration
Migration of monitoring, alerting, logging, incident workflows, and service-level operations baselines.
Delivery and resilience migration
Migration of CI/CD pipelines, automation controls, backup chains, and disaster recovery capabilities.
Use this as a practical orientation for application design:
Do not choose based on team habit only. Choose based on measurable requirements, operating capacity, and life cycle goals.
VM runtime (IaaS)
Best for low-change migrations and components needing OS-level control, custom agents, or strict legacy compatibility.
Kubernetes runtime (PaaS-like ops model)
Best for containerized workloads needing controlled scalability, release automation, and standardized platform operations.
Cloud Foundry runtime (PaaS)
Best when teams prioritize developer productivity and fast app delivery over low-level platform control.
Static delivery with Object Storage/CDN
Best for frontend/static workloads with high distribution needs and minimal backend runtime complexity.
SaaS replacement path
Best when process fit and standard capabilities provide higher value than migrating and operating the existing application stack.
Every migration runbook should include these chapters:
Executable
Verifiable
Validation points define clear pass/fail criteria and required evidence.
Recoverable
Rollback path is complete, timed, and linked to explicit trigger conditions.
Handover-ready
Go deep here: connect each R-strategy choice with one-time investment, run-cost economics, and expected long-term value.
The following matrix explicitly models what the run-cost stack does not show: one-time migration and project cost by strategy choice.
How to read this matrix:
Use both views together for decision quality:
The following semantic stack compares baseline and target costs by category on one shared scale. In this example, the STACKIT stack shows a midpoint scenario and explicit value ranges per category. Depending on migration quality and FinOps maturity, some categories can increase.
Important: This chart uses illustrative cost-index values to explain the comparison method. It is not an empirical benchmark and must be replaced with project-specific baseline and pricing inputs.
Go deep here: the migration plan is the shared control document connecting portfolio decisions with executable delivery waves.
The following diagram visualizes the operating model based on phases and modules: planning remains anchored in the Migration Plan module (Design and Mobilize), while delivery runs in staggered migration waves.
In this model, phase boundaries are intentionally overlapping:
The detailed setup scope is documented in its dedicated chapter: Migration Factory Setup.
The pattern is intentionally dynamic: portfolio work keeps a stable forward buffer, while migration work runs waves with runbooks, cutovers, and validation.
In this module, the migration factory is typically operated through four components:
Project governance rules
Processes and tools that govern wave orchestration, communication, timelines, and cutovers so teams run tasks in the right sequence and at the right time.
Portfolio runbooks
Runbooks used to prioritize applications, plan waves, and collect migration metadata as the input material for delivery.
Migration runbooks
Runbooks used to run migration waves, load metadata into migration tooling, and complete cutover and validation.
Best practices and health-check matrix
A regular health-check mechanism used to assess progress, identify delivery risks early, and keep delivery on track.
Go deep here: set up the shared platform baseline before application teams begin migration waves.
The following visual summarizes the core components that should be addressed for a reliable platform baseline.
Start the landing-zone stream as early as possible, in parallel with discovery.
The practical model is a dual track: establish the platform baseline early, then refine application landing zone templates as discovery insights mature.
Platform Landing Zone
Company-wide foundation for governance, identity, security, networking, cost controls, and automation.
Open Platform Landing ZoneApplication Landing Zone
Workload-specific implementation patterns derived from the platform baseline and discovery findings.
Open Application Landing ZoneGive the Target Operating Model its own moment: it defines how the platform is run, staffed, and governed once workloads land.
Governance and decision making
Establish decision rights, architecture and security review forums, exception handling, and an escalation model. See Governance and Decision Making.
Roles and responsibilities
Define accountable ownership across platform, application, security, FinOps, and service management teams. See Roles and Responsibilities.
Service management and operations
Make incident, change, problem, request, support, and handover processes operational. See Service Management and Operations.
Platform team and enablement
Operate the STACKIT platform foundation as an internal product with reusable guardrails and self-service paths. See Platform Team and Enablement.
Skills and change management
Build the capabilities, adoption practices, and communication routines needed for new cloud responsibilities. See Skills and Change Management.
Measurement and continuous improvement
Use reliability, delivery, security, and cost signals to improve platform and workload operations. See Measurement and Continuous Improvement.
Show how readiness findings become an operating enablement system: CCoE ownership, role-based STACKIT learning, and trusted documentation with AI-assisted guidance.
Cloud migration enablement turns a target architecture and migration plan into repeatable delivery capability. It gives teams the authority, skills, practical experience, and trusted information they need to make decisions without creating a dependency on a small group of experts.
The Readiness Assessment provides the starting point. Its questionnaire and workshops expose organizational and technical gaps, while the five-dimension scorecard identifies the roles, controls, funding, and platform capabilities that must be in place. Use those findings to prioritize the three enablement chapters below.
The Cloud Center of Excellence (CCoE) owns the enablement system across migration waves. It sets guardrails and reference patterns, connects platform and workload teams, maintains the skills plan, and makes sure that lessons from delivery become reusable organizational knowledge. It should enable decentralized delivery rather than become an approval bottleneck.
Establish the CCoE with a clear mandate, signed charter, appropriate structure and roles, a phased rollout, and a federated operating model that can scale across delivery teams.
During a migration, the CCoE should:
Create a trusted reference path for each migration role using authoritative STACKIT product documentation, migration decisions, and evidence.
Create one trusted reference path for each migration role. Combine authoritative STACKIT product documentation with migration-specific decisions and evidence, instead of copying product guidance into project documents that quickly become outdated.
Use the reference system for:


CloudMent AI-Powered Cloud Advisor supports migration teams in Assess and Design and Mobilize. It combines CloudMent Deck for structured assessment artifacts with CloudMent Essential for interactive STACKIT advisory.
The solution helps architects and portfolio teams capture requirements, map source services to STACKIT options, select R-strategies, design target architectures, and estimate STACKIT run costs. Recommendations are grounded in STACKIT documentation and include citations for expert review.
Go deep here: this is where an approved design becomes an executable, wave-scale delivery factory.
Cover partner model, tooling, interfaces, and runbook finalization as the pillars of a factory-ready setup.
Bring runbook gates and tool selection criteria together in one traceable approval for wave execution.
Keep this as concise as Assess and focus on the end-to-end factory flow that runs every wave to completion.
The end-to-end factory flow is the core chapter here: intake, run, validate, and hand over each wave through the factory.
Keep this concise: Optimize turns freshly migrated workloads into cost- and performance-tuned steady-state services.
Optimize starts when workloads run on STACKIT and real operating data is available. The module converts post-cutover observations into measurable improvements for performance, stability, and cost efficiency.
Optimize is not a one-time task. It is an iterative cycle that can overlap with early stabilization and post-cutover care.
Many right-sizing and tuning decisions are only reliable under real load patterns. After cutover, teams can use production telemetry to separate assumptions from actual behavior.
Close the journey briefly with the Run phase module map so the audience sees where migration outcomes ultimately land.
Run combines short-term stabilization and long-term service operations. The following model visualizes the intended flow from migration handoff to stable day-2 operations.