ALIBABA CLOUD TO STACKIT
Alibaba Cloud to STACKIT migration
Moving off Alibaba Cloud starts with knowing what you run. StackToIT reads your Alibaba Cloud Terraform and gives each resource a STACKIT target, a treatment and a reason, then writes the Terraform draft and the migration sequence.
From Alibaba Cloud services to a STACKIT plan
Alibaba Cloud estates rely on services with their own APIs and data engines. Some have a clear STACKIT target and some need a decision, so each resource gets its own treatment and reason.
Reads your Terraform
Alibaba Cloud resources, modules and dependencies from Terraform and OpenTofu root modules. Nothing connects to your Alibaba Cloud account.
Reads the database engine
An ApsaraDB RDS instance is mapped by its engine: PostgreSQL to PostgreSQL Flex, MySQL and MariaDB to STACKIT MariaDB, SQL Server to SQLServer Flex.
Writes the package
STACKIT Terraform draft, target architecture, execution sequence and a register of open choices for your architects.
Where your services go
Typical outcomes from the versioned StackToIT rule base. Each resource is treated according to its actual configuration, and the report states the reason.
| Alibaba Cloud | STACKIT target | Treatment |
|---|---|---|
| Elastic Compute Service | STACKIT Compute Engine | Reconfigure |
| Container Service for Kubernetes | STACKIT Kubernetes Engine (SKE) | Replatform |
| ApsaraDB RDS | PostgreSQL Flex, MariaDB, SQLServer Flex | Replatform |
| PolarDB | Decided case by case | Redesign |
| Object Storage Service | STACKIT Object Storage | Reconfigure |
| ApsaraDB for Redis | Key Value Store (Valkey) | Reconfigure |
| Message Queue for RabbitMQ | STACKIT RabbitMQ | Replatform |
| Message Queue for Kafka | Self-managed Kafka-compatible broker on SKE | Containerize |
| Function Compute | SKE or Cloud Foundry | Containerize |
| MaxCompute, AnalyticDB | Lakehouse on Object Storage or a self-managed warehouse | Redesign |
| Resource Access Management | Decided case by case | Architect decision |
Alibaba Cloud migration guides
Migration guides
- The complete Alibaba Cloud to STACKIT migration guide →
- ApsaraDB RDS to STACKIT managed databases →
- ApsaraDB Redis and MongoDB migration to STACKIT →
- Alibaba NAS and cloud disks to STACKIT File Storage and Block Storage →
- Alibaba Cloud RAM, KMS and secrets migration to STACKIT →
Service mapping
- Alibaba Cloud vs STACKIT: service mapping →
- Alibaba Cloud VPC, vSwitch, NAT and security groups on STACKIT →
Terraform and inventory tutorials
- Alibaba Cloud ECS to STACKIT Compute Engine →
- Alibaba Cloud ACK to STACKIT Kubernetes Engine →
- Alibaba Cloud Terraform to STACKIT: the workflow, step by step →
- Alibaba OSS to STACKIT Object Storage, step by step →
- Alibaba SLB, ALB and NLB migration, step by step →
- Alibaba Function Compute migration, from Terraform to containers →
Checklists and runbooks
Architecture guides
- PolarDB migration strategies for STACKIT →
- Alibaba Cloud Kafka, RabbitMQ and RocketMQ on STACKIT →
- MaxCompute and AnalyticDB: designing the STACKIT target →
- Alibaba Cloud Tablestore and HBase on STACKIT →
Real-world examples
What it gives the business
A plan for European infrastructure
See what a move from Alibaba Cloud to STACKIT, a German cloud, asks of each system before you commit budget.
Reuse your container investment
ACK clusters target STACKIT Kubernetes Engine, and Function Compute functions move to SKE or Cloud Foundry as containers.
See the large items early
PolarDB, MaxCompute and AnalyticDB have no direct counterpart and are marked for redesign, so they are in the plan before the budget is set.
Your architects review each target before anything moves. Run StackToIT on your estate and get the complete migration package for it.
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.