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). # Migration journeys Migration journeys A migration journey is an Amazon resource that you create and use to plan, organize, and track the migration of your solutions to AWS. A journey consists of phases that represent the main stages of a migration. Each phase consists of modules, which in turn consist of discrete tasks. **Topics** + [ # Creating a journey ](journey-creation.md) + [ # Journey status ](journey-status.md) + [ # Copying a journey ](journey-copy.md) + [ # Updating a journey ](journey-updates.md) + [ # Transferring a journey ](journey-transfers.md) + [ # Individuals and teams ](individuals-and-teams.md) + [ # Attached files ](attached-files.md) + [ # Customizing your journey ](customization.md) # Creating a journey Migration Hub Journeys provides templates that you can use to create your migration journey. These templates represent common migration scenarios and follow best practices. When you create a journey from a template, you get a journey with predefined phases, modules, tasks, and subtasks. If you have a migration scenario that doesn't match any of the available templates, you can create a custom journey. In this case, you get an empty journey to which you add the phases, modules, tasks, and subtasks that you need for your migration. Whether you use a template or create a custom journey, you can edit the structure and details of the journey at any time. **To create a migration journey from a template** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. Choose **Create migration journey**. 1. Choose the template that you want to use for the journey. 1. In the **Journey creation method** section, keep the default option. 1. In the **Journey details** tile, enter a name for the journey. The description and completion date fields are optional. If you leave them blank, you can specify them after you create the journey. 1. Choose the migration space in which you want to put the journey. Alternatively, you can enter a name for a new migration space, and then choose **Create migration space**. 1. Choose **Create migration journey**. **To create a custom migration journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. Choose **Create migration journey**. 1. In the **Journey creation method** section, choose **Create custom journey**. 1. In the **Journey details** section, enter a name for the journey. The description and completion date fields are optional. If you leave them blank, you can specify them after you create the journey. 1. Choose the migration space in which you want to put the journey. Alternatively, you can enter a name for a new migration space, and then choose **Create migration space**. 1. In the **Create phases** section, you can specify the phases that you want your journey to have. However, you are not required to specify any phases while creating the journey. You can add and remove phases after you create the journey. To specify a phase, enter a name and an optional description for it. To add a second phase, choose **Add phase**. 1. Choose **Create migration journey**. # Journey status A migration journey can have any of the status values that appear in the following table. For information about how to change the status of a journey, see [Updating a journey](journey-updates.md). **** | Status | Meaning | | --- | --- | | Creating | The service is creating the journey. You cannot perform any actions on the journey until the create operation is complete. | | Copying | The service is copying the journey. You cannot perform any actions on the journey until the copy operation is complete. | | Copy failed | There was an error that prevented the successful creation of the journey. If you see this status, delete the journey. | | Deleting | The service is deleting the journey. You cannot perform any actions on a journey that is in this state. | | Not started | This is the initial status of a migration journey after you create the journey. | | In progress | This status means that journey members have started working on the journey. | | Completed | This status marks the journey as complete. | | Transfer initiated | A journey member has initiated a transfer, but the invitee hasn't received the invitation yet. | | Transfer pending | An individual has received a journey-ownership-transfer invitation, but has neither accepted nor declined it yet. | | Transfer cancelled | A journey member has cancelled a pending ownership-transfer invitation. | | Transferring | The recipient of a journey-ownership-transfer invitation has accepted the invitation, and the service is in the process of transferring the ownership. You cannot perform any actions on the journey until the transfer is complete. | | Transfer declined | The recipient of a journey-ownership-transfer invitation has declined the invitation. | | Transfer failed | The recipient of a journey-ownership-transfer invitation accepted the invitation, but then the transfer failed due to an internal issue. | # Copying a journey The following procedure describes how to create a copy of a migration journey. The copy that you create will have the same phases, modules, tasks, subtasks, task dependencies, acceptance criteria, and tools as the original journey. In the copy, all the phases and modules will be in scope and the status of all the tasks will be `Planned`. Attachments, assignees, and comments won't be included in the copy. 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to copy. 1. Choose **Actions**, then choose **Copy journey**. 1. Specify a different name for the copy if you don't want it to have the name that Migration Hub Journeys suggests. 1. You can optionally specify a description and a completion date for the copy. 1. Specify the migration space in which you want to place the copy. You can choose an existing migration space or create a new one. 1. Choose **Copy**. # Updating a journey The following procedure describes how to update the status, description, and completion date of a migration journey. 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to update. 1. Choose **Actions**, then choose **Edit journey details**. 1. Specify new values for the fields that you want to change, and then choose **Update**. For information about how to update the phases of a journey, see [Phases](phases.md). For information about how to update the tasks of a journey, see [Migration Hub Journeys tasks and subtasks](tasks.md). # Transferring a journey After you create a migration journey, you can send a request to transfer the journey to another individual. If that individual accepts the transfer, they can move the journey to another migration space where they have the `MigrationSpaceAdmin` role. That individual then becomes a `JourneyAdmin` for that journey. For information about roles, see [Roles and permissions](permissions.md). **To transfer a journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to transfer. 1. Choose **Actions**, then choose **Transfer journey ownership**. 1. Enter the email address of the person to whom you want to transfer the journey, and then choose **Transfer**. 1. Notify the individual to whom you sent the transfer request that they will receive an email from the following address: `no-reply@es.prod.reg.service.migrationhub.aws`, where *reg* is your AWS Region. The body of the email will have a **Respond** button that they can use to accept or reject the transfer. In addition to the invitation email, the individual can also go to **Pending actions** in the navigation pane to see the transfer request that you sent them, and to accept it or reject it. For more information, see [Pending actions](pending-actions.md). **Important** For the transfer to take effect, the individual to whom you sent the transfer request must accept that request. To accept the request, they can choose **Respond** in the transfer email, or they can go directly to **Pending actions** in the Migration Hub Journeys console. For more information, see [Pending actions](pending-actions.md). # Individuals and teams A migration journey can have two types of members: individuals and teams. A member, whether an individual or a team, can have one of two roles in a journey: `JourneyAdmin` or `JourneyContributor`. For information about these two roles and the actions that they allow a journey member to perform, see [Roles and permissions](permissions.md). **To view the individuals and teams that are members of a migration journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey whose members you want to view. 1. Choose the **Individuals and teams** tab. For information about how to invite an individual or a team to become a member of a journey, and how to grant the `JourneyAdmin` role or the `JourneyContributor` role to a new or existing journey member, see [JourneyAdmin](roles.md#journey-admin) and [JourneyContributor](roles.md#journey-contributor). # Attached files You can attach files to tasks and subtasks. For example, you can attach analysis reports that help in completing the task. You can also attach files that contain results from the task. The following file extensions are supported: CSV, PDF, DOCX, DOC, PPT, PPTX, TXT, JPEG, and PNG. **To view all the files that are attached to a migration journey** This procedure explains how to view all the files that are attached to tasks and subtasks in a journey. 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey whose attachments you want to view. 1. Choose the **Attached files** tab. **To attach a file to a task** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that contains the task where you want to attach the file. 1. Choose the **Tasks** tab. 1. Choose the tile that represents the task where you want to attach the file. 1. Scroll down and choose the **Attached files** tab. 1. Choose **Choose file**. **To attach a file to a subtask** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that contains the subtask where you want to attach the file. 1. Choose the **Tasks** tab. 1. Choose the tile that represents the task that contains the subtask where you want to attach the file. 1. Scroll down and choose the **Subtasks** tab. 1. Choose the name of the subtask where you want to attach the file. 1. Scroll down and choose the **Attached files** tab. 1. Choose **Choose file**. # Customizing your journey When you create a journey from a template, you can customize the journey to make it match your particular migration scenario more closely. To help you fine-tune your journey, Migration Hub Journeys includes a customization tool that asks you questions about your migration scenario, and then, based on your answers, moves the parts of the journey that don't apply to your scenario out of scope. This customization feature works for certain templates. For other templates, it is grayed out. For a list of templates that support this customization feature, see [AWS templates](aws-templates.md). **Note** If you create a journey from a template that doesn't support this questionnaire-based customization feature, you can still customize your journey manually by editing its modules, phases, and tasks. **To customize the phases of your journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to customize. 1. Choose the **Phases** tab. 1. Choose **Customize**. 1. Answer the questions that appear in the right panel, then choose **Apply**. Based on the answers you provided, Migration Hub Journeys moves phases that don't apply to your migration scenario out of scope. 1. When you see a message stating that the customization was successful, choose **Exit**. **To customize the modules of your journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to customize. 1. Choose the **Modules** tab. 1. Choose **Customize**. 1. Answer the questions that appear in the right panel, then choose **Apply**. Based on the answers you provided, Migration Hub Journeys moves modules that don't apply to your migration scenario out of scope. 1. When you see a message stating that the customization was successful, choose **Exit**. **To customize the tasks within a module** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that you want to customize. 1. Choose the **Modules** tab. 1. Choose the module that you want to customize. 1. In the **Tasks** section, choose **Customize**. 1. Answer the questions that appear in the right panel, then choose **Apply**. Based on the answers you provided, Migration Hub Journeys moves tasks that don't apply to your migration scenario out of scope. 1. When you see a message stating that the customization was successful, choose **Exit**.