---
title: "Migration at a Glance"
description: "Fast, image-first tour of the STACKIT Migration Framework for trade-fair booths and quick briefings: one visual per phase and module, looping automatically."
scfTrail:
  tags: ["migration-framework", "overview", "kiosk", "trade-fair", "visual"]
  maintainers:
    - user: "lukas.weberruss"
      role: true
      website: true
    - name: "Carsten Fraszczak"
    - name: "Georg Deil"
  steps:
    - style: "compass"
      id: "cloud-journey"
      title: "The Cloud Journey"
      trailContext: "Start at the tourist information office, prepare at basecamp, and follow the path to migration, operations, and innovation. Ask where your organization stands today. These six illustrated stations are a simplified story, not the formal framework phases."
      imageSrc: "contributors/stackit/files/migration/migration-wimmelbild.webp"
      imageAlt: "Mountain journey to STACKIT with German signs for orientation, strategy, preparation, migration, operations, and innovation, plus basecamp and a landing zone lodge"

    - style: "compass"
      id: "kiosk-migration-phases"
      title: "Migration Phases"
      imageSrc: "migration/files/migration-framework-overview.svg"
      imageAlt: "STACKIT Migration Framework phase overview from Assess through Design and Mobilize and Migrate to Run"

    - 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: "kiosk-rapid-discovery"
      title: "Rapid Discovery"
      imageSrc: "migration/assess/rapid-discovery/files/rapid-discovery-process.svg"
      imageAlt: "Rapid Discovery process turning raw source data into a decision-ready baseline"

    - role: sub
      id: "readiness-assessment"
      title: "Readiness Assessment"
      trailContext: "Assess technical, process, personnel, financial, and governance readiness, then assign every gap to an owner and migration-wave gate."
      imageSrc: "migration/files/readiness-assessment-at-a-glance.svg"
      imageAlt: "Five readiness dimensions leading from validated evidence to an owned backlog and migration-wave gates"

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

    - role: sub
      id: "kiosk-discovery"
      title: "Discovery"
      imageSrc: "migration/design-and-mobilize/discovery/files/discovery-analysis-flow.svg"
      imageAlt: "Discovery analysis flow turning technical and stakeholder input into decision-ready outputs"

    - role: sub
      id: "kiosk-design"
      title: "Design"
      imageSrc: "migration/files/r-strategy-method.svg"
      imageAlt: "R-strategy method with seven migration paths: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire"

    - role: sub
      id: "service-portfolio"
      title: "Explore the STACKIT Service Portfolio"
      trailContext: "Use the interactive portfolio to connect migration design decisions with the available STACKIT target 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"

    - role: sub
      id: "kiosk-business-case"
      title: "Business Case"
      imageSrc: "migration/design-and-mobilize/business-case/files/business-case-r-strategy-investment-value-matrix-en.svg"
      imageAlt: "R-strategy investment versus long-term value matrix for business case decisions"

    - role: sub
      id: "kiosk-migration-plan"
      title: "Migration Plan"
      imageSrc: "migration/design-and-mobilize/migration-plan/files/migration-plan-phase-module-model.svg"
      imageAlt: "Phase and module model for migration wave planning"

    - role: sub
      id: "kiosk-landing-zone"
      title: "Landing Zone"
      imageSrc: "migration/design-and-mobilize/landing-zones/files/landing-zone-core-components-map-en.svg"
      imageAlt: "Core components of a STACKIT landing zone"

    - 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: "kiosk-landing-zone-accelerator"
      title: "STACKIT Landing Zone Accelerator"
      imageSrc: "contributors/stackit/files/migration/landing-zone-accelerator-architecture.svg"
      imageAlt: "Architecture overview of the STACKIT Landing Zone Accelerator"

    - role: sub
      id: "enablement"
      title: "Enablement"
      trailContext: "Prepare migration teams through CCoE ownership, role-based STACKIT University learning, trusted documentation, and validated AI guidance."
      imageSrc: "migration/files/enablement-at-a-glance.svg"
      imageAlt: "Three migration enablement capabilities: Center of Excellence, trainings and learning paths, and documentation and reference"

    - 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."
      pageId: "migration/migrate/migrate/overview/#end-to-end-factory-flow"

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

    - style: "rocket"
      id: "isv-overview"
      title: "ISV Onboarding Overview"
      trailContext: "One form on the Marketplace assigns you a dedicated Partner Manager, and a 30-to-45-minute discovery call establishes mutual fit before either side invests engineering or legal time. Bring a business owner and a technical lead — the call covers both."
      pageId: "isv/index"

    - role: sub
      style: "chart"
      id: "isv-kickoff"
      title: "ISV: Build the Joint Business Case"
      trailContext: "Pricing model, resource footprint, target verticals and revenue expectations turn a conversation into a business case. The same commercial parameters agreed here become billing SKUs much later, which is why loose answers are expensive."
      pageId: "isv/kickoff-and-strategy-alignment"

    - role: sub
      style: "stairs"
      id: "isv-poc"
      title: "ISV: Deploy the Proof of Concept"
      trailContext: "Tenancy strategy, landing zone, resilience requirements and a formal architectural blueprint mapped to STACKIT services — then automate it. Manual provisioning through the portal does not survive the quality gate."
      pageId: "isv/technical-proof-of-concept"

    - role: sub
      style: "shield"
      id: "isv-es3"
      title: "ISV: Pass the ES3 Self Assessment"
      trailContext: "Nine sovereignty dimensions, each checked contractually, organizationally, and technically, and condensed into one of four maturity levels from Initial to Future-Proof. The minimum principle applies: your overall level is the lowest level you reach in any single dimension."
      pageId: "isv/es3-self-assessment"

    - role: sub
      style: "gondola"
      id: "isv-placement"
      title: "ISV: Turn the Product Into an Offer"
      trailContext: "The Product Delivery Sheet is the single document the storefront entry and the billing SKUs are built from. Then choose your depth: a standard listing with manual fulfilment, or API integration with automated provisioning and metering."
      pageId: "isv/placement-and-marketplace-enablement"

  presentations:
    - id: "trade-fair-loop"
      label: "Trade Fair Loop"
      description: "Fully automated, image-first slide loop for unattended trade-fair booths: highlights cycle continuously without an agenda."
      default: true
      launch: true
      preset: "kiosk"
      fullscreen: true
      agenda: false
      steps:
        - "cloud-journey"
        - "kiosk-migration-phases"
        - "assess"
        - "kiosk-rapid-discovery"
        - "readiness-assessment"
        - "design-and-mobilize"
        - "kiosk-discovery"
        - "kiosk-design"
        - "service-portfolio"
        - "design-use-cases"
        - "design-target-pattern"
        - "design-runbook"
        - "kiosk-business-case"
        - "kiosk-migration-plan"
        - "kiosk-landing-zone"
        - "landing-zone-governance"
        - "landing-zone-network"
        - "kiosk-landing-zone-accelerator"
        - "enablement"
        - "migrate"
        - "optimize"
        - "run"
        - "isv-overview"
        - "isv-kickoff"
        - "isv-poc"
        - "isv-es3"
        - "isv-placement"
source_url: "https://framework.stackit.cloud/migration/trails/stackit/migration-at-a-glance/"
source_file: "docs/migration/trails/stackit/migration-at-a-glance.mdx"
---

## Steps

### 1. The Cloud Journey

Stage: `compass`

Start at the tourist information office, prepare at basecamp, and follow the path to migration, operations, and innovation. Ask where your organization stands today. These six illustrated stations are a simplified story, not the formal framework phases.

### 2. Migration Phases

Stage: `compass`

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

### 4. Rapid Discovery

### 5. Readiness Assessment

Assess technical, process, personnel, financial, and governance readiness, then assign every gap to an owner and migration-wave gate.

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

### 7. Discovery

### 8. Design

### 9. Explore the STACKIT Service Portfolio

Use the interactive portfolio to connect migration design decisions with the available STACKIT target 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`

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

### 11. Select the Target Pattern and Runtime

### 12. Prepare the Runbook and Cutover

### 13. Business Case

### 14. Migration Plan

### 15. Landing Zone

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

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

### 18. STACKIT Landing Zone Accelerator

### 19. Enablement

Prepare migration teams through CCoE ownership, role-based STACKIT University learning, trusted documentation, and validated AI guidance.

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

Page: [/migration/migrate/migrate/overview/#end-to-end-factory-flow](/migration/migrate/migrate/overview/#end-to-end-factory-flow) — source: [/raw/migration/migrate/migrate/overview.md](/raw/migration/migrate/migrate/overview.md), section `#end-to-end-factory-flow`

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

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

### 23. ISV Onboarding Overview

Stage: `rocket`

One form on the Marketplace assigns you a dedicated Partner Manager, and a 30-to-45-minute discovery call establishes mutual fit before either side invests engineering or legal time. Bring a business owner and a technical lead — the call covers both.

Page: [/isv/](/isv/) — source: [/raw/isv.md](/raw/isv.md)

### 24. ISV: Build the Joint Business Case

Stage: `chart`

Pricing model, resource footprint, target verticals and revenue expectations turn a conversation into a business case. The same commercial parameters agreed here become billing SKUs much later, which is why loose answers are expensive.

Page: [/isv/kickoff-and-strategy-alignment/](/isv/kickoff-and-strategy-alignment/) — source: [/raw/isv/kickoff-and-strategy-alignment.md](/raw/isv/kickoff-and-strategy-alignment.md)

### 25. ISV: Deploy the Proof of Concept

Stage: `stairs`

Tenancy strategy, landing zone, resilience requirements and a formal architectural blueprint mapped to STACKIT services — then automate it. Manual provisioning through the portal does not survive the quality gate.

Page: [/isv/technical-proof-of-concept/](/isv/technical-proof-of-concept/) — source: [/raw/isv/technical-proof-of-concept.md](/raw/isv/technical-proof-of-concept.md)

### 26. ISV: Pass the ES3 Self Assessment

Stage: `shield`

Nine sovereignty dimensions, each checked contractually, organizationally, and technically, and condensed into one of four maturity levels from Initial to Future-Proof. The minimum principle applies: your overall level is the lowest level you reach in any single dimension.

Page: [/isv/es3-self-assessment/](/isv/es3-self-assessment/) — source: [/raw/isv/es3-self-assessment.md](/raw/isv/es3-self-assessment.md)

### 27. ISV: Turn the Product Into an Offer

Stage: `gondola`

The Product Delivery Sheet is the single document the storefront entry and the billing SKUs are built from. Then choose your depth: a standard listing with manual fulfilment, or API integration with automated provisioning and metering.

Page: [/isv/placement-and-marketplace-enablement/](/isv/placement-and-marketplace-enablement/) — source: [/raw/isv/placement-and-marketplace-enablement.md](/raw/isv/placement-and-marketplace-enablement.md)

