Migration Hub vs Other AWS Migration Tools
Migration Hub is a tracking layer, not a migration engine — it complements rather than replaces tools like MGN and DMS.
| Tool | Purpose | Relationship to Hub |
|---|---|---|
| AWS MGN (Application Migration Service) | Server replication and cutover | Reports status to Migration Hub |
| AWS DMS (Database Migration Service) | Database replication and conversion | Reports status to Migration Hub |
| AWS Migration Hub | Centralized tracking dashboard | Aggregates data from all tools |
| AWS Migration Evaluator | Business case and cost modeling | Feeds into Hub discovery data |
Setting Up Migration Hub
Migration Hub setup requires selecting a home region and configuring data sources from your migration tools. Follow these steps:
- Select your home region: Choose the AWS region where Migration Hub will store your tracking data. This cannot be changed later.
- Enable discovery tools: Deploy the AWS Discovery Agent or Agentless Discovery Connector on your on-premises servers
- Connect migration tools: Authorize MGN, DMS, or partner tools to report status to Migration Hub
- Group servers into applications: Create application groups to track migrations at the application level rather than individual servers
For detailed migration planning, see our AWS migration process overview.
Migration Hub Pricing
AWS Migration Hub itself is free — you only pay for the underlying migration and discovery services. The Hub console, tracking, and strategy recommendations carry no additional charges. Costs come from:
- AWS Application Discovery Service agent or connector usage
- Underlying migration services (MGN, DMS) based on their individual pricing
- Data transfer charges for replication traffic
Best Practices for Migration Tracking
Effective migration tracking requires consistent application grouping and regular status reviews.
- Group servers by business application, not by infrastructure function
- Set up weekly migration status reviews using Migration Hub dashboards
- Tag all resources with migration wave identifiers for cross-referencing with MAP credit tracking
- Export migration data to Amazon QuickSight for executive-level reporting
- Use MAP engagement milestones to align tracking with program deliverables
Frequently Asked Questions
Is AWS Migration Hub still available?
Existing customers retain full access to Migration Hub. However, as of November 2025, AWS is no longer accepting new customers for certain Migration Hub features. Check AWS documentation for the latest status and alternatives.
Does Migration Hub work with non-AWS migration tools?
Yes, Migration Hub integrates with several third-party migration tools through the Migration Hub API. Partners like CloudEndure (now part of AWS) and other ISV tools can report migration status to the Hub.
Can I use Migration Hub for multi-cloud migrations?
Migration Hub is designed for migrations to AWS. While it can discover and track workloads being moved from any source (including other clouds), the destination must be AWS infrastructure.
What is the difference between Migration Hub and AWS Migration Evaluator?
Migration Evaluator builds the business case for migration by modeling costs and right-sizing recommendations. Migration Hub tracks the actual migration progress once you begin moving workloads. They serve different phases of the migration lifecycle.
How does Migration Hub handle large-scale enterprise migrations?
Migration Hub supports migrations of any scale. For large enterprises, use application grouping to organize hundreds or thousands of servers into logical migration waves, and leverage the Hub API for automated status reporting.
Does Migration Hub integrate with AWS MAP?
Yes, Migration Hub data can be used to verify migration progress for MAP credit allocation. However, MAP 2.0 credit tracking relies on resource tagging rather than Migration Hub status updates.
