Migration: On-premise to cloud orchestrator


We are planning to migrate from our on-premise orchestrator to cloud orchestrator using the Automation Cloud Migration Tool. The Orchestrator Logs and Queue items/data won’t be migrated with the tool. We are looking if there is any way to migrate these data as well.

Please share your thoughts.


Hi @Jerry1,

Can you open a ticket and inquire whether you can receive support on this matter? There’s a possibility that UiPath could assist with moving the db tables.


Yes, I will try that


Did you get any response from technical support?

Have you managed to migrate Logs and Queues data?

Thanks in advance,

Hello @Jerry1 ,

please see the below information for on-Prem to cloud orchestrator Migration.

Below entities were not Migrated:

  • Folder feeds
  • User and robot accounts
  • Role assignments
  • Queue items
  • Action catalogs
  • Webhooks
  • Testing entities (test sets, test cases, test executions, test schedules, test data queues)
  • Logs


Below are the prerequisites:

  1. First need to check on Enterprise or Enterprise Trial licensing plan in active in Automation Cloud. To check this, go to Admin > Licenses.

  2. Check on we have sufficient robot licences in Automation cloud to match the number of robots being migrated. To check validate licences go to Admin > Licenses > Robots & Services. Tool only migrate robots for which licence is available.

  3. We need administrator credentials for the on-premises Orchestrator and the View permission for all entities being migrated. If you don’t have the View permission for some entities, those entities are not migrated.

  4. You must be an organization administrator in Automation Cloud to register the tool as an external application.

  5. To run the tool, you need a machine that:

  6. can connect to the on-premises Orchestrator.

  7. can access Automation Cloud (has internet access and a supported browser)

  8. has the Windows operating system.

  9. has .NET Core Desktop Runtime for x64 installed.

  10. You can download the tool on the above-mentioned machine: Download the Migration Tool

Running the Tool:

The tool can migrate one tenant at a time. You can run the tool for each of your tenants. With each run, the tool:

Connects to your on-premises Orchestrator to export entities for the given tenant.

Connects to Automation Cloud to import and create the migrated entities in Orchestrator service.

Below are the steps:

Extract the ZIP file you downloaded for the tool and then run the tool EXE.

For the activation method, choose Connect to On-Premises:

Fill in the information to allow the tool to connect to your on-premises Orchestrator:

Make sure that the credentials you provide are for an administrator account that also has View permissions on all the entities you want to migrate.

Click Start Export to connect to on-premises Orchestrator and download the setup information. export begins and may take a while to complete.

  • You can click Open File to view the local file created for the export summary, which includes a few more details.
  • Click Home to return to the first screen.
  • For the activation method, this time choose Connect to Automation Cloud.

Fill in the information to allow the tool to connect to Automation Cloud to upload the setup information:

Click Start Import to connect to Automation Cloud and start to migrate the information to the target Orchestrator service.

The import begins and may take a while to complete:

To connect to Automation Cloud using OAuth, a user with the adequate permissions for the scopes added when you registered the external application must log in to Automation Cloud. When they do, a new window opens with a success message if the OAuth flow was successful:

Post-migration Tasks:

Because the tool cannot migrate everything, there are some final tasks that you must perform manually.

  • In Automation Cloud, select the tenant that was the import target and then open Orchestrator. Check that folders and entities were successfully migrated. You can use the import summary to check the specific items that had warnings or errors.
  • Allocate robot and service licenses for Orchestrator. Machines are created and licensed while available licenses exist, but after licenses run out, machines continue to be created without licenses, so you must update them to allocate the adequate number of licenses.
  • Manually upload any library feeds that the tool did not migrate.
  • If any robots were skipped during export or import, manually create them.
  • Create any webhooks, task catalogs, credential stores, or other information that the tool does not migrate. The section Entities Being Migrated also includes a list of what the tool does not migrate.
  • Manually connect robots to the cloud Orchestrator service.
  • Manually enable triggers as needed.
  • Check any locations in Orchestrator where a password is required and add it: Robots, Settings, and Credential Assets.

More details: