- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Migrating standalone products to Automation Suite
Migrate standalone UiPath products to Automation Suite on EKS/AKS.
To migrate your standalone Orchestrator data to Automation Suite, you can use the UiPath Automation Cloud™ Migration Tool. The tool helps you run a single tenant migration process and copy strictly the entities present in your standalone Orchestrator. The tool retrieves these entities from standalone Orchestrator over API and then writes them in Automation Suite over API.
The tool can migrate to either Automation Cloud or Automation Suite, but this guide describes the process of migrating to Automation Suite. For instructions on migrating to Automation Cloud, refer to the Automation Cloud documentation instead.
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.
Before you run a tenant migration, review the details from the following table to understand the scope, results, and requirements.
| Category | Description |
|---|---|
| Scope | - Tenants: Only the targeted tenant. You can run the tool multiple times to migrate several or all tenants. - Entities: Only migrates the Orchestrator entities listed in Entities being migrated. - Orchestrator configurations: Some Orchestrator settings are migrated, but not all. For details, refer to Entities being migrated. |
| Outcome | All your entities are copied over to Orchestrator, but Orchestrator in Automation Suite uses the default Automation Suite configuration. To get to the same setup you had in your standalone installation, you must perform a first-time configuration of Automation Suite, which you can do at any time - before or after migration. |
| Prerequisites | Supports direct migration from any supported standalone Orchestrator version 2019.4. |
| Organization hierarchy | You can migrate your tenants to the same organization, or to several organizations, as needed. |