---
sourceDocument: Yokohama Data and Automation
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/integrate-applications

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Data and Automation

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Migrating your data from a lower environment to a higher environment in RPA Hub

# Migrating your data from a lower environment to a higher environment in RPA Hub {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

As a system administrator, after you restructure the RPA Hub tables to extend the Application file (sys_metadata), you can use the update set capability to migrate your data from a lower (non-production) environment to a higher (production) environment for real-time
use.  
There are two ways you can migrate your data from a lower environment to a higher environment:

* Using the update set capability described in this page for migrating your data from one environment to another environment
* Using the Migrate button in RPA Hub

  In RPA Hub, you can migrate the bot process configuration and associated assets from one environment to another environment with a click of a button. After the migration is complete, you will have to create
  a bot process record, create credentials, make necessary changes, and then publish the bot process. For more information, see [Migrating the bot process configuration in RPA Hub](https://www.servicenow.com/docs/CI8q3qOMWQTAOH45__yVhw "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.").
{#migrate-data-rpa-hub__ul_ilf_frl_zbc}

## Restructured RPA Hub tables (Tokyo and earlier releases) {#migrate-data-rpa-hub__section_ess_pcd_svb}

For more information about the restructuring of the RPA Hub tables, see
[Restructuring RPA Hub tables](https://www.servicenow.com/docs/thdHpbThAIbIEd3YnlS9Tw "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.").

For more information about update sets, see [Get started with update
sets](https://www.servicenow.com/docs/access?context=get-started-update-sets&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US).

## Functionality {#migrate-data-rpa-hub__section_plp_dh4_ywb}

The metadata of the automation (package, package version, schedules, and so on) is captured in the update set. System administrator then moves the update set to a higher (production) environment.

The metadata records are moved to the higher (production) environment but the package version does not contain an automation zip file.

RPA release manager manually downloads the zip file from the lower (non-production) environment and then uploads it to a higher (production environment). RPA admin can also perform this action. However, this task is restricted
to classic environment.

RPA release manager automatically imports package version attachments by selecting the Import Attachment button on a package version. RPA admin can also perform this action. A flow is then triggered
asynchronously and pulls the attachment from the configured connection using API. The automation zip file is attached to the package version and HashCode validation is performed automatically. An email is also sent to the user
who performs the import attachment action.
To execute the orchestration of RPA Hub update sets from third-party tools, it is essential to recreate bot process on the higher environment. The Change Life Cycle Stage Status of a Bot Process action in Workflow Studio helps in ensuring the deployment and enablement of RPA Hub process is automated. For more information about this action, see [RPA Hub actions and subflow](https://www.servicenow.com/docs/7w_MXXMfclHAAurIqZ2Axw "Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution.").

## List of steps for the migration tasks {#migrate-data-rpa-hub__section_imt_1bb_5vb}

Use this list of steps to guide you through all the tasks of the migration.

Complete all the tasks for a step before moving on to the next step.

Do the steps in the order that they're presented.
{#migrate-data-rpa-hub__table_ar4_w1b_5vb__entry__2}

| Task | Environment |
|-|-|
| 1. [Create and select an update set as the current set](https://www.servicenow.com/docs/access?context=create-select-update-set&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Lower (non-production) environment |
| 2. [Create a bot process configuration record in RPA Hub](https://www.servicenow.com/docs/7Rt4TFi9CLOok~OK5gt4MQ "Create a bot process configuration record in RPA Hub so that you can define the preliminary fields for a bot process record."). | Lower (non-production) environment |
| 3. [Adding details for your bot process in RPA Hub](https://www.servicenow.com/docs/xkcX9FDhLJi~WtAxI5mkLg "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."). | Lower (non-production) environment |
| 4. [Mark your current update set complete](https://www.servicenow.com/docs/access?context=t_CompleteUpdateSets&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Lower (non-production) environment |
| 5. [Export to XML](https://www.servicenow.com/docs/access?context=t_SaveAnUpdateSetAsAnXMLFile&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Lower (non-production) environment |
| 6. [Download a package version in RPA Hub](https://www.servicenow.com/docs/g~qwtsiDV1zeTNhgK2T_7A "Download a package version in RPA Hub so that it can be opened from the RPA Desktop Design Studio to build, debug, or modify the automation."). Perform this task, if you are manually migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment. You can skip step 12. | Lower (non-production) environment |
| 7. Switch to higher instance. [Retrieve an update set](https://www.servicenow.com/docs/access?context=t_RetrieveAnUpdateSet&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Higher (production) environment |
| 8. [Preview a remote update set](https://www.servicenow.com/docs/access?context=t_PreviewARemoteUpdateSet&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Higher (production) environment |
| 9. [Commit an update set](https://www.servicenow.com/docs/access?context=t_CommitAnUpdateSet&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | Higher (production) environment |
| 10. [Associate a bot process to a bot process configuration record](https://www.servicenow.com/docs/e_1T3oFFMPNxeRr2EcUlTg "Select a bot process configuration record to associate it with a bot process. This action creates a bot process record in RPA Hub."). | Higher (production) environment |
| 11. [Verify the associated schedules, parameters, packages, and queues in RPA Hub](https://www.servicenow.com/docs/pcTElziXCGCBF3_Z9ybnxg "Verify that the bot process has the associated schedule, process parameters, shared parameters, package, package version, and work queues in RPA Hub. You do this task when you’re migrating your data from a lower (non-production) environment to a higher (production) environment."). | Higher (production) environment |
| 12. If the instance connection is established with a required lower (non-production) instance, perform this import task. To establish an instance connection, create an active connection in the RPA Automation Package connection and credential alias. Ensure to provide the lower (non-production) environment in the Connection URL field. For more information, see [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US). Perform this task if you are automatically migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment. [Import a package version attachment in RPA Hub](https://www.servicenow.com/docs/8V11lqPNkY~sLqmgGvJxjA "Import package version attachments automatically instead of manually uploading a package version attachment, by selecting the Import Attachment button on a package version."). You can skip step 13 and 14. | Higher (production) environment |
| 13. [Upload an automation package attachment in RPA Hub](https://www.servicenow.com/docs/79cf9v6J7CR4vLm~HYSXvg "Upload a zip file of the automation package in RPA Hub to manually migrate the package from a lower (non-production) to a higher (production) environment."). Perform this task in classic environment. | Higher (production) environment |
| 14. [Verify the HashCode of a package version in RPA Hub](https://www.servicenow.com/docs/WiHS0GyLMLAG570NvxtMYw "Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record."). | Higher (production) environment |
| 15. [Assign a business application with a bot process](https://www.servicenow.com/docs/~dnBo9H5QYtFrLdcH931Aw "Assign a business application to a bot process for an effective event correlation or to get information about assigned business applications. For example, you might want to see information about the SAP application."). | Higher (production) environment |
| 16. [Create a credential group in RPA Hub](https://www.servicenow.com/docs/~6By4qTwtk50o74~4VimnQ#create-credential-group "Create a credential group to include a robot credential and application credentials that you can reuse in multiple bot processes. Unattended robots leverage the credential group to perform an automation that you defined in the associated bot process."). | Higher (production) environment |
| 17. [Assign a robot to a bot process in RPA Hub](https://www.servicenow.com/docs/Mw~LEeTYQ2PDgCjxpAbA4w "Assign a robot to an unattended bot process to execute the automation (package) that is mapped to it."). | Higher (production) environment |
| 18. [Assign a process robot credential within a bot process](https://www.servicenow.com/docs/r5E_aS1FiwBw7ECMQSPcoA "Assign a process robot credential within an unattended bot process so that the selected robot can perform the automation in the Windows machine."). | Higher (production) environment |
| 19. [Assign an attended user or group to an attended bot process](https://www.servicenow.com/docs/rYLYSVuVxzMY030U_Ws9zw "Assign an attended user or group to an attended bot process in RPA Hub, so that your user or group can access and execute this automation on Windows machines."). | Higher (production) environment |
[Table 1. Checklist]

{#migrate-data-rpa-hub__table_ar4_w1b_5vb}