Migrating the bot process configuration in RPA Hub

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Migrating the bot process configuration in RPA Hub

    ServiceNow's RPA Hub enables customers to migrate bot process configurations and associated assets between environments, such as from a development environment to UAT or production. This capability supports the automation lifecycle by allowing bots to be developed and tested in lower environments before deployment to higher environments.

    Show full answer Show less

    Bot Process Migration Workflow

    • An RPA developer or administrator marks a published bot process as Ready for Migration, which then makes the Migrate button visible (only when no migration is in progress).
    • An RPA release manager or administrator initiates migration by selecting the Migrate button.
    • After migration, release managers can perform necessary adjustments in the target environment, such as creating process parameters, mapping credentials, associating bot process records, and publishing the bot process.

    What is Migrated

    The migration process varies slightly depending on whether the bot process is attended or unattended:

    • Unattended bot process migration includes:
      • Bot process configuration
      • Packages and package versions with attachments
      • Process parameters and shared process parameters (if assigned)
      • Schedules and queues
      • Associated skills
    • Attended bot process migration includes all unattended components plus:
      • Process field parameters (if Embedded Task Automation (ETA) is enabled)
      • Attended configurations (if ETA is enabled)

    What is Not Migrated

    • Robot credentials, application credentials, and credential groups linked to the bot process are not migrated. These must be created or updated manually in the target environment.
    • Values marked as sensitive in shared or process parameters are not migrated; only default values are transferred, resulting in empty sensitive fields in the target environment.
    • Custom field values are not migrated; only default field values are preserved.

    Additional Considerations

    • For customers using Tokyo release or earlier, RPA Hub tables must be restructured before migration can occur.
    • Migration can be performed between any environments, supporting flexible deployment workflows.

    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

    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

    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

    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

    What's not migrated with the bot process

    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)

    For Tokyo and earlier releases, you must restructure the RPA Hub tables before migration. For more information, see Restructuring RPA Hub tables.