Inventory
Comprehensive capture of servers, virtual machines, databases, middleware, and applications.
Last updated on
Plan VMware Relocate to STACKIT through discovery, target design, landing-zone readiness, migration waves, controlled cutover, validation, and optimization.
Start in Assess with a rapid inventory of VMware compute, storage, operating systems, and first capacity assumptions. Keep uncertainty visible for deeper Discovery instead of treating provisioned capacity as target sizing.
The following diagram shows why Rapid Discovery is performed: raw source data is processed by tooling into a decision-ready baseline that supports early price indication and initial target sizing.
Enrich the estate baseline with dependencies, application criticality, operating constraints, and representative CPU, memory, storage, and network measurements needed for Relocate design and wave grouping.
Inventory
Comprehensive capture of servers, virtual machines, databases, middleware, and applications.
Dependency analysis
Mapping of communication paths and runtime dependencies between systems and applications.
Resource utilization
Analysis of actual CPU, memory, storage, and I/O behavior over a representative period.
Operational context
Collection of backup, patching, SLA, compliance, and operational constraints.
Application owner input
Structured questionnaires and interviews to validate assumptions and close data gaps.
Record the result for every VM and preserve the evidence used for the decision.
Approve a VM for replication only when every blocker has an owner and resolution date. Conditional items must have an executable remediation step in the wave runbook; observations without impact can remain in the evidence record.
Confirm that the workload should remain VM-based and that moving its runtime placement with minimal redesign fits better than a Rehost rebuild or a platform change.
Relocate moves workloads with minimal architectural change, typically by transferring virtualization estates to a STACKIT-compatible target setup. The goal is fast transition with controlled risk, not immediate cloud-native modernization.
In practical terms, Relocate keeps the existing VM operating pattern largely intact. The main change is the runtime location and surrounding platform controls, not the workload runtime model itself.
In Relocate, the data path is often implicit because the full VM (including attached storage) is moved. Even so, large data footprints still require explicit design decisions:
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Create one version-controlled mapping row per VM and volume.
Approve the mapping only when the target profile, expected cost, quota, tool mapping, and acceptance thresholds are all known. Feed the exact mapping into the Coriolis or Acura test migration rather than choosing target resources during cutover.
Establish the governed cloud foundation before migration waves depend on it. Keep shared Platform Landing Zone capabilities separate from workload-specific Application Landing Zones, and derive both from enterprise controls and Discovery evidence.
A landing zone is the structured cloud foundation that defines how your organization operates on STACKIT from day 1. It combines governance, identity, security, network design, cost controls, and automation into one coherent baseline.
Without this foundation, migration waves typically stall due to missing approvals, inconsistent controls, and repeated platform decisions.
The following visual summarizes the core components that should be addressed for a reliable platform baseline.
Start the landing-zone stream as early as possible, in parallel with discovery.
The practical model is a dual track: establish the platform baseline early, then refine application landing zone templates as discovery insights mature.
Platform Landing Zone
Company-wide foundation for governance, identity, security, networking, cost controls, and automation.
Open Platform Landing ZoneApplication Landing Zone
Workload-specific implementation patterns derived from the platform baseline and discovery findings.
Open Application Landing ZoneThis asset provides a reusable foundation for implementing a STACKIT platform landing zone. It is designed for enterprise environments that need a structured baseline for governance, security, networking, cost controls, and automation.
Repository:
The Platform Landing Zone supplies organization-wide governance, connectivity, identity, audit, and automation capabilities. The STACKIT Landing Zone Accelerator then creates one Application Landing Zone project for the workload and environment. Security Groups form an explicit manual approval gate before migration tooling or VMs enter that project.
The boundary is deliberate:
landing_zones map and enable corporate networking, Secrets Manager, and Observability as required.Do not hand the project to a migration tool before steps 1 through 5 pass. The tool consumes the Landing Zone; it does not define or replace it.
Provide the same approved Landing Zone contract to either tool while keeping their implementations separate.
Group VMs by verified dependencies and technical constraints, begin with a representative low-risk pilot, and define ordered runbooks, maintenance windows, cutover gates, and rollback boundaries.
Wave planning
Group applications into logical migration waves based on dependency constraints, business criticality, and technical complexity.
Migration runbooks
Create detailed, step-by-step runbooks per wave or application covering preparation, delivery, cutover, rollback, and post-migration validation.
Resource planning
Define required teams, skills, tools, and expert allocation per wave, including enablement and training planning.
Delivery governance
Establish clear governance processes, ownership, communication cadence, and cutover controls for wave delivery.
Do not start replication until all entry criteria have passed:
Begin Migrate only with approved source and target states. Preserve topology assumptions, synchronize state, control traffic cutover, and require objective continuity and telemetry evidence.
Choose one approved migration tool for the complete wave. Keep its endpoint, mapping, replication, test-migration, final-sync, and cutover sequence together through completion.
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Select this complete path when Cloudbase Coriolis is the approved migration tool.
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Select this complete path when Hystax Acura is the approved migration tool.
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Start validation as soon as target instances are reachable. Record timestamps because the remaining rollback window is a technical constraint.
Rollback is safe only while data ownership remains clear. If the target has accepted writes, stop target processing and execute the approved reverse synchronization or reconciliation method before the source is restarted. Never power on both copies with production connectivity unless the application design explicitly supports concurrent writers.
The wave is technically complete when:
After accepted cutover, collect representative STACKIT runtime evidence and turn performance, stability, and cost findings into controlled infrastructure changes with rollback checkpoints.
Optimization decisions should be based on runtime evidence, not assumptions. For practical implementation, combine workload telemetry, alerting, and controlled infrastructure changes.
STACKIT
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Classify the finding before changing capacity:
Change one dominant dimension at a time where practical. This keeps the result attributable and makes rollback decisions defensible.