---
title: Operating Model Handover
description: Operating Model Handover transitions responsibilities, knowledge, and controls from migration delivery into durable run ownership.
sidebar:
  label: Overview
  order: 0
source_url: "https://framework.stackit.cloud/migration/migrate/operating-model-handover/overview/"
source_file: "docs/migration/migrate/operating-model-handover/overview.mdx"
---

## Understanding the Operating Model Handover module

Operating Model Handover moves the service from project delivery ownership to long-term operational accountability.
It activates the Target Operating Model in real service conditions.

The handover can start before migration completion when wave cadence and staffing model require parallel run.

## Delivery variants

- **DevOps model**: Product teams retain end-to-end responsibility and absorb run ownership gradually.
- **Classical operations model**: A dedicated operations team receives ownership through structured transition checkpoints.

## Handover flow

<Steps>

1. Confirm ownership model, accountability matrix, and acceptance criteria.
2. Transfer operational knowledge, including architecture decisions, runbooks, and known risks.
3. Validate supportability through shadow operations and controlled incident simulations.
4. Activate operating cadences for change, reliability, security, and capacity governance.
5. Approve handover completion and move to normal service ownership.

</Steps>

## Typical handover artifacts

- **Responsibility matrix**: RACI for operations, support, security, and platform responsibilities.
- **Operational playbooks**: Incident handling, maintenance windows, release and rollback procedures.
- **Service baseline evidence**: SLO values, monitoring coverage, escalation tree, and known constraints.
- **Governance calendar**: Review cycles for reliability, cost, risks, and backlog prioritization.

## Inputs and outputs

<CardGrid>
  <Card title="Primary inputs">
    Hypercare results, Target Operating Model decisions, support scope, and service-level objectives.
  </Card>
  <Card title="Handover outputs">
    Accepted ownership transfer, documented operational controls, and active governance routines.
  </Card>
  <Card title="Outcome">
    The service can be operated independently and at stable cost without migration project dependency.
  </Card>
</CardGrid>

## Boundary to adjacent modules

- Hypercare stabilization should be completed or controlled before final handover: [Hypercare](/migration/run/hypercare/overview/).
- Role boundaries for incidents and requests are formalized in [Support](/migration/run/support/overview/).
- Steady-state run continues in [Operate](/migration/run/operate/overview/).