---
title: "StackToIT – Migration Tool for STACKIT, Deterministic Engine"
url: https://stacktoit.com/en/
---

StackToIT · Deterministic Migration Engine

# Cloud migration to STACKIT.

StackToIT reads your AWS, Azure, Google Cloud, VMware, Huawei Cloud, Alibaba Cloud or Oracle Cloud estate and delivers what a STACKIT migration needs: service mapping, target architecture, Terraform drafts and a migration plan.

[Get Your Migration Assessment](https://stacktoit.com/en/services/migration-assessment/)[Explore Real Results](https://stacktoit.com/examples/)

## Assessment summary

AWS Retail Store · AWS → STACKIT Migration Assessment

- Terraform resources analyzed

  282

- migration units identified

  44

- considered units drafted

  34of 52

### Target architecture on STACKIT

Sample of the service mapping in this run

| AWS source  | STACKIT target           |
| ----------- | ------------------------ |
| Amazon ECS  | Kubernetes Engine (SKE)  |
| Aurora      | PostgreSQL Flex          |
| ElastiCache | Key Value Store (Valkey) |
| DynamoDB    | MongoDB Flex             |

[View Case Study](https://stacktoit.com/examples/aws-retail-store/)

## Technical deliverables, not slideware.

One run delivers the complete migration package your architects work from: analysis, target architecture, Terraform, plan, data migration and decisions, as files you review, version and keep. StackToIT plans not only the target infrastructure but also the path of your data to it.

- ### Migration Assessment

  Resource classifications, service mappings and infrastructure analysis.

  [Open in the Retail Store example: index.html](https://stacktoit.com/examples/aws-retail-store/report/)

- ### Target Architecture

  Proposed STACKIT architecture, dependencies and changes from the existing environment.

  [Open in the Retail Store example: architecture/target.svg](https://stacktoit.com/examples/aws-retail-store/#architecture)

- ### Terraform Generation

  STACKIT Terraform artifacts and target configuration files, ready for architect review.

  [Open in the Retail Store example: terraform/](https://stacktoit.com/examples/aws-retail-store/#terraform)

- ### Migration Planning

  Work packages, sequencing, prerequisites, data movement and verification steps.

  [Open in the Retail Store example: migration/roadmap.md](https://stacktoit.com/examples/aws-retail-store/files/migration/roadmap.md)

- ### Decision Management

  Architecture questions, required inputs and outstanding technical decisions.

  [Open in the Retail Store example: executive/decisions.md](https://stacktoit.com/examples/aws-retail-store/files/executive/decisions.md)

- ### Data Migration Planning

  The path of your data, store by store: stateful units, candidate methods, prerequisites, checks, cutover and rollback decisions, with every unknown named instead of assumed.

  [Open in the Retail Store example: migration/data-movement.md](https://stacktoit.com/examples/aws-retail-store/files/migration/data-movement.md)

- ### Engineering Outputs

  Detailed technical findings, evidence and supporting migration documents.

  [Open in the Retail Store example: engineering/architect-report.md](https://stacktoit.com/examples/aws-retail-store/report/engineering/architect-report.md)

## From infrastructure code to a migration plan, in four engineered steps.

1. ### Analyze Infrastructure

   Read Terraform or OpenTofu code, or VMware RVTools inventories, from any of the seven supported sources.

   **105** files read

2. ### Assess & Map

   Identify STACKIT alternatives, configuration changes and architecture requirements.

   **44** migration units assessed

3. ### Generate Target Infrastructure

   Produce STACKIT Terraform artifacts, target architecture and migration work packages.

   **34** of 52 considered units drafted

4. ### Plan the Migration

   Organize required decisions, prerequisites, manual tasks and verification steps.

   **334** plan steps written

[Figures from the AWS Retail Store run.](https://stacktoit.com/examples/aws-retail-store/) · [View Original AWS Terraform](https://github.com/aws-containers/retail-store-sample-app/tree/main/terraform/ecs/default) · [Outputs on GitHub](https://github.com/stackToIT/stacktoit-examples/tree/main/examples/aws-retail-store) · Assessed at AWS commit [d7a380b](https://github.com/aws-containers/retail-store-sample-app/tree/d7a380b843e0759e58754f74188ea18252a51415/terraform/ecs/default) · StackToIT run of 12 November 2026 · [How StackToIT works](https://stacktoit.com/en/how-stacktoit-works/)

SOURCE CLOUDS → STACKIT

## Seven sources. One engine. One destination.

Whatever your estate runs on today, StackToIT applies the same engineering method: understand the infrastructure, map every service, build the deliverables and make each decision traceable.

- [![](https://stacktoit.com/clouds/aws.svg)](https://stacktoit.com/en/aws-to-stackit/)
  ### [Amazon Web Services](https://stacktoit.com/en/aws-to-stackit/)
  [Terraform and OpenTofu with AWS and AWS Cloud Control resources, from EC2 and EKS to RDS, DynamoDB and Lambda.](https://stacktoit.com/en/aws-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/aws-to-stackit/)
- [![](https://stacktoit.com/clouds/azure.svg)](https://stacktoit.com/en/azure-to-stackit/)
  ### [Microsoft Azure](https://stacktoit.com/en/azure-to-stackit/)
  [AzureRM and AzAPI estates, from AKS and Azure SQL to Cosmos DB, App Service and governance.](https://stacktoit.com/en/azure-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/azure-to-stackit/)
- [![](https://stacktoit.com/clouds/google-cloud.svg)](https://stacktoit.com/en/google-cloud-to-stackit/)
  ### [Google Cloud](https://stacktoit.com/en/google-cloud-to-stackit/)
  [Terraform and OpenTofu estates, from GKE and Cloud SQL to Cloud Run, BigQuery and Spanner.](https://stacktoit.com/en/google-cloud-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/google-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/vmware.svg)](https://stacktoit.com/en/vmware-to-stackit/)
  ### [VMware](https://stacktoit.com/en/vmware-to-stackit/)
  [RVTools exports (.xlsx or CSV): virtual machines, templates and port groups, with no agent in your estate.](https://stacktoit.com/en/vmware-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/vmware-to-stackit/)
- [![](https://stacktoit.com/clouds/huawei.svg)](https://stacktoit.com/en/huawei-cloud-to-stackit/)
  ### [Huawei Cloud](https://stacktoit.com/en/huawei-cloud-to-stackit/)
  [Terraform and OpenTofu estates, from ECS and CCE to RDS, GaussDB, OBS and FunctionGraph.](https://stacktoit.com/en/huawei-cloud-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/huawei-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/alibaba-cloud.svg)](https://stacktoit.com/en/alibaba-cloud-to-stackit/)
  ### [Alibaba Cloud](https://stacktoit.com/en/alibaba-cloud-to-stackit/)
  [Terraform and OpenTofu estates, from ECS and ACK to ApsaraDB RDS, PolarDB, OSS and MaxCompute.](https://stacktoit.com/en/alibaba-cloud-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/alibaba-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/oracle.svg)](https://stacktoit.com/en/oracle-cloud-to-stackit/)
  ### [Oracle Cloud Infrastructure](https://stacktoit.com/en/oracle-cloud-to-stackit/)
  [Terraform and OpenTofu estates, from compute and OKE to Oracle Database, MySQL HeatWave and Object Storage.](https://stacktoit.com/en/oracle-cloud-to-stackit/)

  [Explore the migration path](https://stacktoit.com/en/oracle-cloud-to-stackit/)

Every source runs through the same engine and delivers the same migration package. [Explore real results](https://stacktoit.com/examples/)

DIGITAL SOVEREIGNTY

## Sovereignty is not a checkbox. It is an architecture decision.

Advance your cloud sovereignty strategy with engineering facts: which services hold you, what each one takes to leave and which path leads to STACKIT. StackToIT makes it concrete for your whole estate.

[Read the sovereignty case](https://stacktoit.com/en/cloud-sovereignty/)

1. ### Digital sovereignty

   See which services bind you to your current provider and what each one takes to leave.

2. ### European cloud

   A concrete target on STACKIT for every service, instead of a general intention.

3. ### Vendor lock-in

   Every proprietary service is named, together with the change it needs on STACKIT.

4. ### Cloud independence

   Terraform you own and version, reviewed by your architects and applied by your own pipeline.

## Your migration assessment. Delivered by an expert.

Get a structured STACKIT migration assessment powered by the StackToIT engine. We analyze your infrastructure, review the findings and deliver a practical migration package your team can work with.

[Get Your Migration Assessment](https://stacktoit.com/en/#contact)[See the assessment service](https://stacktoit.com/en/services/migration-assessment/)

- Scope

  One working day of expert-led technical assessment, one workload or Terraform root

- Where it runs

  In your environment, or offline without outbound access

- You receive

  Target architecture, Terraform drafts, migration plan, decisions and data movement planning, reviewed by an engineer

- Price

  €2,490 net, fixed price

## How we start your migration

1. ### Agree the scope

   Together we choose one Terraform estate or VMware RVTools inventory from your sources and agree the assessment questions.

2. ### Run it in your environment

   You run StackToIT on your own computer under a pilot license. We support the onboarding.

3. ### Review the results

   Your architects review the assessment, the target plan and the decisions. You decide what to share with us.

### Your code stays with you

- Your Terraform or RVTools export is read locally and never uploaded.
- No cloud credentials are needed, and StackToIT changes nothing in any cloud.
- Values the provider marks as sensitive and known secrets are redacted in every output.
- By default, StackToIT downloads missing modules, providers and prices from their public hosts. Those hosts see host names and module addresses, not your files. Offline mode sends no request at all.

Implementation partner

## From Assessment to Implementation

When the migration calls for an enterprise implementation team, ARES Consulting carries it with your engineers. The cloud-native consultancy from Munich is an official STACKIT Silver Partner and covers cloud migration, platform engineering, application modernization, DevOps and operations.

> “We can recommend ARES Consulting as a project partner without reservation.”

Guido Schmidt, Dataport · translated from German

Clients quoted by ARES include Dataport, OBERMEYER Infrastruktur and uni-assist.

[Discuss Implementation](https://stacktoit.com/en/#contact)[About ARES Consulting](https://stacktoit.com/en/partners/ares-consulting/)

[![ARES Consulting](https://stacktoit.com/partners/ares-consulting-logo-white.webp)](https://stacktoit.com/en/partners/ares-consulting/)

- STACKIT

  Silver Partner · Professional & Managed Service Partner since 2023

- Team

  30+ cloud and DevOps consultants in Munich

- Track record

  50+ projects in pharma, finance, automotive and other sectors

- Clouds

  STACKIT, AWS, Microsoft Azure and Scaleway

[Listed in the STACKIT partner directory](https://stackit.com/en/partner/find-a-partner/ares)

## Your next move: STACKIT.

Tell us about your estate. We show you what StackToIT delivers for it: target architecture, Terraform artifacts and a structured migration plan.

Leave your contact details and our specialists will get in touch.

Prefer to write yourself? <connect@stacktoit.com>

Services: [Migration assessment service](https://stacktoit.com/en/services/migration-assessment/) · [Implementation with ARES Consulting](https://stacktoit.com/en/partners/ares-consulting/)
