AWS Migration Hub
Single dashboard to discover on-premises servers, group them into applications, and track migration progress across every tool you're using.
Verified against AWS documentation · 2026-09-09
Key facts
- 01Tracks migrations, doesn't perform them — MGN, DMS, and partner tools do the moving; Migration Hub just aggregates their status
- 02Discovery data comes from Application Discovery Service; you group discovered servers into applications, then track progress per application
- 03Home Region: one Region stores all tracking data, but you can migrate into any Region — changing the home Region afterward requires an AWS Support ticket
- 04Reality check: closed to new customers since Nov 7, 2025, replaced by AWS Transform. Existing migrations run unaffected, and CLF-C02 still expects you to know it
Exam triggers
Phrases and scenarios that point here.
- "Single pane of glass", "central dashboard", "visibility across migration tools", "track progress in one place"
- Several teams using different migration tools, leadership wants one status view → Migration Hub
- Migrations landing in multiple Regions, one console to watch them → home Region aggregates all of it
- "What servers do we have and what talks to what?" before any migration → Application Discovery Service feeding Migration Hub
Not this service
- Actually moving servers → Application Migration Service (MGN); moving databases → Database Migration Service (DMS)
- Building the cost case before committing to migrate → Migration Evaluator
- Starting a brand-new migration program today → AWS Transform
Use cases
- 01A data centre exit where the Windows team uses MGN, the DBA team uses DMS, and the steering committee needs one number for 'how far along are we' — Migration Hub is that screen
- 02Wave planning: group the twelve servers behind one ERP into a single application, migrate the wave, mark it complete, move to the next — instead of chasing individual hostnames
- 03A regional rollout where the EU app lands in Frankfurt and the APAC app lands in Singapore, both watched from one home Region console
- 04Catching the forgotten license server in discovery data before it takes down the application at cutover weekend
- 05Giving finance or an auditor portfolio-level progress instead of three tool-specific spreadsheets that never quite reconcile
How it's charged
- 01No charge for Migration Hub itself — discovery storage, application grouping, and status tracking are all free
- 02You pay for the tools doing the real work: MGN replication servers, DMS instance hours, EBS volumes, data transfer
- 03Refactor Spaces is the one paid piece, billed per environment-hour plus API requests
- 04Refactor Spaces provisions Transit Gateway and Network Load Balancer in your account — those bill at their own rates on top
- 05Refactor Spaces free tier: 2,160 environment hours per month for 90 days, plus 500,000 API requests per month with no expiry
