使用 Automation Cloud 迁移工具

The Automation Cloud Migration Tool is a desktop application designed to simplify the process of migration from one deployment option to another. The tool automates various migration steps, making it easier to transition either your standalone or Automation Suite Orchestrator to Automation Cloud, Automation Cloud Public Sector, or Automation Suite.

Instructions on this page apply for migrating your on-premises Orchestrator, either standalone or via Automation Suite, to Automation Cloud^TM.

When planning your migration from on-premises Orchestrator to Automation Cloud^TM, it is advisable that you take the following steps:

1. 升级到受支持的 On-Premises Orchestrator 版本。

2. Migrate from classic to modern folders, as classic folders have restrictions in Automation Cloud^TM.

3. Run the migration tool to migrate from on-premises Orchestrator to Automation Cloud^TM.

备注：

• 虽然其他序列在技术上也可行，但这是最常见的方法。

• Automation Cloud 迁移工具独立运行，不符合我们的标准产品生命周期。

要求

要使用迁移工具，您必须满足以下条件：

• 必须支持您的独立 Orchestrator 版本。有关特定版本的详细信息，请参阅我们的产品生命周期文档。

• 您需要在 Automation Cloud 中拥有 Pro 版、Pro Trial 版或 Enterprise 版许可证。虽然您可以在 Pro Trial 版期间使用该工具进行评估，但可能存在一些限制，例如租户和机器人许可证限制。如需了解详情，请参阅许可证文档。

先决条件

在打开 Automation Cloud 迁移工具之前，请做好以下准备：

1. Check that the Enterprise or Enterprise Trial licensing plan is active in Automation Cloud^TM (Admin > Licenses).

2. Make sure you have sufficient robot licenses to match the number of robots being migrated (Admin > Licenses > Robots & Services). The tool migrates robots as long as there are licenses available, after which it starts to skip robots.

3. Make sure you have administrator credentials for the on-premises Orchestrator

4. Make sure you have View permission for all entities being migrated. If you do not have the View permission for some entities, those entities will not be migrated.

5. 您必须是 Automation Cloud 中的组织管理员，才能将该工具注册为外部应用程序。

6. 确保运行 Automation Cloud 迁移工具的计算机满足以下要求：

   1. Can connect to the on-premises Orchestrator;

   2. Can access Automation Cloud^TM (has internet access and a supported browser);

   3. Runs the Windows operating system;

   4. Has .NET Core Desktop Runtime for x64 installed.

7. Download the migration tool on the machine that meets the requirements in the previous step.

迁移工具迁移的实体

When using the migration tool, the following entities are automatically created in Automation Cloud^TM to mirror your Orchestrator setup:

实体	已迁移	未迁移
设置	Yes, with exceptions	一些本地部署设置，例如密码和向租户公开的某些设置
包	All packages and package versions	Entities that rely on external package feeds requiring authentication 备注： Authentication is required after migration is completed for external package feeds configured with basic authentication
库	Tenant-level feeds only	Entities that rely on libraries with host-level configurations or inaccessible external libraries
日历	是	不适用
计算机	是 备注： Potential machine slot assignments limitations due to missing licenses	计算机键值
文件夹	是	Personal workspace folders
环境	是，适用于传统文件夹。	不适用 （适用于新式文件夹）
机器人（传统）	是 备注： Potential robot creation limitations due to missing licenses	Skipped when licenses run out, with an error logged for each skipped robot
机器人（新式）	是 备注： If certain conditions are met, robots are associated with an on-premises user that has an email address, and that same email was already invited to Automation CloudTM and is associated to a user.	Skipped when licenses run out, with an error logged for each skipped robot Fails if a user in Automation CloudTM does not exist
环境关联	机器人-环境映射	不适用
流程	是 备注： The migration tool may refer to processes as releases	不适用
队列	是	不适用
触发器	Yes, but they are set as disabled	不适用
资产	Certain asset types are fully supported, with some considerations for credential assets	新式文件夹中的每用户资产值
文件夹订阅源	是	不适用

迁移工具未迁移的实体

The migration tool does not migrate the following entities:

• 用户和机器人帐户

• 角色分配

• 队列项目

• 操作目录

• Webhooks

• 测试实体（测试集、测试用例、测试执行、测试计划、测试数据队列）

• 存储桶

• 日志

将迁移工具注册为外部应用程序

The migration tool must connect to the Orchestrator service API in Automation Cloud^TM to create the migrated entities. It uses the OAuth flow for this and, therefore, must be registered as an external application.

要将 Automation Cloud 迁移工具注册为外部应用程序，请执行以下步骤：

1. Add the tool as a new external application by following the instructions in Adding an external application. Make sure to use the following configuration:

   • 类型：非机密

   • 资源：Orchestrator API

   • 用户作用域：OR.Folders、OR.Settings、OR.Robots、OR.Machines、OR.Execution、OR.Assets、OR.Users、OR.Jobs 和 OR.Queues。
   • 重定向 URL：http://127.0.0.1:8888/auth/

2. 保存应用程序 ID 以供日后使用。

运行迁移工具

该迁移工具一次只能迁移一个租户。您可以为每个租户运行工具。每次运行时，该工具都会执行以下操作：

• 连接到 On-Premises Orchestrator，以导出给定租户的实体。

• Connects to Automation Cloud^TM to import and create the migrated entities in Orchestrator.

若需详细了解要进行迁移的实体，请参阅迁移工具迁移的实体。

1. Extract the .zip file you downloaded for the tool, and then run the .exe tool.
2. To choose your export environment, take one of the following steps:

   • 如果您从独立版 Orchestrator 迁移，请选择“本地部署 MSI”。

   • 如果您从 Automation Suite Orchestrator 迁移，请选择“Automation Suite”，连接到外部应用程序并填写导出输入表单。

     
3. 填写相关信息，以允许该工具连接到 On-Premises Orchestrator。
   

   

   注意：请确保您提供的凭据适用于管理员帐户，并且该帐户对要迁移的所有实体具有查看权限。
4. Select Start Export to connect to your source environment and download the setup information. The export begins and may take a while to complete.
   
   完成后，导出摘要将列出已成功导出的所有实体。您可以选择“打开文件”，查看为导出摘要创建的本地文件，其中包括一些详细信息。

   
5. Select Home to return to the first screen of the migration tool.
6. For the activation method, this time choose Connect to Automation Cloud^TM.
7. Fill in the information to allow the tool to connect to Automation Cloud^TM to upload the setup information.
   

   字段	详细信息
   客户端应用程序 ID	The Application ID value associated with the external application registration in Automation CloudTM. 您可以在“管理” > “外部应用程序”页面上找到此值。
   组织名称	The organization-specific part of your Automation CloudTM URL. Organization administrators can find this information in the URL field in Admin > Organization Settings. 注意：您不需要包含完整的 URL，只需包含可编辑的部分，也就是特定于您的组织的部分。例如，如果 URL 为 https://cloud.uipath.com/myOrgName，则将 myOrgName 添加到字段中。
   租户名称	The exact name of the Automation CloudTM tenant where you want to add the migrated information. The migrated data will be visible in the Orchestrator service associated to that tenant.

8. Select Start Import to connect to Automation Cloud^TM and start to migrate the information to the target Orchestrator service.

   导出开始，可能需要一段时间才能完成。

   To connect to Automation Cloud^TM using OAuth, a user with the adequate permissions for the scopes added when you registered the external application must log in to Automation Cloud^TM. When they do, a new window opens with a success message, if the OAuth flow was successful.

   

   When finished, the import summary lists all entities that were successfully imported into the Orchestrator service in Automation Cloud^TM.

   

   Anything that was not imported is listed as an error and partial imports are listed as warnings. You can select View Report for more details about exactly which entities encountered an error or warning.
9. 准备就绪后，单击“完成”以关闭工具。

提示：如有需要，您可以再次运行该工具，以迁移其他租户的数据。

迁移后任务

由于 Automation Cloud 迁移工具无法迁移所有数据，您必须手动执行一些最终任务。

1. In Automation Cloud^TM, select the tenant that was the import target, and open Orchestrator. Check that folders and entities were successfully migrated. You can use the import summary to check the specific items that had warnings or errors.
2. 为 Orchestrator 分配机器人和服务许可证。在存在可用许可证的情况下，创建计算机并分配许可证，但在许可证用尽后，将继续在没有许可证的情况下创建计算机，因此您必须进行更新，以分配足够数量的许可证。
3. 手动上传工具未迁移的任何库订阅源。
4. 如果在导出或导入期间跳过了任何机器人，请手动创建机器人。
5. 创建工具不会迁移的任何 Webhook、任务目录、凭据存储或其他信息。“正在迁移的实体”部分还会列出该工具不会迁移的内容。
6. 手动将机器人连接到 Cloud Orchestrator 服务。
7. 根据需要手动启用触发器。
8. 检查 Orchestrator 中所有需要密码的位置，并将添加：机器人、设置和凭据资产。

获取帮助

如果您在导出、导入或导入后遇到问题且需要帮助，请打开支持工单并添加以下文件：

• 日志文件（位于 logs 子文件夹中）

• 导出报告文件（在 MigrationAssets 子文件夹中）

• 导入报告文件（在“迁移资产”子文件夹中）

除了之前的文件外，了解以下信息将有所帮助：

• On-Premises Orchestrator 的版本；

• Your Automation Cloud^TM organization and tenant names.