AZURE TO STACKIT
Azure to STACKIT migration
Turn your Azure Terraform into a STACKIT migration plan. StackToIT shows where your Azure estate moves cleanly, where it is tied to the platform and which decisions your architects need to make.
From landing zone to STACKIT target
An Azure estate is more than virtual machines. Managed databases, platform services, private networking and governance all behave differently on the target, and each one needs its own answer.
AzureRM and AzAPI
StackToIT reads Terraform and OpenTofu written with either provider, so resources defined through the Azure REST API shape are assessed too.
Identity and network included
Dedicated readers cover routing, security rules, identity and placement, so these concerns appear in the plan rather than after cutover.
Reviewable target
Terraform drafts, target architecture, execution plan and open decisions, in files your platform team can read and change.
Where your services go
Typical outcomes from the StackToIT knowledge base. The treatment of each resource depends on its configuration, and the report states the reason.
| Azure | STACKIT target | Treatment |
|---|---|---|
| Virtual Machines | STACKIT Compute Engine | Reconfigure |
| Azure Kubernetes Service | STACKIT Kubernetes Engine (SKE) | Replatform |
| Azure Database for PostgreSQL | PostgreSQL Flex | Replatform |
| Azure SQL, SQL Managed Instance | SQLServer Flex | Replatform |
| Storage accounts | STACKIT Object Storage | Replatform |
| Key Vault | Secrets Manager and STACKIT KMS | Reconfigure |
| Azure Cache for Redis | Key Value Store (Valkey) | Reconfigure |
| Service Bus | STACKIT RabbitMQ | Replatform |
| App Service, Functions | Cloud Foundry or SKE | Replatform or Containerize |
| Cosmos DB | MongoDB Flex or PostgreSQL Flex (JSONB) | Replatform or Redesign |
| Azure Firewall | Decided case by case | Architect decision |
What it gives the business
Start with what stays familiar
PostgreSQL and SQL Server workloads have managed targets on STACKIT, so your teams can begin with database engines they already run.
Name the platform commitments
Cosmos DB, App Service and Functions are where Azure estates are most tied to the platform. Each gets a route: replatform, containerize or redesign.
Keep governance in the plan
Management groups map to STACKIT folders. Policy assignments have no managed counterpart and become policy as code, a decision you can budget in advance.
Your architects review each draft before anything is applied. For databases from a private PostgreSQL or SQL Server source, set the network access scope in the draft explicitly.
Planning a migration to STACKIT?
Let's explore how StackToIT can help assess your infrastructure and prepare a structured migration plan.