Prepare to manually migrate to Automation 360 Cloud

You can manually migrate from Enterprise 11 or Enterprise 10 to Automation 360 Cloud (without using the Cloud Migration Utility) by creating users, roles, permissions, and other entities required by the migrated bots to run successfully.

Prerequisites

Note: The only way by which you can migrate from Enterprise 11 or Enterprise 10 to Automation 360 Cloud on Google Cloud Platform is by using the following procedure.

Ensure that you have completed the following tasks to check your readiness for migration
Check migration readiness.
Ensure you have procured and activated your migration license.
Get migration license

Note: Use the manual migration in the following scenarios:

You have an existing Automation 360 Cloud instance and want to migrate your Enterprise 11 data.
When you want to migrate only bots and re-create all other Enterprise 11 or Enterprise 10 entities such as users, roles, and credentials manually in Automation 360.
When you want to migrate only a few of the Enterprise 11 or Enterprise 10 entities. For example, if you have 50 users and 10 user-defined roles in Enterprise 11 or Enterprise 10 and you want to migrate only 40 users and 7 roles to Automation 360. Similarly, if you want to migrate only users and roles and want to re-create the required schedules in Automation 360.

For information about automated migration to Cloud (using the Cloud Migration Utility), see Prepare for Enterprise 11 to Automation 360 Cloud migration.

Procedure

Create all the Enterprise 11 or Enterprise 10 entities in Automation 360 Cloud.
For more information about the entities you must create, see Prerequisites for manual migration.

Upload the bots:

Version

Steps

Enterprise 11

Import bots

Enterprise 10

Upload bot and its dependencies
The bots are uploaded to the private workspace in Automation 360. Ensure you have created the same folder structure in the public workspace as in Enterprise 10 Control Room.

You must upload all dependent bots and other files required by the uploaded bots to run successfully in Automation 360. All uploaded bots, their dependent bots, and other required files must be stored in the same folder in the Automation 360 as in Enterprise 10.
Check in the uploaded bots that are available in the private workspace.
Check in a bot

See the following video on how to manually migrate to Automation 360 using Bot Lifecycle Management:

<span>Manually migrate to <span class="ph">Automation 360</span> using <span class="ph">Bot Lifecycle Management</span> </span>

Next steps

Prerequisite tasks for migrating bots