STACKIT MIGRATION ASSESSMENT
STACKIT migration assessment
Before budgets are signed, leadership needs to know what the move involves. A StackToIT assessment answers that from your infrastructure code: every resource, its STACKIT target, the work it takes and the decisions it needs.
What your assessment answers
What moves, and how
Every migration unit with its class, STACKIT target and reason, from direct moves to the services that need a redesign.
What it takes
An ordered execution plan with prerequisites, data movement, cutover and verification steps.
What must be decided
A decision register with owners: the architecture questions the code cannot answer, named early.
Your assessment package
Delivered as files: readable in a browser, versionable in Git, and machine-readable for your own tooling.
- index.html
- The full assessment, unit by unit, offline in any browser
- executive/
- Summary and decisions for leadership
- architecture/
- Current and target architecture diagrams
- terraform/
- STACKIT Terraform for the target
- migration/
- Migration plan and work packages
- execution/
- Ordered execution plan with verification steps
- financial/
- Priced cost lines from public price lists
- engineering/
- Architect report, findings and evidence trace
- assessment.json
- Every result in a structured, machine-readable form
How an engagement runs
Scope
We agree one estate: Terraform or OpenTofu from AWS, Azure, Google Cloud, Huawei Cloud, Alibaba Cloud or Oracle Cloud, or a VMware RVTools export.
Run
You run StackToIT on your own machine. Your code stays with you, and no cloud credentials are needed.
Review
Your architects work through the package and answer the open decisions. The next run reads the answers.
Decide
Leadership receives a migration scope grounded in engineering facts, ready for budgeting and planning.
What a real assessment contains
From the published AWS Retail Store run: five services on Amazon ECS with Aurora, DynamoDB, OpenSearch, ElastiCache and Amazon MQ.
Source read
105 files and 23 module calls, 13 of them registry modules, resolved into 282 resources and 44 migration units.
Classified
34 units are Reconfigure, 9 Replatform and 1 Redesign. Each carries a STACKIT target, a confidence and a reason.
Drafted
Of 52 units the draft considered, 38 became STACKIT Terraform, 11 need no resource on STACKIT and 3 are manual work.
Planned
331 plan steps, 57 of them carried out by OpenTofu or a script. 96 steps cover cutover, verification and retirement.
Asked
16 decisions to make, each with a named owner role and a set of options to choose from.
Who works on what
The package assigns work to roles, so a steering group can see who has to answer what before the pilot.
45 work packages
Owned by the Network Architect (11), Platform Architect (10), Security Architect (7), Data Architect (7), Identity Architect (6), Migration Owner (3) and Storage Architect (1).
Nine phases
Prepare, foundation, platform, security, workload, data, cutover, verify and decommission, so each team sees its part and its place in the order.
112 decision records
Each names the role that answers it: Network Architect 34, Platform Architect 27, Identity Architect 21, Security Architect 19, Data Architect 6. Five state no role.
Proven on a real AWS estate
The AWS Retail Store Sample App, a public Terraform project from AWS, assessed by StackToIT and published in full, exactly as the run wrote it.
View Case Study- 282
- Terraform resource declarations analyzed
- 44
- migration units identified
- 38
- target units generated, from 52 considered
- 331
- plan steps written
Questions leadership asks
What does a STACKIT migration assessment include?
Every resource classified and mapped to STACKIT, target architecture diagrams, STACKIT Terraform, an execution plan, priced cost lines and a decision register.
Do we have to share our code?
No. StackToIT runs on your own machine, reads your files locally and needs no cloud credentials. You decide what you share with us.
Which estates can be assessed?
Terraform and OpenTofu estates from AWS, Microsoft Azure, Google Cloud, Huawei Cloud, Alibaba Cloud and Oracle Cloud, and VMware estates exported with RVTools.
Does the assessment change anything in our cloud?
No. StackToIT reads and writes files. It creates, changes and deletes nothing in any cloud and moves no data. Every step is carried out by a person, by OpenTofu or by a script you run.
How do we know the package is complete?
stacktoit verify checks the package against its manifest. For the Retail Store run it reported 145 files matching by size and SHA-256, and 7 of 7 checks passing.
Which steps are ready to start?
The package says so per step. In the Retail Store run, 48 of the 57 automated steps are free of decisions and manual prerequisites. They wait only for values such as project_id, which you supply.
Sources
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.