---
title: Run
description: Run stabilizes migrated workloads on STACKIT, formalizes service operations, and secures long-term value through support and continuous improvement.
hero:
  tagline: Run turns migration outcomes into resilient, supportable, and continuously improved cloud operations on STACKIT.
  illustration:
    name: product
    position: left
sidebar:
  label: Overview
  order: 0
source_url: "https://framework.stackit.cloud/migration/run/"
source_file: "docs/migration/run/index.mdx"
---

## Understanding this phase

Run is the target state of the migration journey: workloads run on STACKIT with defined ownership,
stable operations, and measurable service quality.

The phase starts with post-cutover stabilization and extends into long-term cloud operations.
It is where migration outcomes are translated into durable operational performance.

## Position in the framework

Run is not just a follow-up activity. It is the strategic destination behind migration run.
For many programs, the practical objective is clear: maximize the share of workloads that run reliably
in a "Runs on STACKIT" operating state.

Run connects to Migrate through Hypercare and extends the Target Operating Model into real
day-to-day service operations.

## When Run starts and ends

<Steps>

1. Start with Hypercare directly after cutover, while migration and project teams are still reachable.
2. Close operational gaps, including missing monitoring, alerting, and runbook refinements.
3. Formalize handover to DevOps ownership or a dedicated operations team.
4. Establish support and service request responsibilities between customer and provider.
5. Continue in steady-state run with continuous optimization and regular operating model validation.

</Steps>

Operating Model Handover is anchored in Migrate and can overlap with migration waves before Run starts.

## Run phase module map

Run combines short-term stabilization and long-term service operations. The following model visualizes
the intended flow from migration handoff to stable day-2 operations.

<RunPhaseModuleModelSvg
  style={{ width: "100%", maxWidth: "1320px", height: "auto", display: "block" }}
/>

## Semantic map

The Run model uses four semantic streams to clarify ownership and purpose:

- **Stabilization stream**: Hypercare resolves post-cutover risks while delivery teams are still available.
- **Operations stream**: Operate secures reliability, security, observability, and controlled change in steady-state service run.
- **Service stream**: Support defines who handles incidents and which requests are provider-managed versus customer-managed.
- **Value stream**: Customer Success keeps adoption and outcomes aligned over time.

## Why this phase matters

<CardGrid>
  <Card title="Bridge from project to operations">
    Hypercare ensures unresolved migration topics are stabilized before they become recurring incidents.
  </Card>
  <Card title="Clear ownership and support model">
    Defined responsibilities for incidents and service requests reduce friction and escalation loops.
  </Card>
  <Card title="Operational resilience">
    Monitoring, observability, and runbook maturity improve reliability and recovery behavior.
  </Card>
  <Card title="Sustained value realization">
    Continuous service improvement keeps performance, cost, and user outcomes aligned with business goals.
  </Card>
</CardGrid>

## Core modules in this phase

- [Hypercare](/migration/run/hypercare/overview/): Stabilization bridge from Migrate to Run with fast feedback and controlled remediation.
- [Operate](/migration/run/operate/overview/): Steady-state cloud operations for reliability, security, and efficiency on STACKIT.
- [Support](/migration/run/support/overview/): Incident and service request model across customer and provider responsibilities.
- [Customer Success](/migration/run/customer-success/overview/): Value stream with a central contact model for adoption and outcome tracking.

## Typical outcomes

At the end of the initial Run establishment, teams should have:

- **Stabilized post-cutover service**: Critical migration defects are resolved or controlled with agreed actions.
- **Closed operational gaps**: Missing monitoring, alerting, and operational evidence paths are implemented.
- **Validated handover model**: DevOps or classical operations ownership is tested in real service scenarios.
- **Support model in production use**: Incident and request handling paths are active, documented, and measured.
- **Durable run governance**: Service performance, cost behavior, and improvement backlog are reviewed in regular cadences.