---
title: "Migration Framework Walkthrough"
description: "Comprehensive migration walkthrough from Assess through Design and Mobilize and Migrate to Run, using the framework's core visuals and decision models."
scfTrail:
  tags: ["migration-framework", "overview", "assess", "design-and-mobilize", "migrate", "run"]
  maintainers:
    - user: "lukas.weberruss"
      role: true
      website: true
  steps:
    - style: "compass"
      id: "migration-phases"
      title: "Migration Phases"
      trailContext: "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."
      description: "Use the phase model as the agenda frame for the rest of the story: assess quickly, design and mobilize thoroughly, migrate in controlled waves, then stabilize and run."
      pageId: "migration/#framework-overview"

    - style: "hut"
      id: "assess"
      title: "Assess"
      trailContext: "Frame Assess as the fast, low-commitment phase that builds an initial fact base and qualifies migration intent before deeper design work starts."
      description: "Assess combines rapid portfolio discovery, commercial framing, and stakeholder alignment activities that stay intentionally lightweight."
      pageId: "migration/assess/#understanding-this-phase"

    - role: sub
      id: "rapid-discovery"
      title: "Rapid Discovery"
      trailContext: "Give Rapid Discovery real depth: it is the structured starting point that produces an evidence-based view of the portfolio and its migration potential."
      description: "Walk through the Rapid Discovery process end to end, from intake to a prioritized, migration-ready portfolio view."
      pageId: "migration/assess/rapid-discovery/overview/#rapid-discovery-process-at-a-glance"

    - role: sub
      id: "rapid-discovery-assessment"
      title: "Accelerate Portfolio Assessment"
      trailContext: "Use AI-supported analysis to consolidate early portfolio evidence and highlight where deeper investigation is needed."
      description: "Position the advisor as a fast assessment aid that surfaces useful signals, while technical and business evidence still requires validation."
      assetId: "migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview"

    - role: sub
      id: "tco-report"
      title: "TCO Report"
      trailContext: "Keep this brief and summarize only the decision-relevant findings from the TCO analysis."
      description: "Use TCO as a compact decision tool for qualifying migration value and budget direction before detailed design begins."
      pageId: "advisory/business-case-and-financial-planning/tco-analysis/#what-tco-analysis-is-actually-for"

    - role: sub
      id: "deepdive-workshop"
      title: "Deepdive Workshop"
      trailContext: "Mention briefly as a sales-supported enablement format that clarifies technical questions early."
      description: "The Deepdive Workshop builds confidence in STACKIT services and creates qualified follow-up topics for discovery and design."
      pageId: "migration/assess/deepdive-workshop/overview/#overview"

    - role: sub
      id: "briefings-and-workshop"
      title: "Briefings and Workshops"
      trailContext: "Mention briefly as the lightweight alignment format for early-stage topics that do not yet need a full workshop."
      description: "Briefings and Workshops clarify scope, expectations, and open questions between customer and delivery stakeholders."
      pageId: "migration/assess/briefings-and-workshop/overview/#overview"

    - role: sub
      id: "readiness-assessment"
      title: "Readiness Assessment"
      trailContext: "Use the questionnaire, expert workshops, and five-dimension scorecard as the baseline, then translate open findings into migration constraints, owners, evidence, and wave gates."
      description: "Assess technical, process, personnel, financial, and governance foundations before workloads enter detailed migration planning."
      pageId: "migration/assess/readiness-assessment/overview/"

    - style: "t-bar"
      id: "design-and-mobilize"
      title: "Design and Mobilize"
      trailContext: "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."
      description: "This phase covers discovery evidence, target design, business case, migration planning, landing zone, target operating model, enablement, and factory setup."
      pageId: "migration/design-and-mobilize/#understanding-this-phase"

    - style: "stairs"
      id: "discovery"
      title: "Discovery"
      trailContext: "Go deep here: Discovery turns the rapid assessment into migration-ready evidence about workloads, dependencies, constraints, and stakeholders."
      description: "Use the visual analysis flow to show how technical and human-driven evidence streams converge into validated design and wave-planning inputs."
      pageId: "migration/design-and-mobilize/discovery/overview/#discovery-process-at-a-glance"

    - role: sub
      id: "discovery-evidence-and-analysis"
      title: "Validate Evidence and Patterns"
      left:
        - pageId: "migration/design-and-mobilize/discovery/overview/#two-evidence-streams-technical-vs-human-driven"
      right:
        - pageId: "migration/design-and-mobilize/discovery/overview/#typical-analysis-patterns-in-discovery-tooling"

    - style: "stairs"
      id: "design"
      title: "Design"
      trailContext: "Go deep here: use the R-strategy graphic as the anchor for explaining how each application's migration approach is chosen and justified."
      description: "Present Design as the point where evidence becomes a target architecture, R-strategy, and delivery approach."
      pageId: "migration/design-and-mobilize/design/overview/#r-strategy-as-core-design-method"

    - style: "compass"
      id: "service-portfolio"
      title: "Explore the STACKIT Service Portfolio"
      trailContext: "Use the interactive portfolio to connect the target architecture and R-strategy with available STACKIT services and access tools."
      assetId: "architecture/assetcontainer/stackit/stackit-service-portfolio-map.mdx#interactive-service-portfolio"

    - role: sub
      id: "design-use-cases"
      title: "Classify Workload Use Cases"
      trailContext: "Take a deeper look at the use-case lens: it complements R-strategy by clarifying what is actually migrated, not just how."
      description: "Use the use-case catalog to classify requests such as runtime, container platform, data, identity, network, or integration migration."
      pageId: "migration/design-and-mobilize/design/workload-migration-use-cases/#use-case-categories-in-scope"

    - role: sub
      id: "design-target-pattern"
      title: "Select the Target Pattern and Runtime"
      left:
        - pageId: "migration/design-and-mobilize/design/cloud-design-patterns/#service-model-decision-guide-iaas-paas-saas"
      right:
        - pageId: "migration/design-and-mobilize/design/cloud-design-patterns/#runtime-selection-guide-for-typical-stackit-targets"

    - role: sub
      id: "design-runbook"
      title: "Prepare the Runbook and Cutover"
      left:
        - pageId: "migration/design-and-mobilize/design/runbook/#mandatory-runbook-chapters"
      right:
        - pageId: "migration/design-and-mobilize/design/runbook/#quality-criteria-for-a-good-runbook"

    - style: "chart"
      id: "business-case"
      title: "Business Case"
      trailContext: "Go deep here: connect each R-strategy choice with one-time investment, run-cost economics, and expected long-term value."
      description: "Use the R-strategy investment-vs-value matrix to show how design decisions translate into a defensible business case."
      pageId: "migration/design-and-mobilize/business-case/overview/#r-strategy-matrix-for-one-time-investment-versus-long-term-value"

    - role: sub
      id: "business-case-cost-stack"
      title: "Break Down the Cost Stack"
      trailContext: "Ground the business case in a concrete cost stack example so the audience can see where migration cost actually comes from."
      pageId: "migration/design-and-mobilize/business-case/overview/#cost-stack-example"

    - style: "chairlift"
      id: "migration-plan"
      title: "Migration Plan"
      trailContext: "Go deep here: the migration plan is the shared control document connecting portfolio decisions with executable delivery waves."
      description: "Use the phase-and-module model to show how wave planning stays aligned with the overall framework as it executes."
      pageId: "migration/design-and-mobilize/migration-plan/overview/#phase-and-module-model-in-wave-planning"

    - role: sub
      id: "migration-plan-factory-model"
      title: "Align Waves and Factory Delivery"
      trailContext: "Explain how wave planning, standardized roles, intake, tooling, governance, and feedback work together without mixing portfolio and delivery decisions."
      pageId: "migration/design-and-mobilize/migration-plan/overview/#migration-factory-operating-model"

    - style: "shield"
      id: "landing-zone"
      title: "Landing Zone"
      trailContext: "Go deep here: set up the shared platform baseline before application teams begin migration waves."
      description: "A landing zone provides reusable guardrails and core services for secure, governable workload delivery."
      pageId: "migration/design-and-mobilize/landing-zones/overview/#core-components"

    - role: sub
      id: "landing-zone-governance"
      title: "Define Governance Hierarchy"
      trailContext: "Clarify how accounts, ownership, and policies are organized before workloads are onboarded."
      pageId: "migration/design-and-mobilize/landing-zones/account-governance/#governance-hierarchy"

    - role: sub
      id: "landing-zone-network"
      title: "Design the Network Architecture"
      trailContext: "Give network architecture its own moment: it is where segmentation, routing, and hybrid connectivity guardrails are actually decided."
      description: "Use the hub-and-spoke reference topology to show how a central Network Area, routing tables, and a shared firewall govern traffic between landing zones and on-premises."
      pageId: "migration/design-and-mobilize/landing-zones/network-architecture/#reference-topology"

    - role: sub
      id: "landing-zone-accelerator"
      title: "STACKIT Landing Zone Accelerator"
      trailContext: "Point briefly to the STACKIT Landing Zone Accelerator as the reusable implementation asset for this module."
      description: "Use the accelerator's architecture to discuss how governance and network decisions become implementable, repeatable controls."
      assetId: "migration/assetcontainer/stackit/landing-zone-foundation-opentofu/#accelerator-architecture"

    - style: "chart"
      id: "target-operating-model"
      title: "Target Operating Model"
      trailContext: "Give the Target Operating Model its own moment: it defines how the platform is run, staffed, and governed once workloads land."
      description: "Cover the core TOM capability areas and how they connect to the landing zone and to steady-state operations in Run."
      pageId: "migration/design-and-mobilize/operating-model/overview/#tom-capability-areas"

    - style: "crevasse"
      id: "enablement"
      title: "Enablement"
      trailContext: "Show how readiness findings become an operating enablement system: CCoE ownership, role-based STACKIT learning, and trusted documentation with AI-assisted guidance."
      description: "Enablement prepares people and governance before each wave, then feeds proven practices and lessons learned back into the organization."
      pageId: "migration/design-and-mobilize/enablement/overview/#overview"

    - role: sub
      id: "enablement-ccoe"
      title: "Center of Excellence"
      trailContext: "Give the CCoE ownership for migration standards, coaching, decisions, capability development, and learning across migration waves."
      pageId: "migration/design-and-mobilize/enablement/overview/#center-of-excellence"

    - id: "enablement-reference"
      title: "Documentation and Reference"
      trailContext: "Create a trusted reference path for each migration role using authoritative STACKIT product documentation, migration decisions, and evidence."
      pageId: "migration/design-and-mobilize/enablement/overview/#documentation--reference"

    - role: sub
      id: "enablement-ai"
      title: "AI-assisted Enablement"
      trailContext: "Use CloudMent for service mapping, architecture alternatives, and Terraform drafts, then have accountable specialists validate its source-based recommendations."
      assetId: "migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview"

    - style: "stairs"
      id: "migration-factory-setup"
      title: "Migration Factory Setup"
      trailContext: "Go deep here: this is where an approved design becomes an executable, wave-scale delivery factory."
      description: "Cover partner model, tooling, interfaces, and runbook finalization as the pillars of a factory-ready setup."
      imageSrc: "migration/files/migration-factory-setup-flow.svg"
      imageAlt: "Four stages lead from confirmed migration demand through collaboration and enablement to a tested, scalable migration factory."

    - role: sub
      id: "migration-factory-quality-gates"
      title: "Runbook Readiness and Tooling"
      trailContext: "Bring runbook gates and tool selection criteria together in one traceable approval for wave execution."
      imageSrc: "migration/files/runbook-tooling-readiness.svg"
      imageAlt: "Four runbook gates and five tooling criteria converge into one approval for wave execution."

    - style: "gondola"
      id: "migrate"
      title: "Migrate"
      trailContext: "Keep this as concise as Assess and focus on the end-to-end factory flow that runs every wave to completion."
      description: "The end-to-end factory flow is the core chapter here: intake, run, validate, and hand over each wave through the factory."
      imageSrc: "migration/files/migrate-wave-flow.svg"
      imageAlt: "Four stages lead from wave approval and readiness through cutover and acceptance to stabilization and handover to Optimize and Operate."

    - style: "rocket"
      id: "optimize"
      title: "Optimize"
      trailContext: "Keep this concise: Optimize turns freshly migrated workloads into cost- and performance-tuned steady-state services."
      description: "Highlight the typical optimization focus areas and how they move from theory into implemented, evidenced changes."
      pageId: "migration/migrate/optimize/overview/#understanding-the-optimize-module"

    - style: "summit"
      id: "run"
      title: "Run"
      trailContext: "Close the journey briefly with the Run phase module map so the audience sees where migration outcomes ultimately land."
      description: "Run combines short-term stabilization in Hypercare with long-term service operations in Operate, Support, and Customer Success."
      pageId: "migration/run/#run-phase-module-map"

    - role: sub
      id: "hypercare"
      title: "Hypercare"
      left:
        - pageId: "migration/run/hypercare/overview/#hypercare-flow"
      right:
        - pageId: "migration/run/hypercare/overview/#typical-work-items"

  presentations:
    - id: "full-journey"
      label: "Full Journey"
      description: "Complete, presenter-ready walkthrough of the STACKIT Migration Framework covering every phase and module at the right depth for a general audience."
      default: true
      launch: true
      preset: "minimal"
      fullscreen: true
      agenda: true
      steps:
        - "migration-phases"
        - "assess"
        - id: "rapid-discovery"
          role: hidden
        - id: "rapid-discovery-assessment"
          role: hidden
        - id: "deepdive-workshop"
          role: hidden
        - id: "briefings-and-workshop"
          role: hidden
        - id: "readiness-assessment"
          role: hidden
        - "design-and-mobilize"
        - "discovery"
        - "design"
        - "service-portfolio"
        - id: "design-use-cases"
          role: hidden
        - id: "design-target-pattern"
          role: hidden
        - id: "design-runbook"
          role: hidden
        - "business-case"
        - id: "business-case-cost-stack"
          role: hidden
        - "migration-plan"
        - id: "migration-plan-factory-model"
          role: hidden
        - "landing-zone"
        - id: "landing-zone-governance"
          role: hidden
        - id: "landing-zone-network"
          role: hidden
        - id: "landing-zone-accelerator"
          role: hidden
        - "target-operating-model"
        - "enablement"
        - id: "enablement-ccoe"
          role: hidden
        - id: "enablement-reference"
          role: hidden
        - id: "enablement-ai"
          role: hidden
        - "migration-factory-setup"
        - id: "migration-factory-quality-gates"
          role: hidden
        - "migrate"
        - "optimize"
        - "run"
        - id: "hypercare"
          role: hidden
source_url: "https://framework.stackit.cloud/migration/trails/stackit/migration-framework-walkthrough/"
source_file: "docs/migration/trails/stackit/migration-framework-walkthrough.mdx"
---

## Steps

### 1. Migration Phases

Stage: `compass`

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.

Use the phase model as the agenda frame for the rest of the story: assess quickly, design and mobilize thoroughly, migrate in controlled waves, then stabilize and run.

Page: [/migration/#framework-overview](/migration/#framework-overview) — source: [/raw/migration.md](/raw/migration.md), section `#framework-overview`

### 2. Assess

Stage: `hut`

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

Assess combines rapid portfolio discovery, commercial framing, and stakeholder alignment activities that stay intentionally lightweight.

Page: [/migration/assess/#understanding-this-phase](/migration/assess/#understanding-this-phase) — source: [/raw/migration/assess.md](/raw/migration/assess.md), section `#understanding-this-phase`

### 3. Rapid Discovery

Give Rapid Discovery real depth: it is the structured starting point that produces an evidence-based view of the portfolio and its migration potential.

Walk through the Rapid Discovery process end to end, from intake to a prioritized, migration-ready portfolio view.

Page: [/migration/assess/rapid-discovery/overview/#rapid-discovery-process-at-a-glance](/migration/assess/rapid-discovery/overview/#rapid-discovery-process-at-a-glance) — source: [/raw/migration/assess/rapid-discovery/overview.md](/raw/migration/assess/rapid-discovery/overview.md), section `#rapid-discovery-process-at-a-glance`

### 4. Accelerate Portfolio Assessment

Use AI-supported analysis to consolidate early portfolio evidence and highlight where deeper investigation is needed.

Position the advisor as a fast assessment aid that surfaces useful signals, while technical and business evidence still requires validation.

Asset: [/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview](/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview) — source: [/raw/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor.md](/raw/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor.md), section `#overview`

### 5. TCO Report

Keep this brief and summarize only the decision-relevant findings from the TCO analysis.

Use TCO as a compact decision tool for qualifying migration value and budget direction before detailed design begins.

Page: [/advisory/business-case-and-financial-planning/tco-analysis/#what-tco-analysis-is-actually-for](/advisory/business-case-and-financial-planning/tco-analysis/#what-tco-analysis-is-actually-for) — source: [/raw/advisory/business-case-and-financial-planning/tco-analysis.md](/raw/advisory/business-case-and-financial-planning/tco-analysis.md), section `#what-tco-analysis-is-actually-for`

### 6. Deepdive Workshop

Mention briefly as a sales-supported enablement format that clarifies technical questions early.

The Deepdive Workshop builds confidence in STACKIT services and creates qualified follow-up topics for discovery and design.

Page: [/migration/assess/deepdive-workshop/overview/#overview](/migration/assess/deepdive-workshop/overview/#overview) — source: [/raw/migration/assess/deepdive-workshop/overview.md](/raw/migration/assess/deepdive-workshop/overview.md), section `#overview`

### 7. Briefings and Workshops

Mention briefly as the lightweight alignment format for early-stage topics that do not yet need a full workshop.

Briefings and Workshops clarify scope, expectations, and open questions between customer and delivery stakeholders.

Page: [/migration/assess/briefings-and-workshop/overview/#overview](/migration/assess/briefings-and-workshop/overview/#overview) — source: [/raw/migration/assess/briefings-and-workshop/overview.md](/raw/migration/assess/briefings-and-workshop/overview.md), section `#overview`

### 8. Readiness Assessment

Use the questionnaire, expert workshops, and five-dimension scorecard as the baseline, then translate open findings into migration constraints, owners, evidence, and wave gates.

Assess technical, process, personnel, financial, and governance foundations before workloads enter detailed migration planning.

Page: [/migration/assess/readiness-assessment/overview/](/migration/assess/readiness-assessment/overview/) — source: [/raw/migration/assess/readiness-assessment/overview.md](/raw/migration/assess/readiness-assessment/overview.md)

### 9. Design and Mobilize

Stage: `t-bar`

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.

This phase covers discovery evidence, target design, business case, migration planning, landing zone, target operating model, enablement, and factory setup.

Page: [/migration/design-and-mobilize/#understanding-this-phase](/migration/design-and-mobilize/#understanding-this-phase) — source: [/raw/migration/design-and-mobilize.md](/raw/migration/design-and-mobilize.md), section `#understanding-this-phase`

### 10. Discovery

Stage: `stairs`

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

Use the visual analysis flow to show how technical and human-driven evidence streams converge into validated design and wave-planning inputs.

Page: [/migration/design-and-mobilize/discovery/overview/#discovery-process-at-a-glance](/migration/design-and-mobilize/discovery/overview/#discovery-process-at-a-glance) — source: [/raw/migration/design-and-mobilize/discovery/overview.md](/raw/migration/design-and-mobilize/discovery/overview.md), section `#discovery-process-at-a-glance`

### 11. Validate Evidence and Patterns

### 12. Design

Stage: `stairs`

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

Present Design as the point where evidence becomes a target architecture, R-strategy, and delivery approach.

Page: [/migration/design-and-mobilize/design/overview/#r-strategy-as-core-design-method](/migration/design-and-mobilize/design/overview/#r-strategy-as-core-design-method) — source: [/raw/migration/design-and-mobilize/design/overview.md](/raw/migration/design-and-mobilize/design/overview.md), section `#r-strategy-as-core-design-method`

### 13. Explore the STACKIT Service Portfolio

Stage: `compass`

Use the interactive portfolio to connect the target architecture and R-strategy with available STACKIT services and access tools.

Asset: [/architecture/assetcontainer/stackit/stackit-service-portfolio-map/#interactive-service-portfolio](/architecture/assetcontainer/stackit/stackit-service-portfolio-map/#interactive-service-portfolio) — source: [/raw/architecture/assetcontainer/stackit/stackit-service-portfolio-map.md](/raw/architecture/assetcontainer/stackit/stackit-service-portfolio-map.md), section `#interactive-service-portfolio`

### 14. Classify Workload Use Cases

Take a deeper look at the use-case lens: it complements R-strategy by clarifying what is actually migrated, not just how.

Use the use-case catalog to classify requests such as runtime, container platform, data, identity, network, or integration migration.

Page: [/migration/design-and-mobilize/design/workload-migration-use-cases/#use-case-categories-in-scope](/migration/design-and-mobilize/design/workload-migration-use-cases/#use-case-categories-in-scope) — source: [/raw/migration/design-and-mobilize/design/workload-migration-use-cases.md](/raw/migration/design-and-mobilize/design/workload-migration-use-cases.md), section `#use-case-categories-in-scope`

### 15. Select the Target Pattern and Runtime

### 16. Prepare the Runbook and Cutover

### 17. Business Case

Stage: `chart`

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

Use the R-strategy investment-vs-value matrix to show how design decisions translate into a defensible business case.

Page: [/migration/design-and-mobilize/business-case/overview/#r-strategy-matrix-for-one-time-investment-versus-long-term-value](/migration/design-and-mobilize/business-case/overview/#r-strategy-matrix-for-one-time-investment-versus-long-term-value) — source: [/raw/migration/design-and-mobilize/business-case/overview.md](/raw/migration/design-and-mobilize/business-case/overview.md), section `#r-strategy-matrix-for-one-time-investment-versus-long-term-value`

### 18. Break Down the Cost Stack

Ground the business case in a concrete cost stack example so the audience can see where migration cost actually comes from.

Page: [/migration/design-and-mobilize/business-case/overview/#cost-stack-example](/migration/design-and-mobilize/business-case/overview/#cost-stack-example) — source: [/raw/migration/design-and-mobilize/business-case/overview.md](/raw/migration/design-and-mobilize/business-case/overview.md), section `#cost-stack-example`

### 19. Migration Plan

Stage: `chairlift`

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

Use the phase-and-module model to show how wave planning stays aligned with the overall framework as it executes.

Page: [/migration/design-and-mobilize/migration-plan/overview/#phase-and-module-model-in-wave-planning](/migration/design-and-mobilize/migration-plan/overview/#phase-and-module-model-in-wave-planning) — source: [/raw/migration/design-and-mobilize/migration-plan/overview.md](/raw/migration/design-and-mobilize/migration-plan/overview.md), section `#phase-and-module-model-in-wave-planning`

### 20. Align Waves and Factory Delivery

Explain how wave planning, standardized roles, intake, tooling, governance, and feedback work together without mixing portfolio and delivery decisions.

Page: [/migration/design-and-mobilize/migration-plan/overview/#migration-factory-operating-model](/migration/design-and-mobilize/migration-plan/overview/#migration-factory-operating-model) — source: [/raw/migration/design-and-mobilize/migration-plan/overview.md](/raw/migration/design-and-mobilize/migration-plan/overview.md), section `#migration-factory-operating-model`

### 21. Landing Zone

Stage: `shield`

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

A landing zone provides reusable guardrails and core services for secure, governable workload delivery.

Page: [/migration/design-and-mobilize/landing-zones/overview/#core-components](/migration/design-and-mobilize/landing-zones/overview/#core-components) — source: [/raw/migration/design-and-mobilize/landing-zones/overview.md](/raw/migration/design-and-mobilize/landing-zones/overview.md), section `#core-components`

### 22. Define Governance Hierarchy

Clarify how accounts, ownership, and policies are organized before workloads are onboarded.

Page: [/migration/design-and-mobilize/landing-zones/account-governance/#governance-hierarchy](/migration/design-and-mobilize/landing-zones/account-governance/#governance-hierarchy) — source: [/raw/migration/design-and-mobilize/landing-zones/account-governance.md](/raw/migration/design-and-mobilize/landing-zones/account-governance.md), section `#governance-hierarchy`

### 23. Design the Network Architecture

Give network architecture its own moment: it is where segmentation, routing, and hybrid connectivity guardrails are actually decided.

Use the hub-and-spoke reference topology to show how a central Network Area, routing tables, and a shared firewall govern traffic between landing zones and on-premises.

Page: [/migration/design-and-mobilize/landing-zones/network-architecture/#reference-topology](/migration/design-and-mobilize/landing-zones/network-architecture/#reference-topology) — source: [/raw/migration/design-and-mobilize/landing-zones/network-architecture.md](/raw/migration/design-and-mobilize/landing-zones/network-architecture.md), section `#reference-topology`

### 24. STACKIT Landing Zone Accelerator

Point briefly to the STACKIT Landing Zone Accelerator as the reusable implementation asset for this module.

Use the accelerator's architecture to discuss how governance and network decisions become implementable, repeatable controls.

Asset: [/migration/assetcontainer/stackit/landing-zone-foundation-opentofu/#accelerator-architecture](/migration/assetcontainer/stackit/landing-zone-foundation-opentofu/#accelerator-architecture) — source: [/raw/migration/assetcontainer/stackit/landing-zone-foundation-opentofu.md](/raw/migration/assetcontainer/stackit/landing-zone-foundation-opentofu.md), section `#accelerator-architecture`

### 25. Target Operating Model

Stage: `chart`

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

Cover the core TOM capability areas and how they connect to the landing zone and to steady-state operations in Run.

Page: [/migration/design-and-mobilize/operating-model/overview/#tom-capability-areas](/migration/design-and-mobilize/operating-model/overview/#tom-capability-areas) — source: [/raw/migration/design-and-mobilize/operating-model/overview.md](/raw/migration/design-and-mobilize/operating-model/overview.md), section `#tom-capability-areas`

### 26. Enablement

Stage: `crevasse`

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

Enablement prepares people and governance before each wave, then feeds proven practices and lessons learned back into the organization.

Page: [/migration/design-and-mobilize/enablement/overview/#overview](/migration/design-and-mobilize/enablement/overview/#overview) — source: [/raw/migration/design-and-mobilize/enablement/overview.md](/raw/migration/design-and-mobilize/enablement/overview.md), section `#overview`

### 27. Center of Excellence

Give the CCoE ownership for migration standards, coaching, decisions, capability development, and learning across migration waves.

Page: [/migration/design-and-mobilize/enablement/overview/#center-of-excellence](/migration/design-and-mobilize/enablement/overview/#center-of-excellence) — source: [/raw/migration/design-and-mobilize/enablement/overview.md](/raw/migration/design-and-mobilize/enablement/overview.md), section `#center-of-excellence`

### 28. Documentation and Reference

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

Page: [/migration/design-and-mobilize/enablement/overview/#documentation--reference](/migration/design-and-mobilize/enablement/overview/#documentation--reference) — source: [/raw/migration/design-and-mobilize/enablement/overview.md](/raw/migration/design-and-mobilize/enablement/overview.md), section `#documentation--reference`

### 29. AI-assisted Enablement

Use CloudMent for service mapping, architecture alternatives, and Terraform drafts, then have accountable specialists validate its source-based recommendations.

Asset: [/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview](/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor/#overview) — source: [/raw/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor.md](/raw/migration/assetcontainer/cloudment/cloudment-ai-powered-cloud-advisor.md), section `#overview`

### 30. Migration Factory Setup

Stage: `stairs`

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.

### 31. Runbook Readiness and Tooling

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

### 32. Migrate

Stage: `gondola`

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.

### 33. Optimize

Stage: `rocket`

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

Highlight the typical optimization focus areas and how they move from theory into implemented, evidenced changes.

Page: [/migration/migrate/optimize/overview/#understanding-the-optimize-module](/migration/migrate/optimize/overview/#understanding-the-optimize-module) — source: [/raw/migration/migrate/optimize/overview.md](/raw/migration/migrate/optimize/overview.md), section `#understanding-the-optimize-module`

### 34. Run

Stage: `summit`

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

Run combines short-term stabilization in Hypercare with long-term service operations in Operate, Support, and Customer Success.

Page: [/migration/run/#run-phase-module-map](/migration/run/#run-phase-module-map) — source: [/raw/migration/run.md](/raw/migration/run.md), section `#run-phase-module-map`

### 35. Hypercare