HUAWEI CLOUD TO STACKIT
Huawei Cloud to STACKIT migration
Moving off Huawei Cloud starts with knowing what you run. StackToIT reads your Huawei Cloud Terraform and gives each resource a STACKIT target, a treatment and a reason, then writes the Terraform draft and the migration sequence.
From Huawei Cloud services to a STACKIT plan
Huawei 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
Huawei Cloud resources, modules and dependencies from Terraform and OpenTofu root modules. Nothing connects to your Huawei Cloud account.
Reads the database engine
An 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.
| Huawei Cloud | STACKIT target | Treatment |
|---|---|---|
| Elastic Cloud Server | STACKIT Compute Engine | Reconfigure |
| Cloud Container Engine | STACKIT Kubernetes Engine (SKE) | Replatform |
| RDS | PostgreSQL Flex, MariaDB, SQLServer Flex | Replatform |
| GaussDB | PostgreSQL Flex or MariaDB, after a conversion | Redesign |
| Object Storage Service | STACKIT Object Storage | Reconfigure |
| Distributed Cache Service | Key Value Store (Valkey) | Reconfigure |
| DMS for RabbitMQ | STACKIT RabbitMQ | Replatform |
| DMS for Kafka | Self-managed Kafka-compatible broker on SKE | Containerize |
| FunctionGraph | SKE or Cloud Foundry | Containerize |
| Data Warehouse Service | Lakehouse on Object Storage or a self-managed warehouse | Redesign |
| IAM | Decided case by case | Architect decision |
Huawei Cloud migration guides
Migration guides
- The complete Huawei Cloud to STACKIT migration guide →
- Huawei Cloud RDS to STACKIT managed databases →
- Huawei DMS to STACKIT: Kafka, RabbitMQ and RocketMQ →
- Huawei Cloud IAM migration and access control on STACKIT →
- Huawei EVS and SFS Turbo to STACKIT storage →
Service mapping
- Huawei Cloud services mapped to STACKIT, from an assessed estate →
- Huawei Cloud VPC, subnets, NAT and security groups on STACKIT →
Terraform and inventory tutorials
- Huawei Cloud ECS to STACKIT Compute Engine →
- Huawei Cloud CCE to STACKIT Kubernetes Engine →
- Huawei Cloud Terraform to STACKIT, step by step →
- Huawei OBS to STACKIT Object Storage, worked through →
- Huawei Cloud ELB to STACKIT load balancing, hands on →
- Huawei DCS Redis to STACKIT Valkey →
- Huawei KMS and CSMS to STACKIT KMS and Secrets Manager →
Checklists and runbooks
Architecture guides
- GaussDB to STACKIT: MySQL and openGauss options →
- Moving Huawei FunctionGraph functions to STACKIT →
- Huawei DWS, MRS and DLI migration architecture →
Real-world examples
What it gives the business
A plan for European infrastructure
See what a move from Huawei Cloud to STACKIT, a German cloud, asks of each system before you commit budget.
Reuse your container investment
CCE clusters target STACKIT Kubernetes Engine, and FunctionGraph functions move to SKE or Cloud Foundry as containers.
See the large items early
GaussDB, Data Warehouse Service and MapReduce Service 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.