Source environment
Cloud / Knowledge library
AWS Migration Hub
Tracks and orchestrates application migrations across AWS and partner tools
Why learn AWS Migration Hub?
Teams use AWS Migration Hub to adopt cloud migration assessment and orchestration without building the complete underlying platform themselves.
The problem it solves
Discovers, assesses, plans, and tracks workload migration
Where it came from
AWS Migration Hub is Amazon Web Services's offering for cloud migration assessment and orchestration. Its closest catalog counterparts are Azure Migrate and Google Cloud Migration Center; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of AWS Migration Hub.
- Choose a workload that fits AWS Migration Hub.
- Identify one operational tradeoff of AWS Migration Hub.
- Compare AWS Migration Hub with Azure Migrate.
- Compare AWS Migration Hub with Google Cloud Migration Center.
Documentation and sources
- AWS cloud services catalog (aws.amazon.com)
Connect the ideas
Alternatives
Real World Example
Unified Migration Orchestration for Global Retailers
A multinational retail enterprise managing a fragmented portfolio of legacy on-premises data centers and disparate cloud-native microservices.
The business problem
The IT operations team struggles with visibility, as they lack a centralized dashboard to track the progress of hundreds of individual application migrations occurring across different AWS regions and third-party partner tools.
How this topic solves it
AWS Migration Hub serves as the central control plane, aggregating status updates from AWS Application Discovery Service and AWS Application Migration Service (MGN) into a single, unified view to track migration progress across the entire portfolio.
- Enable AWS Migration Hub in the home region to serve as the central repository for migration data.
- Deploy AWS Application Discovery Service agents on-premises to map existing dependencies and server configurations.
- Integrate third-party migration tools with the Migration Hub API to push status updates into the central dashboard.
- Configure AWS Application Migration Service (MGN) to automate the replication of source servers into the target AWS environment.
- Monitor the unified status dashboard to identify bottlenecks in the migration lifecycle across all integrated tools.
This diagram illustrates how Migration Hub aggregates data from various discovery and migration services to provide a single view.
Maps dependencies
Replicates data
Central dashboard
- On-Premises Servers → collects metadata → Discovery Service
- On-Premises Servers → replicates blocks → Migration Service (MGN)
- Discovery Service → reports status → Migration Hub
- Migration Service (MGN) → reports progress → Migration Hub
Expected business outcome
The organization achieves a consolidated view of migration status, enabling stakeholders to make informed decisions and synchronize cutover activities across geographically dispersed teams.
Limitations and checks
Migration Hub acts as a tracking and orchestration layer rather than a data migration engine; it relies on the accuracy of status reporting from integrated tools. To verify data integrity, administrators must manually reconcile the status in the Hub against the source tool logs.