Skip to content
Beta

Relocate to STACKIT: VMware Migration Overview

Last updated on

Stackit LogoStackit Logo
STACKIT

Relocate to STACKIT: VMware Migration Overview

Plan VMware Relocate to STACKIT through discovery, target design, landing-zone readiness, migration waves, controlled cutover, validation, and optimization.

PLAN

Rapid Discovery

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.

AssessRapid discoveryOverview In 4 trails

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.

Swipe sideways to see the whole diagram
Rapid discovery process Input data is processed through rapid discovery tooling to produce decision-ready outputs for early migration choices. Input dataCMDB & inventory exportsAsset lists, hosts, base platform factsHypervisor & cloud reportsUsage, footprint, and utilization signalsPlatform listsKubernetes, database, and OS baselinesRapid discovery toolingIngest & normalize datasetsStandardize source records and schemaClassify & aggregate assetsConsolidate by technology and quantityApply assumptionsConfidence levels and growth factorsOutput informationConsolidated asset baselineFact base for scope and planningInitial STACKIT sizingFirst capacity assumptionsPrice indication & TCO corridorEarly cost orientation for decisions
STEP

Discovery

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.

Design and mobilizeDiscoveryOverview In 4 trails
Discovery source-to-decision flow Discovery separates technical and human-driven inputs, runs technical-first and human-enriched analyses, and hands over both insight streams to follow-on modules. Discovery inputsTechnical and automated discoveryInfrastructure inventoryCMDB, VM, database, middleware, storageRuntime and utilization dataCPU, memory, I/O, network and seasonalityIntegration and flow signalsNetwork paths, APIs, identity, data movementAssessment-driven human inputSecurity and compliance contextData classes, controls, audit requirementsOwner and business inputCriticality, release windows, lifecycle plansDiscovery analysis toolingTechnical-first analysesNormalize and correlateUnify records and technical identitiesDependency mappingInfer communication and couplingUtilization and sizing analysisEstimate baseline demand corridorsPreliminary segmentationCluster by stack and environmentHuman-driven analyses (application owner input)Criticality and risk calibrationValidate business impact and constraintsWave feasibility and sequencingReconcile dependencies with release windowsAssumption and gap registerTrack open points and confidenceHandover outputsTool-derived outputsDesignTarget architecture options and sizing factsLanding zonePlatform guardrails and account structure needsMigration planWave backlog, sequencing, and cutover windowsAssessment-validated outputsSecurity and complianceControl needs, data classes, remediation pointsOperating modelRole model, ownership boundaries, process impactBusiness caseValue/risk profile and modernization priorities
Discovery analysis flow combining technical evidence and application-owner input into migration decisions

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.

STACKIT LogoSTACKIT Logo
VMware Relocate Source Readiness STACKIT · Runbook Open asset ↗

Record the result for every VM and preserve the evidence used for the decision.

  • Guest compatibility: Pass with a supported operating system, boot mode, disk layout, and conversion path. Block on an unsupported device, encryption method, architecture, or boot path.
  • Source integrity: Pass with a healthy VM, tested recovery point, and safe snapshot state. Block on a consolidation error, failed backup, or insufficient datastore capacity.
  • Performance baseline: Pass with representative CPU, memory, storage, and growth measurements. Block when only provisioned capacity or incomplete peak-window data is available.
  • Access: Pass with tested least-privilege endpoint credentials and certificate trust. Block on missing API permissions or unmanaged shared credentials.
  • Transfer path: Pass with measured capacity and validated routing, ports, DNS, NTP, and MTU. Block on firewall gaps, unstable links, or a copy duration outside the wave schedule.
  • Cutover inputs: Pass with target mappings, validation tests, a rollback trigger, and source retention. Block on an undefined traffic switch or rollback path that cannot be tested.

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.

LIFT

Design

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.

Design and mobilizeDesignRelocate In 1 trail
R-strategy migration method Decision flow from discovery to production with the seven R-strategies: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire. R-strategy migration methodFrom discovery and path selection through the seven R-strategies to validation, transition, and production.DiscoveryDiscoveryAssess / prioritizeAssess / prioritizeDetermine migration pathDetermine migration pathValidationValidationTransitionTransitionProductionProductionRelocateRelocate(move VM)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployValidation & handoverRehostingRehosting(move application)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployReplatformingReplatforming(lift and reshape)Define Landing ZoneDefine Landing ZoneMap Target PlatformMap Target PlatformAdapt Platform StackAdapt Platform StackRepurchasingRepurchasing(replace, drop and shop)Purchase COTS/SaaS and licensingPurchase COTS/SaaS and licensingMigrate business processMigrate business processRefactoringRefactoring(re-architecting applications)Redesign application/ infrastructure architectureRedesign application/ infrastructure architectureApp code developmentApp code developmentFull ALM/SDLCFull ALM/SDLCIntegrationIntegrationRetain/moveRetain/movekeep for now or move laterRetire/decommissionRetire/decommissionLanding zone foundationLanding zone foundationShared platform base for all paths
R-strategy method with seven migration paths and Relocate as the VM-estate movement path

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:

  • Network connectivity capacity: Validate end-to-end throughput, latency, and transfer path stability for the planned migration window.
  • Storage class fit: Align source and target storage classes with required IOPS/throughput characteristics before cutover.
  • Pre-seed strategy: Transfer baseline volumes before cutover where possible.
  • Delta synchronization: Minimize final downtime window by only syncing latest changes during cutover.
  • Integrity checks: Define checksum and sample-read validation for migrated disks.
  • Rollback checkpoints: Keep source snapshot retention until target acceptance is confirmed.
Secured VMware-to-STACKIT transfer path
Secured VMware-to-STACKIT transfer path
OPS

Map Target Capacity

Create one version-controlled mapping row per VM and volume.

  • Source VM and workload: Stable inventory identifier and application mapping.
  • Target region and placement: Region, availability zone or Metro requirement, and quota result.
  • Machine type: Exact type, CPU and RAM requirement, governing dimension, headroom, and overprovisioning decision.
  • Root volume: Capacity, performance class, boot assumptions, and recovery assumptions.
  • Data volumes: Source-to-target disk mapping, capacity, performance class, and consistency group.
  • Network: Target network, addresses, security groups, DNS, and bandwidth expectation.
  • Validation thresholds: CPU, memory, latency, IOPS, throughput, application SLO, and observation window.
  • Adjustment options: Approved larger and smaller type, storage alternative, change method, and rollback condition.

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.

BASE

Landing Zone

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.

Design and mobilizeLanding zonesOverview In 6 trails
Platform and application landing zone layers
Platform and application landing zone layers

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.

Landing zone core components Six building blocks of a secure landing zone. Landing zone core componentsThe six building blocks of a secure platform foundation on STACKIT.Account GovernanceAccount GovernanceHow do I structure my projects?Identity & Access ManagementIdentity & Access ManagementWho can do what on the platform?Security & ComplianceSecurity & ComplianceHow do I monitor and protect?Network ArchitectureNetwork ArchitectureHow are components securely connected?Cost Management and ControlCost Management and ControlHow do I keep spending in control?Automation (IaC)Automation (IaC)How is everything delivered and managed?
  • Control and risk reduction: Enforce security and compliance controls consistently across teams.
  • Scalable delivery baseline: Enable repeatable provisioning patterns for multiple migration waves.
  • Clear responsibilities: Define ownership boundaries for platform, security, and application teams.
  • Faster migration throughput: Avoid redesigning core controls for each application move.

Start the landing-zone stream as early as possible, in parallel with discovery.

  • Too late: Productive migrations are blocked because mandatory controls are not yet available.
  • Too early without discovery feedback: Application constraints are missed and later cause rework.

The practical model is a dual track: establish the platform baseline early, then refine application landing zone templates as discovery insights mature.

Two layers: Platform and Application Landing Zones

Section titled “Two layers: Platform and Application Landing Zones”

Platform Landing Zone

Company-wide foundation for governance, identity, security, networking, cost controls, and automation.

Open Platform Landing Zone

Application Landing Zone

Workload-specific implementation patterns derived from the platform baseline and discovery findings.

Open Application Landing Zone
STACKIT LogoSTACKIT Logo
STACKIT Landing Zone Accelerator STACKIT · Blueprint Open asset ↗

This 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:

STACKIT Landing Zone Accelerator architecture from bootstrap through platform capabilities to application landing zones
STACKIT Landing Zone Accelerator architecture from bootstrap through platform capabilities to application landing zones
STACKIT LogoSTACKIT Logo
VM Application Landing Zone for Relocate STACKIT · Blueprint Open asset ↗

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.

Platform Landing ZoneVM Application Landing ZoneTool and workload contentGovernance and IAMShared connectivity and DNSAudit and automation baselineAccelerator baselineManual gateCoriolis or Hystax AcuraMigrated VMs and volumesGuest metrics, logs, and backupSTACKIT project and RBACRouted network and DNS zoneSecrets Manager and automation identityObject Storage and state bucketObservability endpointSecurity GroupsRule review and approval baseline readyinherit shared route policyinherit guardrailsapproved ingress and egress

The boundary is deliberate:

  • Landing Zone responsibility: Project, roles, routed network, DNS zone, Secrets Manager, Object Storage, automation identity, optional Observability instance, labels, and shared routing.
  • Manual security responsibility: Security Groups and their workload-specific ingress and egress rules are reviewed and created before tool deployment.
  • Workload responsibility: Migration appliances, migrated servers and volumes, guest configuration, application dependencies, backup policies, and telemetry agents.
STACKIT LogoSTACKIT Logo
VM Application Landing Zone for Relocate STACKIT · Blueprint Open asset ↗

VM Application Landing Zone build sequence

Section titled “VM Application Landing Zone build sequence”
  1. Confirm the Platform Landing Zone prerequisites: governance folders, IAM model, Network Area, shared DNS, routing and firewall policy, audit path, and automation ownership.
  2. Derive one VM Application Landing Zone specification from Discovery: environment, project owner, dependency boundaries, address demand, DNS names, data classification, availability, recovery objectives, and telemetry requirements.
  3. Add the workload environment to the Accelerator landing_zones map and enable corporate networking, Secrets Manager, and Observability as required.
  4. Apply the Accelerator and verify the project, role assignments, routed network, route policy, DNS zone, secrets boundary, state storage, automation identity, and Observability outputs.
  5. Create and approve the Security Groups manually from the dependency matrix and the selected migration tool’s control and transfer paths.
  6. Hand the approved project ID, network, DNS, Secrets Manager, Observability endpoints, Security Groups, quotas, and target mappings to either the Coriolis or Acura runbook.
  7. Let the selected tool deploy only its required appliance, worker, server, volume, image, and migration content into the Application Landing Zone.
  8. Connect VM guest metrics and logs to the provisioned Observability endpoint, apply backup and recovery policies, and validate all controls in an isolated test migration.

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.

STACKIT LogoSTACKIT Logo
VM Application Landing Zone for Relocate STACKIT · Blueprint Open asset ↗

Provide the same approved Landing Zone contract to either tool while keeping their implementations separate.

  • Common inputs: STACKIT project and region, target network and addresses, Security Groups, DNS, machine and volume mappings, Secrets Manager usage, Observability endpoints, quotas, and rollback boundaries.
  • Coriolis content: Coriolis appliance components, STACKIT endpoint, minion pools, Transfers, Deployments, and the resulting VM and volume resources.
  • Hystax Acura content: Acura control components, replication integration, cloud-site settings, orchestration plans, target snapshots or volumes, and the resulting VM resources.
  • Common completion evidence: Security-rule test, dependency test, guest telemetry, backup and restore evidence, application acceptance, and removal plan for temporary migration access.
OPS

Migration Plan

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.

Design and mobilizeMigration planOverview In 2 trails
Migration Plan model connecting portfolio evidence, wave governance, runbooks, and controlled execution
Migration Plan model connecting portfolio evidence, wave governance, runbooks, and controlled execution

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.

STACKIT LogoSTACKIT Logo
VMware Relocate Wave Execution STACKIT · Runbook Open asset ↗

Do not start replication until all entry criteria have passed:

  • Wave scope and dependency groups are frozen and every VM has a stable source identifier.
  • VMware source readiness, tool-specific prerequisites, and recovery points are verified.
  • Target machine types, volumes, performance classes, networks, addresses, security groups, and placement are approved and available within quota.
  • Application-level consistency, test cases, maintenance window, expected downtime, and maximum cutover duration are documented.
  • Source freeze, traffic switch, monitoring activation, and rollback actions have named technical owners.
  • The source retention period and the authority to delete source VMs are defined before cutover.
LIVE

Migrate

Begin Migrate only with approved source and target states. Preserve topology assumptions, synchronize state, control traffic cutover, and require objective continuity and telemetry evidence.

MigrateMigrateOverview In 4 trails
End-to-End Migration Wave Flow Four sequential stages lead from wave approval through preparation and cutover to stabilization and handover. Every wave follows the same controlled factory flow. Secure scope and baseline, execute migration, prove acceptance, and hand over safely to operations. 1 APPROVE Scope and baseline Window, rollback, and ownership Freeze versions and dependencies 2 PREPARE Readiness and R-path Validate source and target Run playbook by archetype 3 CUT OVER Cutover and acceptance Route traffic to STACKIT safely Validate tech, function, operations 4 STABILIZE Learn and hand over Resolve findings in short loops Hand over to Optimize and Operate Traceable wave completion: accepted, stabilized, and fully handed over
Controlled migration wave flow from readiness through synchronization, cutover, validation, and handover
  1. Recreate workload placement in STACKIT with equivalent topology assumptions.
  2. Migrate data and state with consistency checks.
  3. Cut over traffic with rollback guardrails.
  4. Validate business continuity and operational telemetry.
AUTO

Select and Execute One Tool Path

Choose one approved migration tool for the complete wave. Keep its endpoint, mapping, replication, test-migration, final-sync, and cutover sequence together through completion.

SAFE

Validate or Roll Back

Start validation as soon as target instances are reachable. Record timestamps because the remaining rollback window is a technical constraint.

  1. Validate VM state: boot, console, disks, file systems, mounts, network interfaces, routes, DNS, NTP, certificates, Server Agent, and required operating-system services.
  2. Validate data state: expected recovery point, file or database consistency, checksums or record counts, and absence of unintended writes on the source.
  3. Start dependencies and applications in order, then run health checks, synthetic transactions, integrations, scheduled jobs, and mandatory business tests.
  4. Confirm logs, metrics, alerts, backups, administrative access, and security controls in the target environment.
  5. Compare CPU, memory, disk latency, IOPS, throughput, network behavior, application latency, and error rates with the approved acceptance thresholds.
  6. At the decision deadline, either accept the target or execute the documented rollback. Do not drift into an unbounded troubleshooting window.

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:

  • mandatory technical and functional checks pass and the target is the declared system of record;
  • monitoring and backup evidence is available from STACKIT;
  • defects, temporary exceptions, and follow-up actions have owners and deadlines;
  • actual replication, freeze, cutover, and validation durations are recorded for the next wave;
  • source VMs remain powered off and access-controlled for the approved retention period;
  • source deletion occurs only after retention expiry, recovery confirmation, and explicit approval;
  • the initial target sizing is handed to Optimize with its measurements and acceptance thresholds.
OPS

Optimize

After accepted cutover, collect representative STACKIT runtime evidence and turn performance, stability, and cost findings into controlled infrastructure changes with rollback checkpoints.

MigrateOptimizeOverview In 7 trails
Evidence-based VM optimization loop
Evidence-based VM optimization loop

Optimization decisions should be based on runtime evidence, not assumptions. For practical implementation, combine workload telemetry, alerting, and controlled infrastructure changes.

  • Managed observability baseline: Use STACKIT Observability to collect metrics, logs, and traces with Grafana, Prometheus, Thanos, Loki, and Tempo.
  • Detection logic: Define explicit thresholds and observation windows for low utilization and overload conditions.
  • Run path: Apply rightsizing through IaC changes (for example VM flavor changes) with rollback checkpoints.
  • Validation loop: Re-measure SLO, error rates, and run-cost after each tuning increment.
GOAL

Rightsize the Relocated VMs

Classify the finding before changing capacity:

  • No change: The current profile meets performance, resilience, and cost expectations.
  • Compute downsize: CPU and memory retain approved headroom across representative demand.
  • Compute upsize or family change: CPU, memory, or CPU-to-memory ratio constrains the workload.
  • Move to a non-overprovisioned type: Sustained CPU demand, latency sensitivity, or steal time requires more predictable CPU access.
  • Increase volume capacity: Forecast usable capacity reaches the approved threshold.
  • Change storage performance: IOPS or throughput limits, latency, or I/O wait indicate a class mismatch after application and guest causes are excluded.
  • Investigate first: The limiting signal is caused by configuration, application behavior, dependency latency, network loss, or insufficient evidence rather than resource capacity.

Change one dominant dimension at a time where practical. This keeps the result attributable and makes rollback decisions defensible.

Trail historyActive 3 of the last 12 weeksLWUpdatedNo updates · 1 bar = 1 week i
Maintainer
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172Contributed in STACKIT
Show full history (6 more)