- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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: 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
Automation Suite on EKS/AKS installation guide
Performing a full migration
The full migration is one of two ways in which you can migrate a standalone UiPath® product to Automation Suite. This method helps you migrate Orchestrator and other products and services. For more information, see Migration options.
We tested the migration for Orchestrator, Action Center, and Test Automation, which share the same database, as well as Insights.
The full migration options also ensures high-fidelity data transfer between the standalone product databases and the automatically created Automation Suite databases. If you do not want to use the default Automation Suite databases, you can opt for your own migrated databases provided that you update their connection strings.
To migrate from a standalone deployment to Automation Suite, take the following steps:
|
Description |
Instructions |
|
1. Upgrade your standalone deployment. |
|
|
2. Deploy Automation Suite. |
|
|
3. Make sure you meet the requirements. |
|
|
4. Follow the pre-migration steps. |
|
| 5. Follow the migration steps. |
|
|
6. Follow the post-migration steps. |
|
