Migrating the bot process configuration in RPA Hub

  • Release version: Zurich
  • Updated July 31, 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 you to migrate bot process configurations and their associated assets between environments, such as from development to UAT or production. This capability supports the automation lifecycle by allowing you to create and test automations in lower environments and then move them securely and efficiently to higher environments.

    Show full answer Show less

    Migration Workflow

    • An RPA developer or administrator marks a published bot process as "Ready for Migration," which activates the Migrate button (visible only when no migration is in progress).
    • An RPA release manager or administrator initiates the migration by clicking the Migrate button.
    • After migration, the release manager can adjust settings in the target environment, such as process parameters, credential mappings, and publish the bot process.

    What is Migrated

    The migration process transfers the following based on bot type:

    • Unattended bots: Bot process configuration, packages and their versions with attachments, process parameters including shared parameters if assigned, schedules, queues, and associated skills.
    • Attended bots: All unattended bot assets plus process field parameters, attended configurations if Embedded Task Automation (ETA) is enabled, queues, and associated skills.

    What is Not Migrated

    • Robot credentials, application credentials, and credential groups linked to the bot process must be recreated or updated manually in the target environment.
    • Sensitive parameter values (marked sensitive in shared or process parameters) are not migrated and appear empty; only default values transfer.
    • Custom field values do not migrate; only default field values are preserved.

    Additional Considerations

    For customers using Tokyo or earlier releases, RPA Hub tables must be restructured before migration to ensure compatibility.

    Practical Benefits for ServiceNow Customers

    • Facilitates seamless promotion of tested automations across environments, reducing manual efforts and errors.
    • Provides clear roles and actions for developers, administrators, and release managers during migration.
    • Ensures bot configurations and assets are consistently moved while maintaining security by requiring credential setup in target environments.

    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.