AWS Migration Hub is no longer open to new customers as of November 7, 2025. For capabilities similar to AWS Migration Hub, explore [AWS Transform](https://aws.amazon.com/transform). # Getting started with AWS Migration Hub Getting started In this section, you can find information about how to get started with AWS Migration Hub. Included are steps to introduce you to the initial console pages that Migration Hub presents to a new user. **Note** If you are a developer or are interested in sending migration status from a migration tool, script, or custom code, see [AWS Migration Hub API](api-reference.md) and [AWS Migration Hub Home Region API Reference](https://docs.aws.amazon.com//migrationhub-home-region/latest/APIReference/Welcome.html). All Migration Hub and AWS Application Discovery Service API commands must be called from within the home Region only, and they require you to call `GetHomeRegion` at least once before you call any other API, to obtain the account's Migration Hub home Region. Calls originating from outside your home Region are rejected. ## Prerequisites To perform the steps in this getting-started section, you must first ensure the following: + You have signed up for AWS. For more information, see [Setting up AWS Migration Hub](setting-up.md). + You have selected your Migration Hub home Region. For information, see [Managing your AWS Migration Hub home Region](home-region.md). Here's what to expect: + Migration Hub monitors the status of your migrations in all AWS Regions, provided that your migration tools are available in each Region. + The migration status of every AWS Region undergoing migration is shown in your home Region console. + The migration tools that integrate with Migration Hub store all data about your migration status in Migration Hub. The data is stored in your selected home Region. + The migration tools do not send a status unless you have authorized their connection. + For a list of AWS Regions where you can use Migration Hub, see the [Amazon Web Services General Reference](https://docs.aws.amazon.com/general/latest/gr/rande.html#migrationhub_region). + For more information about working with your home Region, see the section about [Managing your AWS Migration Hub home Region](home-region.md). ## Access to AWS Migration Hub AWS Migration Hub tracks the status of application migrations on the AWS Migration Hub console in your home Region. The Getting Started section and other sections of this guide use the console to illustrate migration functionality. Open the AWS Migration Hub console at [https://console.aws.amazon.com/migrationhub/](https://console.aws.amazon.com/migrationhub/). Additionally, you can use the AWS Migration Hub API to track the status of your migrations from other tools, or to send custom migration status to AWS Migration Hub. For more information about the Migration Hub API, see [AWS Migration Hub API](api-reference.md). You'll also need to call the `GetHomeRegion` API from the Migration Hub [home region API](https://docs.aws.amazon.com//migrationhub-home-region/latest/APIReference/Welcome.html) when working with Migration Hub programmatically. The AWS SDKs assist you to develop applications that interact with Migration Hub. The AWS SDKs for Java, .NET, and PHP wrap the underlying Migration Hub API to simplify your programming tasks. For information about downloading the SDK libraries, see [Sample Code Libraries](http://aws.amazon.com/code). **Topics** # Discover on-premises resources using AWS Migration Hub discovery tools Discover AWS Migration Hub (Migration Hub) provides a single place to discover your existing servers, plan migrations, and track the status of each application migration. Before migrating you can discover information about your on-premises server and application resources to help you build a business case for migrating or to build a migration plan. Discovering your servers first is an optional starting point for migrations, gathering detailed server information, and then grouping the discovered servers into applications to be migrated and tracked. Migration Hub also gives you the choice to start migrating right away and to group servers during migration. You get the data about your servers and applications into the AWS Migration Hub console by using the following discovery tools. + **Application Discovery Service Agentless Collector** – Agentless Collector is an on-premises application that collects information through agentless methods about your on-premises environment, including server profile information (for example, OS, number of CPUs, amount of RAM), database metadata (for example, version, edition, numbers of tables and schemas), and server utilization metrics. You install the Agentless Collector as a virtual machine (VM) in your VMware vCenter Server environment using an Open Virtualization Archive (OVA) file. For more information, see [Agentless Collector](https://docs.aws.amazon.com/application-discovery/latest/userguide/agentless-collector-gs.html) in the *Application Discovery Service User Guide*. + **AWS Application Discovery Agent** – The Discovery Agent is AWS software that you install on your on-premises servers and VMs to capture system configuration, system performance, running processes, and details of the network connections between systems. Agents support most Linux and Windows operating systems, and you can deploy them on physical on-premises servers, Amazon EC2 instances, and virtual machines. For more information, see [AWS Application Discovery Agent](https://docs.aws.amazon.com/application-discovery/latest/userguide/discovery-agent.html) in the *Application Discovery Service User Guide*. + **Migration Evaluator Collector** – Migration Evaluator is a migration assessment service that helps you create a directional business case for AWS cloud planning and migration. The information that the Migration Evaluator collects includes server profile information (for example, OS, number of CPUs, amount of RAM), SQL Server metadata (for example, version and edition), utilization metrics, and network connections. For more information, see [Migration Evaluator](https://aws.amazon.com/migration-evaluator/). + **Migration Hub import** – With Migration Hub import, you can import information about your on-premises servers and applications into Migration Hub, including server specifications and utilization data. You can also use this data to track the status of application migrations. For more information, see [Migration Hub import](https://docs.aws.amazon.com/application-discovery/latest/userguide/discovery-import.html) in the *Application Discovery Service User Guide*. **Topics** + [ ## Step 1: Choose an AWS discovery tool ](#gs-discovery-tools) + [ ## Step 2: View server details and dependencies ](#gs-discovery-view-servers) + [ ## Step 3: Group servers as applications ](#gs-discovery-group-as-applications) ## Step 1: Choose an AWS discovery tool Step 1: Choose a discovery tool You get the data about your servers and applications into the AWS Migration Hub console by using the AWS discovery tools. **To use the discovery tools** 1. In the Migration Hub console navigation pane, choose **Discover** and then choose **Tools**. 1. On the **Discovery Tools** page, you can choose to import data, download the Agentless Collector or a Discovery Agent, or you can choose to use the Migration Evaluator Collector. To help you decide which tool to use, choose **Compare AWS discovery tools**. The following topics provide information about how to use each of the discovery tools: + [Discovery using Agentless Collector](#gs-agentless-collector) + [Discovery using the AWS Application Discovery Agent](#gs-discovery-agent) + [Discovery using Migration Evaluator Collector](#gs-me-collector) + [Using Migration Hub import](#gs-import) ### Discovery using Agentless Collector Agentless Collector The following procedure describes the discovery process using Agentless Collector for collecting data about your on-premises resources. **To discover resources using the Agentless Collector** 1. In the Migration Hub console navigation pane, under **Discover**, choose **Tools**, and then choose **Download collector** on the **Agentless Collector** card. 1. Following the instructions in [Getting started with Agentless Collector](https://docs.aws.amazon.com/application-discovery/latest/userguide/agentless-collector-gs.html) in the *Application Discovery Service User Guide*. ### Discovery using the AWS Application Discovery Agent AWS Application Discovery Agent The following procedure describes the discovery process for collecting data about your on-premises resources using an AWS Application Discovery Agent. You can install Discovery Agent agents on both your VMs and physical servers to not only discover your on-premises servers, but also to capture technical specifications, system performance, network dependencies, and to process information. Network dependency and process information is available, but only for export. Use the Application Discovery Service CLI to export the data and analyze it outside of the Migration Hub. For more information, see [describe-export-tasks](http://docs.aws.amazon.com/cli/latest/reference/discovery/describe-export-tasks.html). The benefit of using Discovery Agent is that it provides more detailed information than using Application Discovery Service Agentless Collector(Agentless Collector). This information includes system performance and resource utilization. By contrast, the benefit of using Agentless Collector is that it provides a more efficient and faster on-premises infrastructure assessment. **To discover resources using an agent** 1. In the Migration Hub console navigation pane, under **Discover**, choose **Tools**, and then choose **Download agent** on the **AWS Discovery Agent** card. 1. In the **Download agent** dropdown list, choose one of the download options. 1. Deploy and configure the agent by following the instructions in [AWS Application Discovery Agent](https://docs.aws.amazon.com/application-discovery/latest/userguide/discovery-agent.html) in the *AWS Application Discovery Service User Guide*. 1. After you have successfully installed the agent, return to the in the Migration Hub console navigation pane, under **Discover** choose **Data Collectors**. Then, refresh your internet browser. 1. On the **Agents** tab, select the agent(s) that you want to start. 1. Choose **Start data collection**. To install additional agents, repeat the procedure. ### Discovery using Migration Evaluator Collector Migration Evaluator Collector The following procedure describes the discovery process using Migration Evaluator Collector for collecting data about your on-premises resources. **To discover resources using Migration Evaluator Collector** 1. In the Migration Hub console navigation pane, under **Discover**, choose **Tools**, and then choose **Request assessment** on the **Migration Evaluator Collector** card. 1. Following the instructions in [Getting started with Migration Evaluator](https://aws.amazon.com/migration-evaluator/getting-started/). ### Using Migration Hub import Import If you have already performed discovery using an AWS Migration Partner discovery tool or have existing data from data sources such as a Configuration Management Database (CMDB) or IT Asset Management System (ITAM), you can use Migration Hub import to upload this data. For more information, see [Migration Hub Import](https://docs.aws.amazon.com/application-discovery/latest/userguide/discovery-import.html) in the *Application Discovery Service User Guide*. ## Step 2: View server details and dependencies Step 2: View server details The following procedures describe how to view detailed information about servers discovered with AWS discovery tools. ### Viewing server details Server details The following procedure describes how to view information about the servers discovered by using any of the AWS discovery tools. **To view details about a discovered server** 1. In the navigation pane, under **Discover**, choose **Servers**. 1. To view details about the server, choose the hostname of the server from the **Server info** column. The server's detail page displays information about the server, such as hostname, IP address, performance metrics, and so on. ### Exploring server network connections Exploring network connections If you use AWS Application Discovery Agent or Migration Evaluator Collector for discovery, you can explore server network connections by using the network diagram in AWS Migration Hub. Start exploring by choosing a single server or by choosing multiple servers at the same time. Use the network diagram to explore your discovered servers and their connections to help you decide on how to group them together to assist in your migration planning. **To explore network connections starting with a single server** 1. In the navigation pane, under **Discover**, choose **Servers**. 1. To view details about the server, choose the hostname of the server from the **Server info** column. The server's detail page displays information about the server, such as hostname, IP address, performance metrics, and so on. 1. Choose **Network**. The icon for the server you choose is centered in the network diagram. Connections fan out from the center server to servers that are directly connected to the server you choose. 1. Choose a server icon to see details about the server. For information about how to work with the network diagram, see [Viewing network connections in AWS Migration Hub](network-diagram.md). **To explore network connections starting with multiple servers** 1. In the navigation pane, under **Discover**, choose **Servers**. 1. To see the network connections for multiple servers, select the check box for each of the servers you want in the network diagram, and then choose **Visualize network**. 1. You can modify the network diagram for the servers you chose. For information on how to work with the network diagram, see [Viewing network connections in AWS Migration Hub](network-diagram.md). ## Step 3: Group servers as applications Step 3: Group servers The following procedures describe how to group servers as applications. Because applications can have multiple servers, it can help simplify migration tracking to group them into logical units. ### Grouping servers as applications from the servers list The following procedure shows you how to select the servers you want to group for your application, how to create your application and name it, and how to add identifying tags. **Tip** You can import application groups in bulk using the AWS CLI for Application Discovery Service and calling the `CreateApplication` API. For more information, see [CreateApplication](http://docs.aws.amazon.com/application-discovery/latest/APIReference/API_CreateApplication.html) in the *Application Discovery Service API Reference*. **To group servers into a new or existing application from the servers list** 1. In the navigation pane, choose **Servers**. 1. In the servers list, select the check box for each of the servers that you want to group into a new or existing application. 1. You can also search and filter on any of the criteria specified in the headers of the server list. In the search box choose an item from the dropdown, then choose an operator from the next dropdown, and then type in your criteria. 1. Optionally, for each selected server, you can add a descriptive tag by choosing **Add tag** from the **Actions ** menu. Doing so shows a dialog box where you can type a value for **Key**, and optionally a value for **Value**. 1. To create your application, or add to an existing one, choose **Group as application**. 1. In the **Group as application** dialog box, choose either **Group as a new application** or **Add to an existing application**. 1. If you chose **Group as a new application**, type a name in the **Application name** field. Optionally, you can type a description in the **Application description** field. 1. If you chose **Add to an existing application**, choose an application from the **Choose existing application** dropdown menu. 1. Choose **Group**. ### Grouping servers as applications from the network diagram You must select the servers in the network diagram that you want to group into a new or existing application. The following procedure shows you how to select the servers you want to group for your application from the network diagram, how to create your application and name it, and how to add identifying tags. **To group servers into a new or existing application from the network diagram** 1. Set up a network diagram following one of the procedures in the [Exploring server network connections](#gs-discovery-view-servers-network) section. 1. You can use the following options to select servers from the network diagram: + Choose a server node icon. Details about the server show in the server details pane, where you choose **Select server**. + Open the context (right-click) menu on the server node icon, and then choose **Select server**. + Choose **Select all** to select all the servers for grouping that are in your diagram. Only the servers with the Discovery Agent running on them or are being monitored by the Migration Evaluator Collector can be selected. + Hold **shift** to select multiple servers at the same time. Selected servers are shown in a list in the same pane as the server details. You can toggle back and forth between the server details view and the selected server list view by choosing the server icon. 1. After you select one or more servers, create your application, or add to an existing one, by choosing **Group as application**. 1. In the **Group as application** dialog box, choose either **Group as a new application** or **Add to an existing application**. 1. If you chose **Group as a new application**, type a name in the **Application name** field. The servers that are members of the group are labeled on the diagram with the application name. Optionally, you can type a description for **Application description**. 1. If you chose **Add to an existing application**, choose an application from the **Choose existing application** dropdown menu. 1. Choose **Group**. 1. Optionally, you can add a descriptive tag to the selected servers by choosing **Add tag** from the **Actions** menu. Doing so shows a dialog box where you can type a value for **Key**, and optionally a value for **Value**. # Migrate to AWS by using AWS Migration Hub migration tools and tracking Migrate You can start migrating with or without first using the AWS Migration Hub discovery tools. Directly migrating servers is efficient because your servers are migrating while you simultaneously group them into applications. Remember that if you haven't selected a Migration Hub home Region, the first time you view the console, you'll be required to select one. It is important to understand that connecting a migration tool to Migration Hub is how you authorize that tool to communicate migration status to Migration Hub in your home Region. Without this authorization, Migration Hub will not track your migration. As you perform the migration, the servers you are migrating appear in the **Servers** page. On this page you can logically define and group all the servers that comprise the applications you are migrating. You can also group more servers into either an existing or a new application at a later time. To get to the **Servers** page, in the Migration Hub console navigation pane, under **Discover**, choose **Servers**. The following steps show how to use the Migration Hub to migrate your on-premises servers and application resources to AWS. **Topics** + [ ## Step 1: Connect migration tools to Migration Hub ](#migrate-wt-auth-migrate-tools) + [ ## Step 2: Migrate using the connected migration tools ](#migrate-wt-migrate-using-tools) + [ ## Step 3: Group servers as applications ](#migrate-wt-group-as-applications) ## Step 1: Connect migration tools to Migration Hub Step 1: Connect migration tools Migration happens outside AWS Migration Hub using AWS migration tools. To access these tools, in the Migration Hub console navigation pane under **Migrate**, choose **Tools**. The table following lists the supported tools. | Resource type | Migration tool | | --- | --- | | Server | **AWS Application Migration Service (Application Migration Service)**–AWS Application Migration Service is the primary migration service recommended for lift-and-shift migrations to AWS. For more information about Application Migration Service, see [AWS Application Migration Service](https://aws.amazon.com/application-migration-service/) and [Application Migration Service Documentation](https://docs.aws.amazon.com/mgn/index.html ). | | Database | **AWS Database Migration Service (AWS DMS)**–For more information about AWS DMS, see [AWS Database Migration Service](https://aws.amazon.com/dms/) and [AWS DMS Documentation](https://docs.aws.amazon.com/dms/index.html). | The preceding tools communicate directly to Migration Hub giving an aggregated view of their migrated progress and status so they can be tracked through Migration Hub. The following steps walk you through connecting (authorizing) your selected migration tool. **To connect (authorize) a migration tool** 1. In the Migration Hub console navigation pane under **Migrate**, choose **Tools**. 1. Decide upon which AWS migration tool to use to migrate your application. 1. Choose **Connect** in the box to authorize the migration tool you selected to communicate with Migration Hub. AWS migration tools utilize a one-click authorization process that automatically adds the required AWS Identity and Access Management (IAM) permissions role once you choose **Connect**. **Note** Note that if you are using API's or do not want to authorize through Migration Hub's console, you can learn about manual role creation in [New user IAM setup for AWS Migration Hub](new-customer-setup.md). ## Step 2: Migrate using the connected migration tools Step 2: Migrate using the connected migration tools The following steps walk you through the migration of a previously defined application. **To migrate an application** 1. In the Migration Hub console navigation pane under **Migrate**, choose **Tools**. 1. After you connect (authorize) an AWS migration tool, choose the console link for the tool. 1. After you link to the tool's console, follow the migration instructions for your selected migration tool as migration happens outside of Migration Hub. 1. After your application's migration has started, return to the Migration Hub console. ## Step 3: Group servers as applications Step 3: Group servers as applications The following steps walk you through the process of grouping servers as applications when directly migrating with a migration tool without performing discovery first. (You already did this, if you first performed discovery as described in [Discover on-premises resources using AWS Migration Hub discovery tools](gs-new-user-discovery.md) before migrating.) After the migration tool has started, you'll see the servers listed in Migration Hub from the migration updates sent from the migration tool. You can select the servers and group them as applications. Keep in mind that the server information communicated to Migration Hub from the migration tool is not as detailed as what is collected from a discovery tool. The following steps show you how to select the server or servers you want to group for your application, how to create your application and name it, and how to add identifying tags. **To group servers into a new or existing application** 1. In the Migration Hub console navigation pane, under **Discover**, choose **Servers**. 1. In the severs list, select each of the servers that you want to group into a new or existing application. 1. You can also search and filter on any of the criteria specified in the headers of the server list. Click inside the search bar and choose an item from the dropdown, then choose an operator from the next dropdown, and then type in your criteria. 1. Optionally, for each selected server, you can add a descriptive tag by choosing **Add tag**. A dialog box appears where you can type a value for **Key**, and optionally, a value for **Value**. 1. Create your application, or add to an existing one, by choosing **Group as application**. 1. In the **Group as application** dialog box, select either **Group as a new application** or **Add to an existing application**. 1. If you chose **Group as a new application**, type a name for **Application name**. Optionally, you can type a description for **Application description**. 1. If you chose **Add to an existing application**, select the radio button next to the application name in the list box. 1. Choose **Save**. A green confirmation message appears at the top of the screen. **Next steps** After you complete the migration steps, proceed to + [Track the status of your migrations in AWS Migration Hub](migrate-wt-track.md) # Track the status of your migrations in AWS Migration Hub Track With a migration underway, you can track its progress status as well as details for each server grouped to the application. This status is communicated to AWS Migration Hub from the migration tool at key points during the migration. **To track an application's migration status** 1. After your application's migration has started, return to Migration Hub console and then choose **Dashboard** in the navigation pane. 1. Under **Most recently updated applications**, choose the name of your migrating application. Doing this displays the application's detail screen. 1. If you do not see all of your application's servers listed in the application's details page, it could be because you have not grouped those servers into this application yet. See [Updates about my migrations don't appear inside an application](troubleshooting.md#migs-do-not-appear-in-app). 1. The first time a migration task is started for a server associated with the application, applications with this server will change to the **In progress** status, automatically. After verifying the in-progress migration status from the application's detail screen, if the status is still **Not started**, you can manually change it to **In progress**. To change the status, choose **In progress** from the **Update status** menu. 1. Choose **Confirm**. A green confirmation message appears at the top of the screen, and the status label changes to **In progress**. 1. When the data in the application's detail screen indicates migration has completed, and you've performed testing and verification, change the status from **In progress** to **Completed** from the **Update status** menu. 1. Choose **Confirm**. A green confirmation message appears at the top of the screen, and the status label changes to **Completed**.