- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration compatibility matrix
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Version compatibility requirements for migrating standalone products to Automation Suite on EKS/AKS.
When migrating from a standalone product to Automation Suite, you must make sure the versions of the standalone product, UiPath.OrganizationMigrationApp, and Automation Suite are compatible.
The following table describes the version compatibility required to perform a migration to Automation Suite:
| Standalone product version | Test Manager migration script version | UiPath.OrganizationMigrationApp version | Automation Suite version | ||
|---|---|---|---|---|---|
| Orchestrator | Insights | Test Manager | |||
| 2023.10.15 2023.10.14 | 2023.10.11 | 2023.10.12 | 2023.10.6 | 2023.10.11 | |
| 2023.10.13 | 2023.10.10 | 2023.10.12 | 2023.10.6 | 2023.10.10 | 2023.10.10 |
| 2023.10.10 | 2023.10.9 | 2023.10.10 | 2023.10.6 | 2023.10.9 | 2023.10.9 |
| N/A 1 | N/A 1 | 2023.10.6 | N/A 1 | ||
| 2023.10.9 | 2023.10.7 | 2023.10.9 | 2023.10.6 | 2023.10.8 | 2023.10.7 |
| 2023.10.8 | 2023.10.6 | 2023.10.8 | 2023.10.6 | 2023.10.7 | 2023.10.6 |
| 2023.10.6 | 2023.10.5 | 2023.10.6 | 2023.10.6 | 2023.10.6 | 2023.10.5 |
| 2023.10.5 | 2023.10.4 | 2023.10.5 | 2023.10.6 | 2023.10.5 | 2023.10.4 |
| 2023.10.4 | 2023.10.3 | 2023.10.4 | 2023.10.6 | 2023.10.4 | 2023.10.3 |
| 2023.10.3 | N/A | 2023.10.2 | 2023.10.6 | 2023.10.2 | 2023.10.2 |
| 2023.10.1 | N/A | 2023.10.1 | 2023.10.6 | 2023.10.1 | 2023.10.1 |
| 2023.10.0 | N/A | 2023.10.0 | 2023.10.6 | 2023.10.0 | 2023.10.0 |
1 There are no Orchestrator and Insights standalone versions compatible with Automation Suite 2023.10.8. Therefore, no UiPath.OrganizationMigrationApp version is available with Automation Suite 2023.10.8.
How to read the table
- As an example, to migrate standalone Orchestrator 2023.10.0, you must use UiPath.OrganizationMigrationApp 2023.10.0 and make sure that you installed Automation Suite 2023.10.0.
- For information on updates to the UiPath.OrganizationMigrationApp and the migration workflows, see the release notes for your
targeted Automation Suite version. The links to the release notes are available in the Automation Suite version column.
If there is no entry dedicated to the UiPath.OrganizationMigrationApp in the release notes, this means that we made only minor improvements to the tool.