---
sourceDocument: Xanadu Create Integrations with Applications
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/integrate-applications

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Create Integrations with Applications

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Migrate the bot process configuration to another environment

# Migrate the bot process configuration to another environment {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Migrate the bot process configuration and associated assets to another environment in RPA Hub. 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/_gvANcYTusUht07YvWJSgg "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/xcmEuzHFsP8LDB6gpk2SLA#setup-rem-instance "Integrate the local and remote ServiceNow instances by creating an OAuth API endpoint in the remote ServiceNow instance to authenticate requests.").

The bot process must be marked ready for migration. For more information, see [Mark the bot process as ready for migration](https://www.servicenow.com/docs/PUTGUXWChi~QqD8Bpxw4iA "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.").

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 of a bot process in RPA Hub](https://www.servicenow.com/docs/joZ5FFVApqpa2_ZTs_ED_Q "The State transition of a bot process guides you through the stages of its life cycle.").

When you re-migrate, verify that the life-cycle stage status of the bot process in the target environment isn't set to Published or Retired. If Published,
the values are overridden in the target environment.

Role required: sn_rpa_fdn.rpa_release_manager 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 migrate.
5. In the form header, select Migrate.  
   You can't see the Migrate button when the bot process migration is in progress.
6. In the Confirmation dialog box, select Migrate.
{#migrate-bot-process__steps_jl4_zlv_4bc}

## Result

After the migration is completed successfully or if an error occurs, an email notification is sent to the user who performs the migration. To receive the email notification, the email address of the user must be added to the
user profile.

## What to do next

* [Associate a bot process to a bot process configuration record](https://www.servicenow.com/docs/zk0ZY~yQ38bRyqDA~3wFHA "Select a bot process configuration record to associate it with a bot process. This action creates a bot process record in RPA Hub.")
* [Configuring credentials in RPA Hub](https://www.servicenow.com/docs/ZobTtuhByvdUkSWd6Ap_PQ "In RPA Hub, you can create application credentials, robot credentials, and Time-based One-time Password (TOTP) authentications and link them to multiple bot processes through a credential group. Set up external credential vault to retrieve robot credentials, application credentials, or Time-based One-time Password (TOTP) seed.")
* [Adding details for your bot process in RPA Hub](https://www.servicenow.com/docs/9Nj2r2h4T1himDaT1sqiXQ "After you create a bot process in RPA Hub, you can add some details for your bot process, such as information about the credential groups, business applications, and more.")
* [Publish an RPA Hub bot process](https://www.servicenow.com/docs/lTlml8MN74ZfS_8YBCOSZw "Publish a bot process so that you can get it ready to execute a process.")
{#migrate-bot-process__ul_uz4_z3l_zbc}

*[\>]: and then