Complete Guide: Migrating from On-Premise to Alibaba Cloud

Cloud migration is no longer a question of "if" but "how." Moving workloads from on-premise data centers to Alibaba Cloud involves more than technical execution—it demands rigorous project planning and risk management. This guide provides an end-to-end framework to help you navigate the journey.

Phase 1: Assessment and Planning

1.1 Asset Inventory

The first step is a comprehensive inventory of your existing IT estate:

| Dimension | Key Information | Suggested Tools | |-----------|----------------|-----------------| | Servers | Count, specs, utilization, dependencies | Alibaba Cloud Migration Assessment Tool | | Applications | Tech stack, architecture patterns, SLA requirements | Manual review + APM tools | | Data | Volume, growth rate, compliance needs | Database assessment scripts | | Network | Bandwidth, latency, security policies | Network probes |

1.2 Migration Strategy Selection

The industry-standard 6R framework applies equally to Alibaba Cloud:

| Strategy | Description | Use Case | Effort | |----------|-------------|----------|--------| | Rehost (Lift & Shift) | Move as-is to the cloud | Tight timelines, legacy systems | Low | | Replatform | Minor adjustments to leverage cloud features | Database upgrades, middleware swaps | Medium | | Refactor | Redesign for cloud-native architecture | Long-term strategy, microservices | High | | Repurchase | Switch to SaaS alternatives | Office software, CRM | Low | | Retire | Decommission unnecessary systems | Obsolete or redundant systems | None | | Retain | Keep on-premise for now | Compliance constraints, special hardware | None |

Start with low-risk, high-value systems and build experience before tackling core business workloads.

1.3 Cost Comparison

Always perform a TCO analysis before migrating:

| Cost Item | On-Premise | Alibaba Cloud (ecs.g7.2xlarge) | |-----------|-----------|-------------------------------| | 8C32G server (3-year) | ¥80,000–120,000 | ¥36,500 (subscription) | | Colocation/power | ¥2,000–5,000/month/rack | Included | | Operations staff | 2–3 people | 50%+ reduction | | Hardware refresh | 3–5 year cycle | Not needed | | Disaster recovery | Self-built, costly | Built-in same-city/cross-region DR |

Phase 2: Network Connectivity

2.1 VPN Gateway (Small-Scale Migration)

Alibaba Cloud IPsec VPN Gateway establishes encrypted tunnels in under 30 minutes:

• Bandwidth: Up to 1 Gbps
• Cost: From ¥270/month (gateway + bandwidth)
• Best for: Management traffic, small data volumes

2.2 Express Connect (Large-Scale Migration)

For datasets exceeding 10 TB or latency-sensitive workloads:

| Spec | Bandwidth | Approx. Monthly Cost | Time to Migrate 100 TB | |------|-----------|---------------------|----------------------| | 50M | 50 Mbps | ¥3,500+ | ~20 days | | 100M | 100 Mbps | ¥5,500+ | ~10 days | | 1G | 1 Gbps | ¥28,000+ | ~1 day |

2.3 Smart Access Gateway

For branch office scenarios, Alibaba Cloud Smart Access Gateway (SAG) provides one-click cloud connectivity with 4G/5G backup links.

Phase 3: Server Migration

3.1 SMC (Server Migration Center)

Alibaba Cloud SMC is the core migration tool, supporting physical servers, VMs, and other cloud platforms:

Steps:

1. Install the SMC client on the source server:

wget https://smc-client.aliyun.com/smc/latest/linux/amd64/smc.tar.gz
tar -xf smc.tar.gz
cd smc
./go2aliyun_client --accesskey=YOUR_AK --secretkey=YOUR_SK

2. Create a migration task in the SMC console
3. Select target instance type and VPC
4. Execute migration—SMC automatically handles full + incremental replication
5. Validate and switch traffic

3.2 Migration Method Comparison

| Method | Downtime | Scale | Cost | |--------|----------|-------|------| | SMC online migration | Minutes | 1–100 servers | Free | | Offline migration (image import) | Hours | Pre-existing images | Storage + traffic | | Cross-cloud migration tools | Minutes | Other cloud platforms | Free |

3.3 Instance Type Mapping

| On-Premise Config | Recommended Instance | Monthly Cost (Subscription) | |-------------------|---------------------|---------------------------| | 4C8G | ecs.g7.xlarge | ¥456 | | 8C32G | ecs.g7.2xlarge | ¥912 | | 16C64G | ecs.g7.4xlarge | ¥1,824 | | GPU (V100) | ecs.gn6v-c8g1.8xlarge | ¥18,500+ |

Compared to GCP n2 series, Alibaba Cloud g7 instances offer significant price advantages in mainland China with higher internal network bandwidth.

Phase 4: Database Migration

4.1 DTS (Data Transmission Service)

DTS supports full + incremental migration for minimal-downtime cutover:

Supported Sources:

• MySQL, SQL Server, PostgreSQL, Oracle
• MongoDB, Redis
• Self-managed or other cloud RDS instances

Process:

1. Create a DTS migration task with source and target configurations
2. After pre-check passes, start full migration
3. Automatically transition to incremental sync
4. Switch during low-traffic window—downtime under 5–10 minutes

4.2 Migration Costs

| Data Volume | DTS Fee | Estimated Time | |-------------|---------|---------------| | 100 GB | ¥280 | 2–4 hours | | 1 TB | ¥1,200 | 8–16 hours | | 10 TB | ¥5,000+ | 1–3 days |

Phase 5: Cutover and Validation

5.1 Cutover Checklist

• [ ] DNS TTL reduced to 300 seconds in advance
• [ ] Incremental sync lag < 1 second
• [ ] All application health checks passing
• [ ] Rollback plan confirmed (keep on-prem for 7 days)
• [ ] Monitoring and alerting configured
• [ ] Business stakeholders confirmed maintenance window

5.2 Cutover Timeline

1. T-3 days: Full migration complete, incremental sync ready
2. T-1 day: Final validation, notify stakeholders
3. T-0: Stop app → wait for incremental sync → switch DNS → start cloud app → validate
4. T+1 day: Confirm stability, decommission on-prem services
5. T+7 days: Reclaim on-prem resources

Phase 6: Post-Migration Optimization

Migration is the beginning, not the end:

1. Auto Scaling: Configure ESS to add/remove instances based on load
2. Storage Tiering: OSS Standard → IA → Archive saves 60%+ on storage
3. Reserved Instances: 1-year saves ~30%, 3-year saves ~50%
4. Right-sizing: Adjust instance types based on CloudMonitor data

Hybrid Cloud Strategy

For systems that can't migrate immediately, Alibaba Cloud offers mature hybrid cloud solutions:

• Hybrid Networking: Dual-link assurance with Express Connect + VPN
• Hybrid Backup: HBR supports unified backup policies across on-prem and cloud
• Tencent Cloud and AWS can complement your multi-cloud architecture

Conclusion

Migrating from on-premise to Alibaba Cloud is a systematic undertaking, but with tools like SMC and DTS, most enterprises can complete core business migration within 1–3 months with minute-level downtime.

Duoyun Cloud is an authorized Alibaba Cloud partner offering end-to-end migration services from assessment to execution. By purchasing Alibaba Cloud resources through Duoyun, you receive exclusive channel discounts (5%–15% below list price), dedicated architect support, and unified multi-cloud billing. Visit duoyun.io today for a free migration assessment.