Skip to content
Beta

Migration Framework Walkthrough

Last updated on

Stackit LogoStackit Logo
STACKIT

Migration Framework Walkthrough

Comprehensive migration walkthrough from Assess through Design and Mobilize and Migrate to Run, using the framework's core visuals and decision models.

PLAN

Migration Phases

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.

In 1 trail

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.

Swipe sideways to see the whole diagram
STACKIT Cloud Migration Framework Journey across the four phases Assess, Design and Mobilize, Migrate, and Run with their key modules. Assess PHASE 1 Assess Design & mobilize PHASE 2 Design & mobilize Migrate PHASE 3 Migrate Run PHASE 4 Run PLANNING Discovery Discovery Map apps and dependencies. Design Design Define target patterns. Migration plan Migration plan Sequence waves for delivery. Rapid discovery Rapid discovery Inventory workloads to create an early scope and cost baseline. TCO report TCO report Model migration economics to support investment and planning decisions. Readiness assessment Readiness assessment Assess technology and organization gaps before detailed design starts. Deepdive workshop Deepdive workshop Explore STACKIT services and platform options for target design. Briefings & workshops Briefings & workshops Align stakeholders on goals, scope, and migration expectations. Business case Business case Compare value, effort, and investment per application. Enablement ENABLEMENT Center of Excellence Trainings & Learning Paths Documentation & Reference Landing zone Landing zone Establish the secure platform base for migrated workloads. Security & compliance Security & compliance Define security and compliance controls for migration and operations. Target operating model Target operating model Define roles, processes, and ownership for target operations. Migration factory setup Migration factory setup Prepare teams, tools, and runbooks for scalable migration execution. Migrate MIGRATE Relocate Relocate Rehost Rehost Replatform Replatform Optimize Optimize Improve sizing, performance, and cost after cutover. Repurchase Repurchase Evaluate SaaS options when replacement delivers better value. Refactor Refactor Restructure strategic workloads for cloud- native scalability and agility. Operating model handover Operating model handover TOM validation and ownership transfer Hypercare Hypercare Post-cutover stabilization bridge. Operate Operate Steady-state cloud operations. Support Support Manage incidents and service requests across support responsibilities. Customer Success Customer Success Track adoption, outcomes, and value realization with stakeholders.
BASE

Assess

Frame Assess as the fast, low-commitment phase that builds an initial fact base and qualifies migration intent before deeper design work starts.

Overview In 2 trails

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.

  1. Start when migration scope, business drivers, and decision stakeholders are defined at a high level.
  2. Build the baseline through Rapid Discovery, readiness evaluation, cost modeling, and stakeholder workshops.
  3. End when scope assumptions, migration readiness, and financial direction are clear enough to start detailed design.

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.

STACKIT LogoSTACKIT Logo
Rapid Discovery STACKIT · Assess › Rapid Discovery Open page ↗

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.

Swipe sideways to see the whole diagram
Rapid discovery process Input data is processed through rapid discovery tooling to produce decision-ready outputs for early migration choices. Input dataCMDB & inventory exportsAsset lists, hosts, base platform factsHypervisor & cloud reportsUsage, footprint, and utilization signalsPlatform listsKubernetes, database, and OS baselinesRapid discovery toolingIngest & normalize datasetsStandardize source records and schemaClassify & aggregate assetsConsolidate by technology and quantityApply assumptionsConfidence levels and growth factorsOutput informationConsolidated asset baselineFact base for scope and planningInitial STACKIT sizingFirst capacity assumptionsPrice indication & TCO corridorEarly cost orientation for decisions
CloudMent LogoCloudMent Logo
CloudMent AI-Powered Cloud Advisor CloudMent · Software Open asset ↗

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.

  • Rapid Discovery and Readiness Assessment: Captures application landscape information and functional or non-functional requirements to create first readiness and portfolio views.
  • Discovery and Design: Maps AWS, Azure, and Google Cloud services to STACKIT equivalents with fit ratings and supports R-strategy selection during design.
  • Business Case: Estimates STACKIT monthly run rates from pricing context and generates decision-support figures for migration planning.
  • Enablement: Provides a guided advisory interface for teams learning STACKIT service options, Terraform patterns, and architecture decisions.
  • Requirements-driven assessment: Turns workload descriptions, inventories, or CMDB inputs into cloud readiness, R-strategy, target architecture, and business-case drafts.
  • Grounded advisory: Uses STACKIT documentation and provider context so recommendations can be checked through cited sources.
  • Source-to-target mapping: Compares hyperscaler services with STACKIT alternatives and labels direct fits, partial fits, and gaps.
  • Interactive design support: Builds and refines target architecture options with service mapping, cost estimates, and Terraform drafts.
STACKIT LogoSTACKIT Logo
TCO Analysis STACKIT · Business Case And Financial Planning Open page ↗

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.

STACKIT LogoSTACKIT Logo
Deepdive Workshop STACKIT · Assess › Deepdive Workshop Open page ↗

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:

  • become familiar with the STACKIT platform and its core concepts;
  • understand which services are relevant for their workloads and operating model;
  • discuss technical questions and assumptions early with STACKIT experts; and
  • identify topics that require deeper investigation during the following phases.

The exact agenda is tailored to the migration scope and the participating roles. Typical topics include:

  • Platform foundations: Regions, projects, identity and access management, networking, and security concepts.
  • Relevant services: Compute, storage, Kubernetes, databases, and other services that are appropriate for the target workloads.
  • Operational concepts: Monitoring, logging, automation, responsibilities, and support models.
  • Migration context: How existing workloads, dependencies, and technical requirements can be considered on STACKIT.
  • Hands-on exploration: Optional guided exercises in a prepared environment to explore selected services and workflows.

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:

  • a shared baseline understanding of the STACKIT platform;
  • an initial view of the services and concepts relevant to their migration;
  • documented technical questions, assumptions, and follow-up topics; and
  • clearer input for discovery, target design, and the migration plan.

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.

STACKIT LogoSTACKIT Logo
Briefings and Workshops STACKIT · Assess › Briefings And Workshop Open page ↗

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:

  • Business objectives and scope: Intended platform use, migration goals, priorities, expected scale, and relevant workloads.
  • Organizations and responsibilities: Customer contacts, decision-makers, technical teams, procurement, and the respective responsibilities of the customer and STACKIT.
  • Account and project structure: Required organizations, projects, access roles, ownership model, and the setup needed for the intended use.
  • Security, compliance, and data protection: Regulatory requirements, data classification, data residency, security expectations, and evidence needed for internal approval.
  • Commercial model and contracting: Required contract scope, pricing and billing expectations, commitments, procurement process, and any necessary contractual clarifications.
  • Operations and support: Service expectations, support model, escalation paths, operational responsibilities, and relevant availability requirements.
  • Delivery planning: Preconditions, dependencies, timeline, decision points, and the next steps toward onboarding, design, and migration.

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:

  • a shared understanding of the intended platform use and engagement scope;
  • a documented view of requirements, assumptions, dependencies, and open items;
  • agreement on the required account, security, support, and commercial setup;
  • clear responsibilities and decision owners for the next steps; and
  • a mutually understood path toward contracting and subsequent onboarding.

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.

STACKIT LogoSTACKIT Logo
Readiness Assessment STACKIT · Assess › Readiness Assessment Open page ↗

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:

  • 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.
Cloud Framework Cloud Readiness Assessment Workshop Series Open page

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 Plan, Enablement, and Migration Factory Setup.

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

Cloud Framework 5-Dimension Readiness Assessment Open page
LIFT

Design and Mobilize

Position Design and Mobilize as the phase carrying most of the framework's substance: it turns Assess signals into an executable, factory-ready delivery plan.

Overview In 2 trails

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.

  1. Start with detailed discovery of applications, dependencies, and migration constraints.
  2. Build target designs, business cases, and migration waves while setting up delivery structures.
  3. End when the first migration waves are approved, runbooks are ready, and governance is operational.

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.

STEP

Discovery

Go deep here: Discovery turns the rapid assessment into migration-ready evidence about workloads, dependencies, constraints, and stakeholders.

Design and mobilizeDiscoveryOverview In 4 trails

The following diagram shows how Discovery transforms technical and stakeholder input into decision-ready outputs for the downstream modules.

Swipe sideways to see the whole diagram
Discovery source-to-decision flow Discovery separates technical and human-driven inputs, runs technical-first and human-enriched analyses, and hands over both insight streams to follow-on modules. Discovery inputsTechnical and automated discoveryInfrastructure inventoryCMDB, VM, database, middleware, storageRuntime and utilization dataCPU, memory, I/O, network and seasonalityIntegration and flow signalsNetwork paths, APIs, identity, data movementAssessment-driven human inputSecurity and compliance contextData classes, controls, audit requirementsOwner and business inputCriticality, release windows, lifecycle plansDiscovery analysis toolingTechnical-first analysesNormalize and correlateUnify records and technical identitiesDependency mappingInfer communication and couplingUtilization and sizing analysisEstimate baseline demand corridorsPreliminary segmentationCluster by stack and environmentHuman-driven analyses (application owner input)Criticality and risk calibrationValidate business impact and constraintsWave feasibility and sequencingReconcile dependencies with release windowsAssumption and gap registerTrack open points and confidenceHandover outputsTool-derived outputsDesignTarget architecture options and sizing factsLanding zonePlatform guardrails and account structure needsMigration planWave backlog, sequencing, and cutover windowsAssessment-validated outputsSecurity and complianceControl needs, data classes, remediation pointsOperating modelRole model, ownership boundaries, process impactBusiness caseValue/risk profile and modernization priorities
Validate Evidence and Patterns

Two Evidence Streams: Technical vs. Human-Driven

Section titled “Two Evidence Streams: Technical vs. Human-Driven”

Discovery intentionally combines two evidence streams that complement each other:

  • Technically derived evidence: Tooling-generated findings from inventory exports, runtime metrics, and dependency signals. This stream provides scale, consistency, and repeatability.
  • Application-owner enrichment (human-driven): Validated business criticality, lifecycle intent, release constraints, and operational realities from owner interviews and questionnaires.

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.

Typical Analysis Patterns in Discovery Tooling

Section titled “Typical Analysis Patterns in Discovery Tooling”

During Discovery, tooling commonly applies the following analysis patterns:

  • Record normalization: Merge heterogeneous exports into one coherent application model.
  • Dependency mapping: Detect communication paths, data exchange, and coupling patterns.
  • Criticality and risk scoring: Evaluate business impact, failure domain, and compliance exposure.
  • Utilization profiling: Build workload demand baselines for right-sizing and target planning.
  • Segmentation analysis: Cluster applications by readiness, constraints, and migration strategy fit.
  • Wave simulation: Model move groups and sequence options under dependency constraints.
  • Gap and assumption tracking: Keep unresolved findings transparent with confidence levels.

These analyses establish the technical fact base. The human-driven stream then validates, prioritizes, and contextualizes these findings for executable migration decisions.

STEP

Design

Go deep here: use the R-strategy graphic as the anchor for explaining how each application's migration approach is chosen and justified.

Design and mobilizeDesignOverview In 2 trails

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.

Swipe sideways to see the whole diagram
R-strategy migration method Decision flow from discovery to production with the seven R-strategies: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire. R-strategy migration methodFrom discovery and path selection through the seven R-strategies to validation, transition, and production.DiscoveryDiscoveryAssess / prioritizeAssess / prioritizeDetermine migration pathDetermine migration pathValidationValidationTransitionTransitionProductionProductionRelocateRelocate(move VM)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployValidation & handoverRehostingRehosting(move application)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployReplatformingReplatforming(lift and reshape)Define Landing ZoneDefine Landing ZoneMap Target PlatformMap Target PlatformAdapt Platform StackAdapt Platform StackRepurchasingRepurchasing(replace, drop and shop)Purchase COTS/SaaS and licensingPurchase COTS/SaaS and licensingMigrate business processMigrate business processRefactoringRefactoring(re-architecting applications)Redesign application/ infrastructure architectureRedesign application/ infrastructure architectureApp code developmentApp code developmentFull ALM/SDLCFull ALM/SDLCIntegrationIntegrationRetain/moveRetain/movekeep for now or move laterRetire/decommissionRetire/decommissionLanding zone foundationLanding zone foundationShared platform base for all paths
  • Relocate: Choose when moving virtualization stacks is faster than redesign and governance constraints still allow conversion to cloud-native operations.
  • Rehost: Choose for low change tolerance and strict timelines, where speed is prioritized over immediate modernization.
  • Replatform: Choose when moderate changes unlock major benefits through STACKIT managed platform capabilities.
  • Repurchase: Choose only for services available in the STACKIT ecosystem, including SaaS options such as ServiceNow, SAP, and partner offerings when they better fit business needs.
  • Refactor: Choose for strategic applications where cloud-native redesign creates clear value in resilience, agility, or cost profile.
  • Retain: Choose retain when timing or dependencies block migration now.
  • Retire: Choose retire when business value no longer justifies operational effort.
PLAN

Explore the STACKIT Service Portfolio

STACKIT LogoSTACKIT Logo
Workload Migration Use Cases STACKIT · Design And Mobilize › Design Open page ↗

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.

Select the Target Pattern and Runtime

Service model decision guide (IaaS, PaaS, SaaS)

Section titled “Service model decision guide (IaaS, PaaS, SaaS)”

Use this as a practical orientation for application design:

  • Choose IaaS when: You need deep OS/runtime control, legacy dependencies, or custom networking constraints that managed platforms cannot satisfy.
  • Choose PaaS when: You want faster delivery and lower operations burden while keeping application ownership and portability goals.
  • Choose SaaS when: The business process can adopt a standard product model and differentiation does not require custom platform operation.

Do not choose based on team habit only. Choose based on measurable requirements, operating capacity, and life cycle goals.

Runtime selection guide for typical STACKIT targets

Section titled “Runtime selection guide for typical STACKIT targets”

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.

Prepare the Runbook and Cutover

Every migration runbook should include these chapters:

  • Scope and context: Application scope, source and target context, assumptions, exclusions.
  • Owners and decision rights: Technical owner, release owner, rollback authority, escalation path.
  • Dependencies and prerequisites: Platform readiness, access, data state, external system windows.
  • Cutover plan: Ordered run steps, expected duration, freeze points, communication points.
  • Validation checks: Functional, non-functional, security, and observability checks with evidence.
  • Rollback and contingency: Trigger conditions, rollback steps, fallback communication flow.
  • Handover and Day-1 operations: Operations transfer, incident ownership, post-cutover watch period.

Executable

Steps are concrete, ordered, and assignable to named roles.

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

Day-1 operations and ownership transfer are fully specified.
OPS

Business Case

Go deep here: connect each R-strategy choice with one-time investment, run-cost economics, and expected long-term value.

Design and mobilizeBusiness caseOverview In 1 trail

R-strategy matrix for one-time investment versus long-term value

Section titled “R-strategy matrix for one-time investment versus 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.

Swipe sideways to see the whole diagram
R-strategy matrix: migration investment versus long-term value Each strategy is shown as a range area: X = one-time migration/project investment, Y = long-term value (run-cost impact plus business effects). R-strategy matrix: migration investment versus long-term valueEach strategy is shown as a range area: X = one-time migration/project investment, Y = long-term value (run-cost impact plus business effects).Preferred zone: low investment, high valueLeast attractive zone: high investment, low valueOne-time migration and project cost index (low to high)Long-term value index (low to high)RelocateRehostReplatformRepurchaseRefactorRetainRetireArea width and height represent value ranges. Midpoint dots are orientation anchors, not commitments. Dashed = not a migration path (keep or decommission).VALUE RANGES BY STRATEGYInvestValueRelocate10–2510–25Rehost15–3520–40Replatform30–5540–65Repurchase45–7555–80Refactor55–9060–90Retain5–2010–30Retire20–4550–85

How to read this matrix:

  • X-axis: One-time migration and project investment (implementation effort, tooling, testing, change, cutover).
  • Y-axis: Long-term value (run-cost impact plus business and operating effects).
  • Point labels: Illustrative ranges, not fixed promises.

Use both views together for decision quality:

  • Run-cost stack: Recurring operating cost trajectory.
  • R-strategy matrix: Upfront investment and transformation effect.
  • Decision metric: Evaluate break-even and value realization over a defined horizon, not by run cost alone.

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.

Swipe sideways to see the whole diagram
Business Case cost transparency by stack Example annual run-cost index by category, using one shared scale for baseline and target. Business Case cost transparency by stackExample annual run-cost index by category, using one shared scale for baseline and target.Infrastructure - 42Licenses - 18Operations - 22Security and compliance - 8Backup and DR - 10Infrastructure - midpoint 32Licenses - midpoint 18Operations - midpoint 20Security and compliance - midpoint 8Backup and DR - midpoint 10On-Premises baselineTotal index: 100STACKIT targetMidpoint index: 88 (range: 72 to 105)Range-based outcome viewTotal effect range: −28% to +5% vs baselineCategory range modelInfrastructure: −40% to −10%Licenses: −20% to +15%Operations: −25% to +10%Security/compliance: −10% to +20%Backup/DR: −15% to +25%Recurring vs one-time costsThis stack covers recurring run costs only.Model one-time migration costs separately.
LIFT

Migration Plan

Go deep here: the migration plan is the shared control document connecting portfolio decisions with executable delivery waves.

Design and mobilizeMigration planOverview In 2 trails

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:

  • Design and Mobilize starts with wave planning and remains active through the planning of Wave 8 (up to Week 3).
  • Migrate starts already in Week 3 and continues through the remaining timeline.
  • Pilot wave and adjustments: Wave 1 is a shorter pilot wave for initial validation, followed by targeted setup adjustments during the first production waves.

The detailed setup scope is documented in its dedicated chapter: Migration Factory Setup.

Swipe sideways to see the whole diagram
Wave model across phases and modules Timeline of wave-based planning and migration execution with Portfolio Team and Migration Team handover pattern. Design and Mobilize phase Migrate phase Migration Factory Setup Factory Setup Adjustment Small Factory Adjustments Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Wave 1 Wave 2 Wave 3 Wave 4 Wave 5 Wave 6 Wave 7 Wave 8 PT Plan PT Plan PT Plan PT Plan PT Plan PT Plan PT Plan PT Plan MT Pilot wave MT Migration MT Migration MT Migration MT Migration MT Migration MT Migration MT Migration PT Portfolio Team MT Migration Team

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.

SAFE

Landing Zone

Go deep here: set up the shared platform baseline before application teams begin migration waves.

Design and mobilizeLanding zonesOverview In 6 trails

The following visual summarizes the core components that should be addressed for a reliable platform baseline.

Landing zone core components Six building blocks of a secure landing zone. Landing zone core componentsThe six building blocks of a secure platform foundation on STACKIT.Account GovernanceAccount GovernanceHow do I structure my projects?Identity & Access ManagementIdentity & Access ManagementWho can do what on the platform?Security & ComplianceSecurity & ComplianceHow do I monitor and protect?Network ArchitectureNetwork ArchitectureHow are components securely connected?Cost Management and ControlCost Management and ControlHow do I keep spending in control?Automation (IaC)Automation (IaC)How is everything delivered and managed?
  • Control and risk reduction: Enforce security and compliance controls consistently across teams.
  • Scalable delivery baseline: Enable repeatable provisioning patterns for multiple migration waves.
  • Clear responsibilities: Define ownership boundaries for platform, security, and application teams.
  • Faster migration throughput: Avoid redesigning core controls for each application move.

Start the landing-zone stream as early as possible, in parallel with discovery.

  • Too late: Productive migrations are blocked because mandatory controls are not yet available.
  • Too early without discovery feedback: Application constraints are missed and later cause rework.

The practical model is a dual track: establish the platform baseline early, then refine application landing zone templates as discovery insights mature.

Two layers: Platform and Application Landing Zones

Section titled “Two layers: Platform and Application Landing Zones”

Platform Landing Zone

Company-wide foundation for governance, identity, security, networking, cost controls, and automation.

Open Platform Landing Zone

Application Landing Zone

Workload-specific implementation patterns derived from the platform baseline and discovery findings.

Open Application Landing Zone
STACKIT LogoSTACKIT Logo
Account Governance STACKIT · Design And Mobilize › Landing Zones Open page ↗
STACKIT LogoSTACKIT Logo
Network Architecture STACKIT · Design And Mobilize › Landing Zones Open page ↗
STACKIT LogoSTACKIT Logo
STACKIT Landing Zone Accelerator STACKIT · Blueprint Open asset ↗
OPS

Target Operating Model

Give the Target Operating Model its own moment: it defines how the platform is run, staffed, and governed once workloads land.

Design and mobilizeTarget Operating ModelOverview In 1 trail

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.

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.

WARN

Enablement

Show how readiness findings become an operating enablement system: CCoE ownership, role-based STACKIT learning, and trusted documentation with AI-assisted guidance.

Design and mobilizeEnablementOverview In 1 trail

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.

  1. Assign ownership for migration standards, decisions, and capability development.
  2. Map readiness and role gaps to learning paths, workshops, and practical exercises.
  3. Curate authoritative documentation, migration decisions, and reusable references.
  4. Verify capability before each wave and feed lessons learned back into all three areas.

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:

  • turn readiness findings into owned remediation and enablement actions;
  • define which standards are mandatory and where teams can make local decisions;
  • maintain approved landing-zone, architecture, security, FinOps, and operations patterns;
  • coordinate role-based learning with migration-wave demand;
  • provide office hours, coaching, and escalation paths for delivery teams;
  • capture feedback, exceptions, and proven practices from each wave.
Cloud Framework Build the Cloud Centre of Excellence Open page
STEP

Documentation and Reference

Create a trusted reference path for each migration role using authoritative STACKIT product documentation, migration decisions, and evidence.

Design and mobilizeEnablementOverview In 1 trail

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:

  • official product behavior, prerequisites, limits, release information, and operational guidance;
  • platform and developer tooling, including APIs, CLI, SDKs, and infrastructure-as-code providers;
  • approved target patterns, architecture decisions, controls, and exceptions;
  • runbooks, validation evidence, handover records, and known issues for each migration wave;
  • clear ownership, review dates, and links back to the authoritative source.
CloudMent LogoCloudMent Logo
CloudMent AI-Powered Cloud Advisor CloudMent · Software Open asset ↗

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.

  • Rapid Discovery and Readiness Assessment: Captures application landscape information and functional or non-functional requirements to create first readiness and portfolio views.
  • Discovery and Design: Maps AWS, Azure, and Google Cloud services to STACKIT equivalents with fit ratings and supports R-strategy selection during design.
  • Business Case: Estimates STACKIT monthly run rates from pricing context and generates decision-support figures for migration planning.
  • Enablement: Provides a guided advisory interface for teams learning STACKIT service options, Terraform patterns, and architecture decisions.
  • Requirements-driven assessment: Turns workload descriptions, inventories, or CMDB inputs into cloud readiness, R-strategy, target architecture, and business-case drafts.
  • Grounded advisory: Uses STACKIT documentation and provider context so recommendations can be checked through cited sources.
  • Source-to-target mapping: Compares hyperscaler services with STACKIT alternatives and labels direct fits, partial fits, and gaps.
  • Interactive design support: Builds and refines target architecture options with service mapping, cost estimates, and Terraform drafts.
STEP

Migration Factory Setup

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.

Migration Factory Setup Four stages lead from confirmed migration demand through collaboration and enablement to a tested, scalable migration factory. From approved design to a scalable factory. Build delivery model, interfaces, tooling, and runbooks together, then prove them before scaling. 1 ALIGN Demand and model Volume, mix, and throughput Ownership, KPIs, and escalation 2 CONNECT Teams and cadence Clear delivery interfaces Decision and communication rhythm 3 ENABLE Toolchain and runbooks Tools for each migration pattern Checkpoints, rollback, and handover 4 PROVE Wave and cutover Scope, window, and communication Review pilot wave and refine Outcome: approved, repeatable setup for scaled wave execution
Four stages lead from confirmed migration demand through collaboration and enablement to a tested, scalable migration factory.
Runbook Readiness and Tooling

Bring runbook gates and tool selection criteria together in one traceable approval for wave execution.

Runbook Readiness and Tooling Four runbook gates and five tooling criteria converge into one approval for wave execution. Two readiness axes. One reliable wave approval. Execution instructions and toolchain must both be traceable, integrated, and rollback-ready. RUNBOOK READINESS Four gates secure execution 1Technical 2Operations 3Business 4Recovery Versioned steps, approvals, evidence, and clear triggers TOOLING READINESS Five criteria keep the toolchain stable Pattern fit Automation Auditability Integration Operational stability Minimum baseline with fallback for critical windows GO FOR THE WAVE Runbook and toolchain approved together
Four runbook gates and five tooling criteria converge into one approval for wave execution.
AUTO

Migrate

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.

End-to-End Migration Wave Flow Four sequential stages lead from wave approval through preparation and cutover to stabilization and handover. Every wave follows the same controlled factory flow. Secure scope and baseline, execute migration, prove acceptance, and hand over safely to operations. 1 APPROVE Scope and baseline Window, rollback, and ownership Freeze versions and dependencies 2 PREPARE Readiness and R-path Validate source and target Run playbook by archetype 3 CUT OVER Cutover and acceptance Route traffic to STACKIT safely Validate tech, function, operations 4 STABILIZE Learn and hand over Resolve findings in short loops Hand over to Optimize and Operate Traceable wave completion: accepted, stabilized, and fully handed over
Four stages lead from wave approval and readiness through cutover and acceptance to stabilization and handover to Optimize and Operate.
LIVE

Optimize

Keep this concise: Optimize turns freshly migrated workloads into cost- and performance-tuned steady-state services.

MigrateOptimizeOverview In 7 trails

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.

  1. Collect runtime evidence: utilization, latency, error rates, throughput, and cost drivers.
  2. Identify bottlenecks and waste patterns at workload, platform, and data layers.
  3. Prioritize actions by business impact, risk reduction, and FinOps effect.
  4. Implement tuning changes in controlled increments.
  5. Validate outcomes against SLO, reliability, and cost targets.
  6. Feed lessons learned into future migration waves and operating standards.
  • Rightsizing: Align compute, storage, and network capacity with actual demand profiles.
  • Performance tuning: Improve latency and throughput through configuration, scaling, and architecture adjustments.
  • Reliability hardening: Reduce incident frequency through better resilience, observability, and failure handling.
  • FinOps controls: Improve cost transparency, remove waste, and optimize run-rate efficiency.
GOAL

Run

Close the journey briefly with the Run phase module map so the audience sees where migration outcomes ultimately land.

Overview In 2 trails

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.

Swipe sideways to see the whole diagram
Run phase module model From migration stabilization to durable cloud operations on STACKIT. Run phase module modelFrom migration stabilization to durable cloud operations on STACKIT.Run flowMigrate handoffCutover complete, known risk listHypercarePost-cutover stabilization, fast remediation bridgeOperateSteady-state cloud operations: reliability, security, efficiencySupportIncidents and service requests, shared responsibility rulesCustomer SuccessCentral contact point, adoption and value realizationSemantic mapBridge stageMigrate to Run transition contextTechnical streamHypercare and Operate steady-state executionOperations streamOperate execution and governance cadenceService streamSupport, incidents, and requestsValue streamCustomer success and adoption scaling
Hypercare
  1. Confirm cutover baseline and define Hypercare entry criteria.
  2. Track incidents, instability patterns, and operational blind spots daily.
  3. Prioritize remediation by business impact and service criticality.
  4. Implement fixes with controlled change windows and rollback readiness.
  5. Verify stabilization criteria and close unresolved risks with clear ownership.
  6. Exit Hypercare when service, observability, and support readiness are accepted.
  • Post-cutover defect closure: Resolve migration-related errors and service degradations.
  • Monitoring completion: Add missing metrics, dashboards, and alert thresholds.
  • Runbook maturity: Refine troubleshooting, escalation, and rollback procedures.
  • Knowledge transfer preparation: Structure findings for operating model handover.
Trail historyActive 2 of the last 12 weeksLWUpdatedNo updates · 1 bar = 1 week i
Maintainer
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081Contributed in STACKIT
Show full history (1 more)