---
title: Design and Mobilize
description: Design and Mobilize translates assessment inputs into target designs, governance, and run-ready migration planning for controlled delivery.
hero:
  tagline: Design and Mobilize turns assessment findings into executable target designs, governance, and wave-ready migration planning.
  illustration:
    name: product
    position: left
sidebar:
  label: Overview
  order: 0
source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/"
source_file: "docs/migration/design-and-mobilize/index.mdx"
---

## Understanding This Phase

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.

### When Design and Mobilize starts and ends

This phase starts after Assess confirms migration scope, readiness, and commercial direction.

<Steps>

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.

</Steps>

Design and Mobilize is complete when migration teams can begin wave run with stable
inputs, controls, and responsibilities.

### Why this phase matters

This phase turns strategy into delivery readiness and prevents uncontrolled migrations.

<CardGrid>
  <Card title="Architecture readiness">
    Target patterns and migration paths per workload are defined and validated.
  </Card>
  <Card title="Factory enablement">
    Roles, processes, tooling, and runbook governance are established before scale-up.
  </Card>
  <Card title="Security by design">
    Security and compliance requirements are integrated into design and planning from the start.
  </Card>
  <Card title="Execution confidence">
    Waves are sequenced with dependency awareness and operational feasibility.
  </Card>
</CardGrid>

## Core modules in this phase

- [Discovery](/migration/design-and-mobilize/discovery/overview/): Creates the application-level baseline and dependency transparency.
- [Migration Plan](/migration/design-and-mobilize/migration-plan/overview/): Translates strategy into wave-based delivery planning.
- [Design](/migration/design-and-mobilize/design/overview/): Defines migration approach and target patterns per application.
- [Business Case](/migration/design-and-mobilize/business-case/overview/): Consolidates value, effort, and investment logic per scope.
- [Migration Factory Setup](/migration/design-and-mobilize/migration-factory-setup/overview/): Establishes the delivery factory model and operating mechanics.
- [Enablement](/migration/design-and-mobilize/enablement/overview/): Builds governance, learning, and reference capabilities for consistent delivery.
- [Landing Zones](/migration/design-and-mobilize/landing-zones/overview/): Implements the secure and scalable platform foundation.
- [Target Operating Model](/migration/design-and-mobilize/operating-model/overview/): Defines the governance, accountabilities, and capabilities for stable cloud operations.
- [Security and Compliance](/migration/design-and-mobilize/security-and-compliance/overview/): Embeds control requirements into architecture and migration run.

## Typical outcomes

At the end of Design and Mobilize, the program should have:

- **Approved target designs**: Migration strategy and target architecture decisions per workload class.
- **Wave-ready migration plan**: Sequenced and dependency-aware wave plan with prioritized backlog.
- **Factory operating setup**: Governance cadence, runbook standards, and delivery ownership in place.
- **Platform and control baseline**: Landing zone and security/compliance controls ready for migration.

## Transition to Migrate

Design and Mobilize can overlap with early migration waves. As soon as the first waves and
runbooks are validated, Migrate begins and delivery continues iteratively while planning is
refined for upcoming waves.