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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Migrating the bot process configuration

# Migrating the bot process configuration in RPA Hub {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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.

## Bot process migration overview {#bot-process-migration__section_p1s_nfg_1cc}

You can migrate the bot processes from any environment to any environment. For example, when a bot process is ready to be migrated from a developer's environment to a UAT environment, an RPA developer or RPA administrator can
select the Ready for Migration button on a published bot process. This action enables the Migrate button to appear. This button is only visible when the bot process migration isn't in
progress. Then, an RPA release manager or RPA administrator can initiate the migration process by selecting the Migrate button. After the bot process and associated assets are migrated, a release manager can
make any necessary changes (such as creating more process parameters, shared parameters, or credential mapping), create and associate credentials, create an associated bot process record, and publish the bot process on the UAT
(target) environment.

## What's migrated with the bot process {#bot-process-migration__section_mjw_sgg_1cc}

In an unattended bot process migration, the following records and associated assets are also migrated:

* Bot process configuration
* Packages
* Package versions with attachments
* Process parameters
* Shared process parameters, if assigned to the bot process
* Schedules
* Queues
* Associated skills  
  Note:  
  Only skills that are directly used in the automation are migrated.
{#bot-process-migration__ul_kx2_21w_4bc}

In an attended bot process migration, the following records and associated assets are also migrated:

* Bot process configuration
* Packages
* Package versions with attachments
* Process parameters
* Shared process parameters, if assigned to the bot process
* Process field parameters, if Embedded Task Automation (ETA) is enabled
* Attended configurations, if ETA is enabled
* Queues
* Associated skills  
  Note:  
  Only skills that are directly used in the automation are migrated.
{#bot-process-migration__ul_bpc_fmv_4bc}

## What's not migrated with the bot process {#bot-process-migration__section_cgf_shg_1cc}

The robot credentials, application credentials, and credential group that are associated with the bot process configuration aren't migrated. After the bot process configuration is migrated, the credentials must be created or
updated in the target environment.

If any shared parameters or process parameters are marked as sensitive in the bot process, the sensitive values that are stored in these parameters aren't migrated and the parameter values are empty in the target environment.

Only the default field values are migrated. The custom field values aren't migrated.

## Restructured RPA Hub tables (Tokyo and earlier releases) {#bot-process-migration__section_ess_pcd_svb}

For Tokyo and earlier releases, you must restructure the RPA Hub tables before migration. For more information, see [Restructuring RPA Hub tables](https://www.servicenow.com/docs/UbwR7ITl88nU7wy9vbSmQg "Starting with the Utah release, the Robotic Process Automation (RPA) tables are restructured to an application file, so that changes that you make to these tables are captured in the update sets and can be moved seamlessly across environments. With this process, you don't have to re-create the data records in the targeted environment.").
* **[Mark the bot process as ready for migration in RPA Hub](https://www.servicenow.com/docs/Gy5~~2GFfnF7dA50xS~4XQ)**   
  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.
* **[Migrate the bot process configuration to another environment in RPA Hub](https://www.servicenow.com/docs/L_bdH6wUxr2hSRqi_hZ2bQ)**   
  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.

**Related tasks**   

* [Mark the bot process as ready for migration in RPA Hub](https://www.servicenow.com/docs/Gy5~~2GFfnF7dA50xS~4XQ "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.")
* [Migrate the bot process configuration to another environment in RPA Hub](https://www.servicenow.com/docs/L_bdH6wUxr2hSRqi_hZ2bQ "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.")