- Overview
- Requirements
- Pre-installation
- 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: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS 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 | UiPath.OrganizationMigrationApp
version |
Target Automation Suite version | Identity migrator | Orchestrator migrator | |
|---|---|---|---|---|---|
| Orchestrator | Insights | ||||
| 2024.10.2 | 2024.10.4 | 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 |
| identity-service-datamigrator:25.1.22-alpha-k8.19 | orchestrator:24.10.3 |
| 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 |
| identity-service-datamigrator:24.10.9-release-k8.31 | orchestrator:24.10.0 |
-
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.
