---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Mark the bot process as ready for migration

# Mark the bot process as ready for migration in RPA Hub {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Mark the bot process as ready for migration in RPA Hub so that the bot process configuration and associated assets can be migrated to another environment. With this feature, you can create an automation and test it in a lower environment and then migrate it to
a higher or production environment.

## Before you begin

Familiarize yourself with the bot process migration concept. For more information, see [Migrating the bot process configuration in RPA Hub](https://www.servicenow.com/docs/EJYNWannHws_aDIDAqOiIg "In RPA Hub, you can migrate the bot process configuration and associated assets for an attended or unattended bot process from one environment to another environment. With this feature, you can create an automation and test it in a lower environment and then migrate it to a higher or production environment.").

Verify that you've completed the tasks that are related to setting up the target environment. For more information, see [Set up the ServiceNow Remote Instance spoke](https://www.servicenow.com/docs/CeroxsMHhgCxKQpMYsGFsw#setup-rem-instance "Integrate the local and remote ServiceNow instances by creating an OAuth API endpoint in the remote ServiceNow instance to authenticate requests.").

Verify that the life-cycle stage status of the bot process in the source environment is set to Published. For more information, see [Life-cycle stage statuses (LLCS) of a bot process in RPA Hub](https://www.servicenow.com/docs/1e7Wk3b~h8Umb9MzJzzgWw "The State transition of a bot process guides you through the stages of its life cycle.").

Verify that the Robotic Process Automation (RPA) developer (sn_rpa_fdn.rpa_developer) is in the Managed by Group list of the bot process.

Role required: sn_rpa_fdn.rpa_developer or sn_rpa_fdn.rpa_admin

## Procedure

1. Navigate to AllRobotic Process AutomationRPA Hub Workspace.
2. Select the list icon (![List icon.]()).
3. On the Lists tab, under Build, select Bot Process.
4. Select the bot process that you want to mark as ready for migration.
5. In the form header, select Ready for Migration.  
   You can't see the Ready for Migration button when the bot process migration is in progress.

*[\>]: and then