---
title: Runbook Blueprint
description: Defines what a migration runbook must contain, how to structure it for delivery, and how to validate readiness before wave runs.
sidebar:
  label: Runbook
  order: 7
source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/design/runbook/"
source_file: "docs/migration/design-and-mobilize/design/runbook.mdx"
---

## Why a Runbook Is a Design Output

In this framework, the runbook is produced in the Design phase. It captures the intended
run path, controls, rollback logic, and handover criteria per migration strategy.

Migration Factory Setup does not create the first runbook version. It operationally hardens,
standardizes, and validates Design runbook drafts for wave-scale delivery.

## Mandatory Runbook Chapters

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.

## Quality Criteria for a Good Runbook

<CardGrid>
  <Card title="Executable">Steps are concrete, ordered, and assignable to named roles.</Card>
  <Card title="Verifiable">
    Validation points define clear pass/fail criteria and required evidence.
  </Card>
  <Card title="Recoverable">
    Rollback path is complete, timed, and linked to explicit trigger conditions.
  </Card>
  <Card title="Handover-ready">Day-1 operations and ownership transfer are fully specified.</Card>
</CardGrid>

## Suggested Design-to-Factory Flow

<Steps>

1. Create strategy-specific runbook draft during Design.
2. Validate technical assumptions with platform, security, and operations stakeholders.
3. Add evidence checkpoints and rollback triggers.
4. Hand over to Migration Factory Setup for standardization and readiness checks.
5. Approve for wave execution after rehearsal or pilot validation.

</Steps>

## Concrete Example Asset

Use this concrete sample runbook asset for a classic Rehost case (Spring Boot to VM):

<ScfAssetLoader
  showFilter={false}
  showSearch={false}
  frameworkSlug="migration"
  filterByTag={["runnable-example", "rehost", "vm"]}
  filterTagMode="all"
/>

- **Pattern**: Lift-and-shift to target VM (no Kubernetes)
- **App type**: Typical enterprise Spring Boot service with PostgreSQL backend