Skip to content
Beta

Getting Started with the Cloud Framework

Last updated on

Stackit LogoStackit Logo
STACKIT

Getting Started with the Cloud Framework

Guided first tour of the STACKIT Cloud Framework site: read the mountain map, explore the frameworks, find assets, follow guided trails, and present them.

PLAN

Welcome: One Map for Your Cloud Journey

The STACKIT Cloud Framework is your map for cloud journeys. Every framework is a mountain, contributors live in the base village, assets are the equipment in the backpack and trails are the marked routes to the summit.

The Cloud Framework mountain map
The Cloud Framework mountain map
BASE

The Six Frameworks: Pick Your Mountain

Six mountains: Advisory for strategy, Adoption for cloud journeys, Architecture for landing zones, Data & AI for workloads, ISV for software vendors and Migration for moving to STACKIT. All six share one structure.

The mountain map with the six frameworks highlighted
The mountain map with the six frameworks highlighted
Example of a Built-Out Framework: Migration One mature framework as the example of what every mountain grows toward.

Migration is the most developed mountain today. Its map shows the whole ascent at a glance. This is the depth every framework grows toward.

Structured overview of the STACKIT Cloud Migration Framework across the phases Assess, Design and Mobilize, Migrate, and Run with their key modules.

In 1 trail
STACKIT Cloud Migration Framework Journey across the four phases Assess, Design and Mobilize, Migrate, and Run with their key modules. Assess PHASE 1 Assess Design & mobilize PHASE 2 Design & mobilize Migrate PHASE 3 Migrate Run PHASE 4 Run PLANNING Discovery Discovery Map apps and dependencies. Design Design Define target patterns. Migration plan Migration plan Sequence waves for delivery. Rapid discovery Rapid discovery Inventory workloads to create an early scope and cost baseline. TCO report TCO report Model migration economics to support investment and planning decisions. Readiness assessment Readiness assessment Assess technology and organization gaps before detailed design starts. Deepdive workshop Deepdive workshop Explore STACKIT services and platform options for target design. Briefings & workshops Briefings & workshops Align stakeholders on goals, scope, and migration expectations. Business case Business case Compare value, effort, and investment per application. Enablement ENABLEMENT Center of Excellence Trainings & Learning Paths Documentation & Reference Landing zone Landing zone Establish the secure platform base for migrated workloads. Security & compliance Security & compliance Define security and compliance controls for migration and operations. Target operating model Target operating model Define roles, processes, and ownership for target operations. Migration factory setup Migration factory setup Prepare teams, tools, and runbooks for scalable migration execution. Migrate MIGRATE Relocate Relocate Rehost Rehost Replatform Replatform Optimize Optimize Improve sizing, performance, and cost after cutover. Repurchase Repurchase Evaluate SaaS options when replacement delivers better value. Refactor Refactor Restructure strategic workloads for cloud- native scalability and agility. Operating model handover Operating model handover TOM validation and ownership transfer Hypercare Hypercare Post-cutover stabilization bridge. Operate Operate Steady-state cloud operations. Support Support Manage incidents and service requests across support responsibilities. Customer Success Customer Success Track adoption, outcomes, and value realization with stakeholders.
The Migration Framework overview map
STACKIT LogoSTACKIT Logo
Migrate STACKIT · Cloud Framework Open page ↗

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.

  1. Start with validated wave scope, target architecture decisions, and operational cutover plans.
  2. Execute migration waves with governance controls, technical validation, and rollback readiness.
  3. 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.

Controlled cutovers

Standardized runbooks and wave governance reduce outage and rollback risks.

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.

STEP

Assets: The Equipment in the Backpack

Assets are the equipment: blueprints, guides, runbooks, workshops and more, each shown as a card. Search, filter and sort to find your gear. Badges show what STACKIT recommends and what is new this week.

The mountain map with Assets highlighted
The mountain map with Assets highlighted
How to Read an Asset Card Every asset is shown as a card. Here is how to read one before you even open it.

Every asset is a card: contributor and category at the top, tags for search and a badge when STACKIT recommends it. The lock line shows the license: Open Source is free to use, Managed is run by the contributor.

STACKIT LogoSTACKIT Logo
Blueprint

STACKIT Landing Zone Accelerator

STACKIT

Migration design-and-mobilize landing-zone opentofu terraform +1
Open Source In 2 trails

STACKIT base asset for building a platform landing zone with reusable OpenTofu/Terraform modules, enterprise baseline patterns, and central Kubernetes.
STACKIT LogoSTACKIT Logo
Owner

STACKIT

The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from German and Austrian data centers with full digital independence.
LIFT

Trails: Guided Journeys up the Mountain

Trails chain assets and pages into a guided journey, stage by stage from PLAN to GOAL. Expand a step with Show more or take the whole trail to your assistant with Copy for AI. You are on one right now.

The mountain map with Trails highlighted
The mountain map with Trails highlighted
How to Read a Trail Card A trail card previews the whole journey before you commit.

A trail card previews the whole route: who built it, which mountain it climbs and the first steps. The card on the right is this very trail. Open it or press Present.

Stackit LogoStackit Logo
STACKIT

Getting Started with the Cloud Framework

Guided first tour of the STACKIT Cloud Framework site: read the mountain map, explore the frameworks, find assets, follow guided trails, and present them.

Advisory getting-started site-tour
Trail Steps
  • Welcome: One Map for Your Cloud Journey
  • The Six Frameworks: Pick Your Mountain
  • Example of a Built-Out Framework: Migration
  • Inside a Framework: The Core Modules
+ 8 more steps
OPS

Who Builds This: Contributors and Updates

STACKIT teams, official partners and other contributors write the content. They keep their own profiles, assets and trails and can suggest updates to any content. Cards show who contributed and when.

The mountain map with Contributors highlighted
The mountain map with Contributors highlighted
AUTO

Present Any Trail as a Slide Deck

Every trail doubles as a slide deck. Click the presentation icon on an open trail, pick a prepared view and start. Speaker notes and a presenter window turn it into a talk or a workshop. No export needed.

The presentation icon in the top-right of an open trail, which turns the trail into a slide deckThe presentation icon in the top-right of an open trail, which turns the trail into a slide deck
The presentation icon in the top-right of an open trail, which turns the trail into a slide deck
On a Phone, With a Clicker The same deck runs on a projector, with a presentation clicker and on a phone.

Turn the slides with a clicker, the mouse wheel or a click on the slide edge. The bar at the bottom jumps to any step. On a phone, tap or swipe between the two columns of a slide.

A trail slide on a phone: one column large, the other as a small preview to tapA trail slide on a phone: one column large, the other as a small preview to tap
A trail slide on a phone: one column large, the other as a small preview to tap
GOAL

Start Your Own Ascent

Three ways to begin: open the framework that fits your journey, browse the Assets page or follow a guided trail. The mountains are ready. Have a good ascent.

The Cloud Framework mountain map: your whole territory
The Cloud Framework mountain map: your whole territory
Trail historyActive 6 of the last 12 weeksTMUpdatedNo updates · 1 bar = 1 week i
Maintainers
TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 12 of the last 12 weeks · 168 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172Contributed in STACKIT
Show full history (9 more)