Migration Hub (closed to new customers)

Closed to new customers

AWS Migration Hub stopped accepting new customers on 7 November 2025. Existing customers can continue using it. New accounts should use AWS Transform for the same discovery, planning and tracking work.

Migration Hub was the single place to discover existing servers, group them into applications, plan a migration and watch the status of each application as it moved. Its value was consolidation: whichever tool was doing the actual moving reported status back into the Hub, so a programme manager had one dashboard instead of one per tool.

It also carried a home Region — migration tracking data was stored in the Region chosen on first use, independently of the Regions being migrated into.

Two tools reported into it: AWS Application Migration Service (now AWS Transform MGN) for server rehosting and AWS Database Migration Service for databases. AWS Server Migration Service, which the older documentation also listed, has been retired and is no longer a supported source of status.

Three capabilities were grouped under the Migration Hub name and are worth distinguishing when reading older material: Strategy Recommendations, which suggested a transformation path per application; Refactor Spaces, for incremental refactoring towards microservices; and Migration Hub Orchestrator, which ran templated migration workflows.

What replaces it

AWS Transform is an agentic service that covers the same ground and more: inventory collection from multiple sources, dependency mapping, prioritised migration waves, landing-zone creation, network translation into a VPC design, and the rehost itself. There is no data migration to perform when moving across — new discovery and planning work simply starts in AWS Transform.

For what the discovery half of this used to look like, see Application Discovery Service.