Controlled cutovers
Standardized runbooks and wave governance reduce outage and rollback risks.
Migrate
Migrate executes approved R-strategy transition paths in controlled waves and secures stable cutover outcomes.
Understanding This Phase
Section titled “Understanding This Phase”Migrate is the phase where migration happens for R-strategy paths that involve a technical move. It uses a factory-based delivery model to move workloads in controlled waves from source environments to STACKIT target environments.
The phase is runbook-driven and focuses on repeatability, cutover quality, and stable handover into operations.
R-strategy scope in this phase
Section titled “R-strategy scope in this phase”Migrate does not look the same for every R-strategy decision. The phase focus depends on the selected path per workload:
- Relocate, Rehost, Replatform: These are the core migration paths in this phase and use wave delivery with runbooks.
- Refactor: This is usually run as a dedicated modernization project stream with its own backlog and delivery setup.
- Repurchase: This follows a different transition pattern and is often best handled as a dedicated workstream or module.
- Retain, Retire: These paths do not require migration run in this phase and are treated as portfolio decisions.
When Migrate starts and ends
Section titled “When Migrate starts and ends”Migrate starts when the first migration waves are approved and their runbooks are ready.
- Start with validated wave scope, target architecture decisions, and operational cutover plans.
- Execute migration waves with governance controls, technical validation, and rollback readiness.
- End per workload group when migrations are completed and post-cutover stabilization is accepted.
At program level, the phase ends when all planned workloads are migrated, modernized, or formally retained/retired according to scope decisions.
Why this phase matters
Section titled “Why this phase matters”Migrate is where migration value is realized in production. Delivery quality in this phase directly impacts business continuity, user trust, and long-term operating efficiency.
Factory scale
Reusable migration patterns increase throughput while preserving quality.
Measured validation
Technical and functional checks confirm target-state stability after each wave.
Continuous improvement
Lessons learned are fed back into upcoming waves, optimize cycles, and modernization paths.
Core modules in this phase
Section titled “Core modules in this phase”- Migrate: Delivers workload relocation and cutover in controlled migration waves.
- Optimize: Improves workload sizing, performance, and cost after migration.
- Refactor: Enables deeper restructuring and cloud-native improvements where required.
- Repurchase: Covers SaaS replacement transition patterns that differ from technical migration waves.
- Operating Model Handover: Validates Target Operating Model ownership and transfer readiness before full Run operations.
Typical outcomes
Section titled “Typical outcomes”At the end of Migrate, the program should have:
- Successful wave run: Approved waves completed with documented cutover and validation evidence.
- Stabilized target workloads: Migrated systems running reliably on STACKIT with defined ownership.
- Optimization backlog and actions: Rightsizing and performance improvements prioritized and implemented.
- Modernization decisions: Refactor paths identified and initiated where business value is highest.
Boundary to run
Section titled “Boundary to run”Migrate includes immediate post-cutover stabilization and optimization loops. Long-term service operations, life cycle governance, and sustained value realization are anchored in the subsequent Run phase.