- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Migration compatibility matrix
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- 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 creation
- Troubleshooting
Automation Suite on OpenShift installation guide
Migration compatibility matrix
When migrating from a standalone product to Automation Suite, you must make sure the versions of the standalone product, UiPath.OrganizationMigrationApp, Automation Suite, and the Identity and Orchestrator migrators are compatible.
The following table describes the version compatibility required to perform a migration to Automation Suite:
| Source standalone product version | Test Manager migration script version | UiPath.OrganizationMigrationApp version | Target Automation Suite version | Identity migrator | Orchestrator migrator | ||
|---|---|---|---|---|---|---|---|
| Orchestrator | Insights | Test Manager | |||||
| 2024.10.6 2024.10.5 | 2024.10.6 | 2024.10.6 | 2024.10.1 | 2024.10.5 | identity-service-datamigrator:25.10.17-release-k8.21 | orchestrator:24.10.9 | |
| 2024.10.6 2024.10.5 | 2024.10.6 | 2024.10.5 | 2024.10.1 | 2024.10.5 | identity-service-datamigrator:25.8.6-release-k8.15 | orchestrator:24.10.8 | |
| 2024.10.3 2024.10.4 | 2024.10.5 | 2024.10.4 | 2024.10.1 | 2024.10.4 | identity-service-datamigrator:25.5.19-release-k8.2 | orchestrator:24.10.7 | |
| 2024.10.2 | 2024.10.4 | 2024.10.3 | 2024.10.1 | 2024.10.3 | identity-service-datamigrator:25.3.19-release-k8.27 | orchestrator:24.10.5 | |
| 2024.10.1 | 2024.10.2 2024.10.3 | 2024.10.2 | 2024.10.1 | 2024.10.2 | identity-service-datamigrator:25.1.22-alpha-k8.19 | orchestrator:24.10.3 | |
| 2024.10.1 | 2024.10.1 | 2024.10.1 | 2024.10.1 | 2024.10.1 | identity-service-datamigrator:24.11.25-alpha-k8.10 | orchestrator:24.10.2 | |
| 2024.10.0 | 2024.10.0 | 2024.10.0 | 2024.10.1 | 2024.10.0 | identity-service-datamigrator:24.10.9-release-k8.31 | orchestrator:24.10.0 | |
How to read the table
-
As an example, to migrate standalone Orchestrator 2024.10.0, you must use UiPath.OrganizationMigrationApp 2024.10.0 and make sure that you installed Automation Suite 2024.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.