- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Downloading the installation packages
- Install-uipath.sh Parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
B) Single tenant migration
This is one of two ways in which you can migrate your standalone Orchestrator to Automation Suite.
For more information, see Migration options.
The tool can migrate to either Automation Cloud or Automation Suite, but this page describes the process of migrating to Automation Suite. For instructions on migrating to Automation Cloud, see the Automation Cloud documentation instead.
You can use the UiPath Automation Cloud™ Migration Tool to automatically migrate entities from your standalone Orchestrator to the Orchestrator service in Automation Suite.
You can only use the Automation Cloud Migration Tool if:
- your standalone Orchestrator version is 2019.10.x, 2020.10.x, 2021.4.x,, 2021.10.x, or later.
- your Automation Suite version is 2021.10.x or later.
When you run the Automation Cloud Migration Tool, it automatically creates the following entities in Automation Suite to match your standalone Orchestrator setup:
Entity |
Migrated |
Not Migrated |
---|---|---|
Settings |
Yes, with exceptions (see on the right). |
Some settings that are exposed to the tenant on the read path cannot be modified in Automation Suite, like host logo and color. Passwords in the Settings table cannot be exported because the API removes the values from the response. As a result no passwords will be migrated. This affects email alerts (SMTP password) and external feeds with basic authentication. |
Packages |
Migrates all packages and all package versions. If a package feed is external and configured with basic authentication, the credentials will need to be input after the migration completes. |
If a package feed is external and not accessible over the internet, entities that rely on these packages are not migrated. |
Libraries |
Tenant-level feeds only. |
If a library feed is at the host level or is external and not accessible over the internet, entities that rely on these libraries are not migrated. |
Calendars |
Yes |
N/A |
Machines |
Yes, but if there are not enough licenses to accommodate Machine slot assignments, the Machine will be imported with all slots set to 0. |
Machine keys are not migrated. |
Folders |
Yes |
Personal workspace folders are not migrated. |
Environments |
Yes, for classic folders. |
N/A for modern folders. |
Robots (classic) |
Yes, but if there are not enough licenses to accommodate robot creation, the robot is skipped during import. |
Skipped when licenses run out and an error is logged for each. |
Robots (modern) |
Modern robots are migrated if the user with which they are associated exists in Automation Suite and has the same email address. |
|
Environment associations |
The robot-environment mapping is migrated. |
N/A |
Processes |
Processes are migrated. The tool may refer to these as Releases. |
N/A |
Queues |
Yes |
N/A |
Triggers |
Triggers are migrated, but are all set as disabled. | |
Assets |
|
Per-user asset values in modern folders are not supported. The asset is imported with the default value or skipped if none is set. |
Machine associations |
Robot-machine mappings are migrated. |
N/A |
Before opening the tool, make the following preparations:
- Make sure you have sufficient robot licenses in Automation Suite to match the number of robots being migrated (Admin > Licenses > Robots & Services). The tool only migrates robots as long as there are licenses available, after which it starts to skip robots.
- You must have administrator credentials for the standalone Orchestrator and View permissions for all entities being migrated. If you don't have the View permission for some entities, those entities are not migrated.
- You must be an organization administrator in Automation Suite.
- To run the tool, you need a machine that:
- can connect to the standalone Orchestrator and to Automation Suite (has internet access)
- has the Windows operating system
- has .NET Core Desktop Runtime for x64 installed.
- Download the tool on the above-mentioned machine from this link.
- Register the tool as an external application in the target Automation Suite organization.
The tool can migrate one tenant at a time. You can run the tool multiple times for each of your tenants.
With each run, the tool:
-
Connects to your standalone Orchestrator to export entities for the given tenant.
-
Connects to Automation Suite to import and create the migrated entities in the Orchestrator tenant.
For more information about entities that are subject to migration, see Entities Being Migrated.
To run the tool:
Because the tool cannot migrate everything, there are some final tasks that you must perform manually to obtain the same setup as you had in your standalone Orchestrator.
If you need assistance with an issue encountered during export, import, or after import, open a Support ticket and include the following files:
- Log file (in the logs sub-folder)
- Export report file (in the MigrationAssets sub-folder)
- Import report file (in the MigrationAssets sub-folder)
In addition to these files, it would be helpful to know:
- The version of your standalone Orchestrator
- Your Automation Suite organization and tenant names.