UiPath Automation Cloud

The UiPath Automation Cloud Guide

Check the current status of Automation Cloud here.

Migrating Data from On-Premises to Cloud Orchestrator

This page describes a method to perform data migration from your on-premises Orchestrator tenants to Cloud Orchestrator services. This method requires that you manually recreate the on-premises configuration and entities in your Automation Cloud organization.



Robots can be connected to only one source at a time. When a Robot is disconnected from the on-premises Orchestrator and connected to Cloud Orchestrator, it automatically consumes a new license from Automation Cloud.

On-premises and Automation Cloud Orchestrator come with the same capabilities, with few notable exceptions listed here.

Cloud Portal Settings





Manage organization settings

Perform organization name, site URL or language changes.


Create your Orchestrator service

If you want to keep the on-premises configuration, for each tenant create a Cloud Orchestrator service.


Allocate the desired number of licenses for your service from the total number of available licenses

Community Automation Cloud comes with one default service. You can create multiple services if you are on the Enterprise Trial or Enterprise plan. License activation is performed automatically.

License allocation can be performed during Orchestrator service creation.


Invite users to join your organization

Users in Automation Cloud Orchestrator are invitation-based.


Assign the users to Orchestrator services, and grant them access-rights by associating them to the corresponding Orchestrator roles

Create additional roles in Orchestrator if you need more on top of the Administrator one.

Assigning users to Orchestrator services and granting them access-rights can be performed while inviting them.

Cloud Orchestrator Settings



These operations must be performed by users with appropriate permissions.





Configure tenant settings

On the General tab, adjust the time zone of the tenant, the language of the user interface for Orchestrator, and toggle the Modern Folders feature.
On the Deployment tab, configure and secure the automation packages feeds.
On the Mail tab, configure email settings.
On the Scalability tab, specify if the Robot service should subscribe to Orchestrator's SignalR channels, and configure the transport protocols that work best for you.
On the Non-Working Days tab, define a list of non-business days, per tenant, on which you may configure your schedules to not run.


Configure alert subscription settings

In order to receive alerts for a category, you need to have the corresponding permissions on that category as well.


Create folders and subfolders, and assign users to them accordingly

Perform this step if you need more folders on top of the Default Classic folder which is automatically created within your service.
Adding users to an Orchestrator service in Cloud Portal also results in adding them to the Default Classic folder, if it exists and it hasn't been renamed.


Add credential stores

Only Azure Key Vault and Orchestrator Database are supported as credential stores. Other third-party stores are not available in Cloud Orchestrator.


Create assets


Publish packages from Studio or upload them manually


Upload libraries

In Cloud Orchestrator, you can only publish libraries at service level. To share libraries between Orchestrator services, you can use a custom feed.


Define triggers


Provision machines


Create Robots in classic folders

Manage Robots in modern folders

In classic folders, Robots need to be added to environments.
See Creating a New Environment for instructions.

In modern folders, Robot settings are controlled at user level. Robots are automatically provisioned for users with access to the new modern folder.
Environments are not used in the context of a modern folder.


Deploy processes


Create task catalogs


Create queues


Create webhooks

You can define webhooks at any point, depending on when you want to be notified during the migration.


Disconnect your Robots from the on-premises instance and then connect each Robot to your Orchestrator service

Remember to add the AccountLogicalName and ServiceName to the Orchestrator URL (E.g.[AccountLogicalName]/[ServiceName]/), and the new machine key when filling in connection details in the Robot tray.

Updated about a month ago

Migrating Data from On-Premises to Cloud Orchestrator

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.