---
title: "STACKIT Migration Assessment Service | StackToIT"
url: https://stacktoit.com/en/services/migration-assessment/
---

MIGRATION ASSESSMENT SERVICE

# Your STACKIT Migration Assessment. One Working Day. Real Engineering Deliverables.

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

[Request Your Fixed-Price Assessment](https://stacktoit.com/en/services/migration-assessment/#contact)[Explore Real Results](https://stacktoit.com/examples/)

## The Migration Assessment Sprint

€2,490 net, fixed price

- One working day of expert-led technical assessment
- One defined workload or Terraform root from one source platform
- Final package within two business days after the assessment day, once inputs and prerequisites are complete
- One results meeting with your team

[Request Assessment](https://stacktoit.com/en/services/migration-assessment/#contact)

### Enterprise Assessment

For estates beyond one workload, we scope the assessment with you and quote it individually.

- Several applications or Terraform roots
- Large estates and cross-account or cross-cloud dependencies
- Complex stateful systems
- Several review workshops and deeper architecture investigation

[Request a Quote](https://stacktoit.com/en/services/migration-assessment/#contact)

## How the assessment runs

A fixed sequence with clear inputs and a defined end. The engineering work happens on one day; the reviewed package follows.

1. ### Scope

   A short call to agree the workload, the source platform, the execution environment and the questions the assessment must answer.

2. ### Assess

   On the assessment day StackToIT runs on your source. We work through classifications, targets, dependencies and open decisions with your engineers.

3. ### Review

   We review scope, unknowns, the Terraform draft and its validation, the migration plan and the data movement steps, then prepare the package.

4. ### Hand over

   A results meeting walks your team through the package, the key decisions and the next steps you choose.

The assessment itself takes one working day. The reviewed package follows within two business days, once inputs and prerequisites are complete.

## What your team receives

Every deliverable is a file the StackToIT engine writes, reviewed by an engineer before handover. Open each one in the public Retail Store example.

- ### Executive migration brief

  The state of the estate and the decisions ahead, on one page for leadership.

  [executive/brief.md](https://stacktoit.com/examples/aws-retail-store/files/executive/brief.md)

- ### Resource inventory and migration units

  Every resource classified and grouped into the units a migration actually moves.

  [index.html](https://stacktoit.com/examples/aws-retail-store/report/)

- ### STACKIT service mapping

  Source service to STACKIT target, with the migration class and the reason for each.

  [migration/source-target.csv](https://stacktoit.com/examples/aws-retail-store/files/migration/source-target.csv)

- ### Current and target architecture

  Diagrams of the existing estate and the proposed STACKIT architecture.

  [architecture/](https://stacktoit.com/examples/aws-retail-store/#architecture)

- ### Dependencies and blockers

  What depends on what, what must exist first and what stands in the way.

  [migration/prerequisites.md](https://stacktoit.com/examples/aws-retail-store/files/migration/prerequisites.md)

- ### Architecture decisions and required inputs

  Each open question with its options and owner, so your architects decide on facts.

  [executive/decisions.md](https://stacktoit.com/examples/aws-retail-store/files/executive/decisions.md)

- ### STACKIT Terraform drafts

  Target Terraform for every unit with a supported STACKIT target, statically validated where providers are available.

  [terraform/](https://stacktoit.com/examples/aws-retail-store/#terraform)

- ### Migration plan and work packages

  Ordered steps, waves and work packages your team can schedule.

  [migration/roadmap.md](https://stacktoit.com/examples/aws-retail-store/files/migration/roadmap.md)

- ### Data movement planning

  For stateful systems: candidate methods, checks, cutover and rollback decisions per data store.

  [migration/data-movement.md](https://stacktoit.com/examples/aws-retail-store/files/migration/data-movement.md)

- ### Technical handover and validation

  Engineering findings, evidence and the validation status of every generated artifact.

  [engineering/architect-report.md](https://stacktoit.com/examples/aws-retail-store/report/engineering/architect-report.md)

- ### The complete output package

  The full StackToIT run as files: readable offline in any browser, yours to version and keep.

  [output/](https://github.com/stackToIT/stacktoit-examples/tree/main/examples/aws-retail-store)

Drafts are proposals for your architects: they review and approve every change before anything is applied, and the package states exactly what was generated, validated and decided.

## Where the assessment runs

Choose the environment that fits your security model. All three use the same engine and deliver the same package.

- ### DefaultIn your environment

  StackToIT runs on a machine you control, against your existing Terraform, OpenTofu or RVTools export. Your source stays in your network, no cloud credentials are needed, and we facilitate the run and review the results with you.

- ### IsolatedOffline, without outbound access

  For networks without internet access. We prepare the release binary, your source with its modules, a local provider mirror and the price data in advance. In offline mode StackToIT sends no request at all, and the package states which checks ran locally.

- ### On requestPrepared working environment

  You provide authorized source material to an isolated working environment we prepare and operate for your engagement only. Set up individually per engagement; there is no self-service upload.

StackToIT reads files. It changes nothing in any cloud and never applies Terraform.

## Supported sources

Terraform or OpenTofu for AWS, Microsoft Azure, Google Cloud, Huawei Cloud, Alibaba Cloud and Oracle Cloud, and VMware estates exported with RVTools.

- [![](https://stacktoit.com/clouds/aws.svg)AWS → STACKIT](https://stacktoit.com/en/aws-to-stackit/)
- [![](https://stacktoit.com/clouds/azure.svg)Azure → STACKIT](https://stacktoit.com/en/azure-to-stackit/)
- [![](https://stacktoit.com/clouds/google-cloud.svg)Google Cloud → STACKIT](https://stacktoit.com/en/google-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/vmware.svg)VMware → STACKIT](https://stacktoit.com/en/vmware-to-stackit/)
- [![](https://stacktoit.com/clouds/huawei.svg)Huawei Cloud → STACKIT](https://stacktoit.com/en/huawei-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/alibaba-cloud.svg)Alibaba Cloud → STACKIT](https://stacktoit.com/en/alibaba-cloud-to-stackit/)
- [![](https://stacktoit.com/clouds/oracle.svg)Oracle Cloud → STACKIT](https://stacktoit.com/en/oracle-cloud-to-stackit/)

## See the output before you order

Two public estates, assessed with StackToIT and published in full. They are public sample projects, not customer engagements.

- [AWS Retail Store example](https://stacktoit.com/examples/aws-retail-store/)
- [Google Cloud Python Web App example](https://stacktoit.com/examples/gcp-python-webapp/)
- [Technical documentation](https://stacktoit.com/docs/)
- [What a STACKIT migration assessment answers](https://stacktoit.com/en/stackit-migration-assessment/)

## After the assessment, you choose

The assessment stands on its own. It commits you to no implementation partner, and the path depends on complexity, expertise and capacity, not on resource count alone.

1. ### Self-managed

   Your engineers implement the migration with the package as their working basis.

2. ### Led by StackToIT

   Smaller, clearly bounded engineering work delivered directly by the StackToIT team.

3. ### Led by ARES Consulting

   Larger enterprise migrations delivered by ARES Consulting, an official STACKIT Professional & Managed Service Partner.

[About implementation with ARES Consulting](https://stacktoit.com/en/partners/ares-consulting/)

## Questions before you order

What do you need from us?

The Terraform or OpenTofu root of one workload, or an RVTools export, plus an engineer who knows the estate for the assessment day. No cloud credentials and no Terraform state.

Does our source code leave our network?

Not in the default setup: StackToIT runs on a machine you control. Only if you choose the prepared working environment do you hand over source material, and only what you authorize.

Does the assessment change anything in our cloud?

No. StackToIT reads files and writes a package. It needs no cloud access, deploys nothing and never applies Terraform. Your team decides and applies.

How is the price fixed?

The sprint covers one workload or Terraform root from one source platform, with a defined day, package and results meeting. We confirm scope and price in writing before we start.

What if our estate is larger?

Several applications, roots or cloud accounts become an Enterprise Assessment, scoped with you and quoted individually.

Can we implement the migration ourselves?

Yes. The package is built for your engineers. Implementation support from StackToIT or ARES Consulting is optional.

## 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: [Implementation with ARES Consulting](https://stacktoit.com/en/partners/ares-consulting/)
