---
title: Refactor
description: Refactor describes high-level transition patterns outside the migration factory and prepares strategic workloads for cloud-native target architectures.
sidebar:
  label: Overview
  order: 0
source_url: "https://framework.stackit.cloud/migration/migrate/refactor/overview/"
source_file: "docs/migration/migrate/refactor/overview.mdx"
---

## Understanding the Refactor module

Refactor covers modernization-oriented transitions at high level.
Unlike Relocate, Rehost, and Replatform wave delivery, modernization is typically managed as a dedicated project stream.

This module intentionally focuses on shared cross-scenario principles, not workload-specific implementation blueprints.

## Why Refactor is handled as a distinct module

- **Different delivery model**: Refactor work follows product and architecture backlogs, not factory wave runbooks.
- **Longer timeline**: Modernization often spans multiple releases and capability increments.
- **Higher design impact**: Target architecture, data model, and integration contracts may change substantially.

## Shared modernization life cycle

<Steps>

1. Define modernization intent, business outcomes, and architecture constraints.
2. Select candidate workloads using value, risk, and complexity criteria.
3. Establish target-state architecture and migration increments.
4. Execute iterative delivery with validation gates and release governance.
5. Transition stabilized capabilities into standard run operations.

</Steps>

## Typical outputs

<CardGrid>
  <Card title="Target architecture decisions">
    Documented decisions for service decomposition, data ownership, and integration boundaries.
  </Card>
  <Card title="Modernization roadmap">
    Prioritized sequence of refactor increments aligned to business milestones.
  </Card>
  <Card title="Operating model alignment">
    Updated responsibilities, reliability controls, and release governance for the new architecture.
  </Card>
</CardGrid>

## Boundary to migrate and optimize

- Refactor is not a substitute for wave delivery in [Migrate](/migration/migrate/migrate/overview/).
- Optimize remains the post-cutover improvement loop for migrated workloads: [Optimize](/migration/migrate/optimize/overview/).

Detailed architecture guidance is part of the Architecture Framework: [/architecture/](/architecture/).