RPA Migration Setup and Common IssuesIssue End user wants to migrate an RPA bot process from one ServiceNow instance to another (e.g., Development → UAT → Production) and needs guidance on prerequisites, setup, and how to test it. ReleaseAllResolution1. Prerequisites Before starting, confirm all of the following are in place. Both instances must have: RPA Hub plugin installed and active and their versions should be in sync.Remote Instance Spoke plugin should be available. Roles required on the source instance: ActionRole RequiredClick "Ready for Migration"sn_rpa_fdn.rpa_developer or sn_rpa_fdn.rpa_adminClick "Migrate"sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_adminConfigure the connection aliasadmin or connection_admin Roles required on the destination instance: ActionRole RequiredReceive and publish the migrated bot processsn_rpa_fdn.rpa_admin or sn_rpa_fdn.rpa_release_managerService account used in the connection aliassn_rpa_fdn.rpa_admin (minimum) NOTE: Simply having rpa_developer + rpa_admin is NOT enough to see the "Migrate" button. The rpa_release_manager role is specifically required. This is the most common reason the Migrate button is missing.The bot process must be in Published state on the source instance before migration can be initiated.The Remote Instance Spoke used for migration requires an active IntegrationHub subscription. Contact your ServiceNow Account Manager if this is not available. 2. Setup RPA Migration uses the ServiceNow Remote Instance Spoke to establish a connection between the source and destination instances. This is a one-time setup 📄 Official doc: Migrate the bot process configuration – Zurich 📄 Step 1 – Configure the Remote Instance spoke in source and destination instance Please follow the Remote Instance Spoke setup steps from the KB - KB0951925 Step 2 – Mark the bot process as Ready for Migration On the source instance, go to Robotic Process Automation → Build → Bot Processes. Open the bot process (must be in Published state) and click "Ready for Migration". This makes the Migrate button visible to release managers. Step 3 – Trigger the migration Click "Migrate", select the destination connection created in Step 4, and confirm. The system transfers the bot process along with its packages, parameters, schedules, queues, and associated skills to the destination instance. Step 4 – Post-migration configuration on the destination instance Once we hit 'Migrate' in the source instanceOpen destination instance and go to the List View of 'Bot process'Then hit 'New' on top rightA modal pops up and you can see the Migrated Bot Process, you can then select it and hit 'Submit'.Once done, refresh the list view of the bot process again, you will then be able to view newly migrated 'Test RPA bot process' in list view. What is NOT migrated automatically: Robot records, credential sets, process parameters , queues and VM/machine configurations must be manually reconfigured on the destination instance after migration. Once verified, click Publish on the bot process. 3. Common Issues IssueCauseFix"Ready for Migration" button not visibleBot process is not in Published state, or user lacks rpa_developer / rpa_admin rolePublish the bot process first, then verify roles"Migrate" button not visibleUser does not have rpa_release_manager roleAssign sn_rpa_fdn.rpa_release_manager to the user, or use an rpa_admin account"There is no destination instance defined…" errorRemote Instance Spoke connection alias is not set up or is inactive Complete Step1 in the Setup section aboveBot process migrated but does not executeCredentials not re-mapped, or process parameters still have source-environment values Complete Step 7 (post-migration config) — re-link credentials and update parametersRobot shows Unresponsive on destination after migrationRobot VM not connected to destination instance, or sleep/network settings interferingRe-register the robot on the destination; check VM sleep and hibernation settings. See KB2725784Bot file not working after move to new VM or Cloud PCRPA Desktop Design Studio connection not re-established to the new machine Reconnect Design Studio to the destination instance, re-publish the package, and re-link it to the bot process Related LinksRelated Links Migrate the bot process – Zurich DocsBot Process Migration Overview – Xanadu DocsSeamless Bot Process Migration – Community BlogMigration Steps – Community Forum ThreadKB0951925 – Remote Instance Spoke ConfigurationKB1315563 – RPA Enablement GuideKB2725784 – RPA Hub Robots going to Unresponsive frequently (internal)