- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- Tenants and services
- Accounts and roles
- External applications
- Notifications
- Logging
- Troubleshooting
- Migrating to Automation Cloud Dedicated
Automation Cloud Dedicated admin guide
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 Automation CloudTM Dedicatedorganization.
|
Step |
Operation |
Details |
|---|---|---|
|
1 |
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 |
Only Azure Key Vault and Orchestrator Database are supported as credential stores. Other third-party stores are not available in Cloud Orchestrator. | |
|
5 | ||
|
6 | ||
|
7 |
In Cloud Orchestrator, you can only publish libraries at service level. To share libraries between Orchestrator services, you can use a custom feed. | |
|
8 | ||
|
9 | ||
|
10 |
Manage Robots in modern folders |
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 | ||
|
12 | ||
|
13 | ||
|
14 |
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 Automation CloudTM Dedicated. |
