---
title: "Enterprise Cloud Migration & Architecture Blueprint"
description: "Structured cross-framework blueprint guiding enterprise migration workflows from initial application analysis down to automated operations on STACKIT."
scfTrail:
  tags: ["wip"]
  maintainers:
    - user: "tobias.mueller"
  steps:
    - style: "compass"
      title: "Strategic Preparation"
      id: "strategic-prep"
      trailContext: "Before any lines of code are written, platform teams evaluate cloud readiness and architectural requirements of legacy workloads using systematic analysis."
      assetId: "advisory/assetcontainer/tm/app-rationalization-6r"

    - style: "compass"
      title: "Decide the Migration Path"
      id: "migration-path"
      trailContext: "Turn the rationalization results into an explicit R-strategy decision per application. The decision criteria clarify when Relocate, Rehost, Replatform, Repurchase, Refactor, or Retain/Retire is the right route."
      pageId: "migration/design-and-mobilize/design/overview/#decision-criteria-by-r-strategy"

    - style: "stairs"
      title: "Infrastructure as Code Foundation"
      id: "iac-foundation"
      trailContext: "Build fundamental knowledge for Infrastructure as Code to describe the target STACKIT environment in a declarative, versioned, and auditable manner."
      assetId: "architecture/assetcontainer/tm/tm1-iac-terraform-basics#why-infrastructure-as-code-iac"
      
    - style: "shield"
      title: "Secure Network Connectivity"
      id: "network-connectivity"
      trailContext: "Establish an isolated Hub-and-Spoke network architecture. Centralized firewall rules and routing tables fully protect workloads from unauthorized access."
      assetId: "migration/assetcontainer/stackit/pfsense-firewall-connectivity-pattern"

    - style: "gondola"
      title: "Automated Migration Execution"
      id: "migration-execution"
      trailContext: "Execute the actual data and application migration onto the target infrastructure using a standardized, combined Terraform and Ansible runbook workflow."
      assetId: "migration/assetcontainer/stackit/rehost-automation-spring-boot-terraform-ansible"

    - style: "chart"
      title: "Wave Delivery at Factory Scale"
      id: "wave-delivery"
      trailContext: "Scale the automated migration pattern from a single application to governed waves: the end-to-end factory flow connects intake, run paths per migration strategy, and quality gates per wave."
      pageId: "migration/migrate/migrate/overview/#end-to-end-factory-flow"

    - style: "summit"
      title: "Post-Migration Optimization"
      id: "optimization"
      trailContext: "Following a successful cutover, platform teams utilize live monitoring via STACKIT Observability to detect over-provisioning and adjust capacities."
      assetId: "migration/assetcontainer/stackit/optimize-rehosted-spring-boot-observability-rightsizing"
  presentations:
    - id: exec
      label: "Executive overview"
      description: "Executive framing: headline steps in the agenda, infrastructure detail nested."
      steps:
        - strategic-prep
        - migration-path
        - { id: iac-foundation, role: sub }
        - { id: network-connectivity, role: sub }
        - migration-execution
        - wave-delivery
        - optimization
    - id: technical
      label: "Technical deep-dive"
      description: "Implementation-focused view: technical steps as agenda headlines, strategy nested."
      steps:
        - { id: strategic-prep, role: sub }
        - migration-path
        - iac-foundation
        - network-connectivity
        - migration-execution
        - wave-delivery
        - optimization
source_url: "https://framework.stackit.cloud/migration/trails/tm/enterprise-migration-journey/"
source_file: "docs/migration/trails/tm/enterprise-migration-journey.mdx"
---

## Steps

### 1. Strategic Preparation

Stage: `compass`

Before any lines of code are written, platform teams evaluate cloud readiness and architectural requirements of legacy workloads using systematic analysis.

Asset: [/advisory/assetcontainer/tm/app-rationalization-6r/](/advisory/assetcontainer/tm/app-rationalization-6r/) — source: [/raw/advisory/assetcontainer/tm/app-rationalization-6r.md](/raw/advisory/assetcontainer/tm/app-rationalization-6r.md)

### 2. Decide the Migration Path

Stage: `compass`

Turn the rationalization results into an explicit R-strategy decision per application. The decision criteria clarify when Relocate, Rehost, Replatform, Repurchase, Refactor, or Retain/Retire is the right route.

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

### 3. Infrastructure as Code Foundation

Stage: `stairs`

Build fundamental knowledge for Infrastructure as Code to describe the target STACKIT environment in a declarative, versioned, and auditable manner.

Asset: [/architecture/assetcontainer/tm/tm1-iac-terraform-basics/#why-infrastructure-as-code-iac](/architecture/assetcontainer/tm/tm1-iac-terraform-basics/#why-infrastructure-as-code-iac) — source: [/raw/architecture/assetcontainer/tm/tm1-iac-terraform-basics.md](/raw/architecture/assetcontainer/tm/tm1-iac-terraform-basics.md), section `#why-infrastructure-as-code-iac`

### 4. Secure Network Connectivity

Stage: `shield`

Establish an isolated Hub-and-Spoke network architecture. Centralized firewall rules and routing tables fully protect workloads from unauthorized access.

Asset: [/migration/assetcontainer/stackit/pfsense-firewall-connectivity-pattern/](/migration/assetcontainer/stackit/pfsense-firewall-connectivity-pattern/) — source: [/raw/migration/assetcontainer/stackit/pfsense-firewall-connectivity-pattern.md](/raw/migration/assetcontainer/stackit/pfsense-firewall-connectivity-pattern.md)

### 5. Automated Migration Execution

Stage: `gondola`

Execute the actual data and application migration onto the target infrastructure using a standardized, combined Terraform and Ansible runbook workflow.

Asset: [/migration/assetcontainer/stackit/rehost-automation-spring-boot-terraform-ansible/](/migration/assetcontainer/stackit/rehost-automation-spring-boot-terraform-ansible/) — source: [/raw/migration/assetcontainer/stackit/rehost-automation-spring-boot-terraform-ansible.md](/raw/migration/assetcontainer/stackit/rehost-automation-spring-boot-terraform-ansible.md)

### 6. Wave Delivery at Factory Scale

Stage: `chart`

Scale the automated migration pattern from a single application to governed waves: the end-to-end factory flow connects intake, run paths per migration strategy, and quality gates per wave.

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`

### 7. Post-Migration Optimization

Stage: `summit`

Following a successful cutover, platform teams utilize live monitoring via STACKIT Observability to detect over-provisioning and adjust capacities.

Asset: [/migration/assetcontainer/stackit/optimize-rehosted-spring-boot-observability-rightsizing/](/migration/assetcontainer/stackit/optimize-rehosted-spring-boot-observability-rightsizing/) — source: [/raw/migration/assetcontainer/stackit/optimize-rehosted-spring-boot-observability-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-rehosted-spring-boot-observability-rightsizing.md)