How to migrate Roles/Users/Assets/Queues from one Orchestrator to another?
An automatic option to perform bulk operations on entities like Assets, Machines, Processes, Users, Robots, Organization Units/Folders, Queues and Packages is the Orchestrator Manager. This is the most recommended approach.
Tool: Orchestrator Manager
Otherwise, the Orchestrator API can be used to migrate entities from one UiPath Orchestrator instance in the cloud to another, which are the same steps as for on-premise instances when migrating to a orchestrator or tenant to another, with some modifications. See example below on migrating an Asset:
- Backup assets on the source Orchestrator: Use the Orchestrator API to retrieve (GET) the assets and save them as files. A JSON response containing the source Orchestrator's assets will be received. A cloud storage service to store the files can be used too.
- Transfer the files to the target Orchestrator: Use a file transfer tool or a cloud storage service to transfer the files to the target Orchestrator
- Restore assets on the target Orchestrator: Use the Orchestrator API to upload the files to the target Orchestrator and create the assets (POST). Include a JSON payload containing the asset information that was previously retrieved.
- Update references to the assets: If the assets have dependencies on other assets, such as queues, update the references to the new assets in the target Orchestrator.
This has to be tested in lower environments before applying it to production.
It is also necessary to adjust these instructions depending on the API version and Orchestrator version being used as the endpoints might vary. Always refer to the official UiPath documentation for the most accurate information. More about the UiPath Orchestrator API: About OData And References.