Manual migration

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

note

Feature availability depends on the cloud platform you use. For details, refer to the feature availability page.

Manually recreating your Orchestrator setup

note

You must perform the following operations in Orchestrator, as described in the table, and make sure that you have the required permissions.

Step	Operation	Details
1	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.
2	Configure alert subscription settings	To receive alerts for a category, you need to have the corresponding permissions on that category as well.
3	Create folders and subfolders, and assign users to them accordingly	Perform this step if you need more folders.
4	Add credential stores	Cloud Orchestrator supports most third party stores. For a full list of supported credential stores, refer to Credential stores . For a list of unsupported credential stores, or custom secure store plugins, refer to Orchestrator Credentials Proxy as a potential solution.
5	Create assets	N/A
6	Publish packages from Studio or upload them manually	N/A
7	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.
8	Define triggers	N/A
9	Provision machines	N/A
10	Depending on your cloud platform: Create Robots in classic folders, or Manage Robots in modern folders	In classic folders, Robots need to be added to environments. 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.
11	Deploy processes	N/A
12	Create action catalogs	N/A
13	Create queues	N/A
14	Create webhooks	You can define webhooks at any point, depending on when you want to be notified during the migration.
15	Disconnect your Robots from the on-premises instance and then connect each Robot to your Orchestrator service	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 the cloud platform.