Migrate to Automation 360
- Updated: 2024/04/25
Migrate to Automation 360
Migration (upgrade) is the process of moving your data and bots from Enterprise 11 or Enterprise 10 to Automation 360. Migration includes but is not limited to replicating and updating your existing database and repository, converting your bots to the Automation 360 format, and migrating learning instances for IQ Bot and dashboards for Bot Insight.
Automation 360 is a single, integrated cloud-native Digital Workforce platform that is designed for flexibility and agility. Migrating to this platform provides you benefits such as faster time to value, business agility, and lower TCO.
For more information, see Automation 360.
What is migration
The migration (or upgrade) process copies all your Enterprise 11 or Enterprise 10 entities such as users, roles, lockers, and bots to Automation 360. This eliminates the efforts required to re-create all these entities in Automation 360. The migration process also eliminates the possibility of missing out on copying an entity that might be required to run a bot after migration. All the Enterprise 11 or Enterprise 10 entities are ready for use in Automation 360 after they are successfully migrated, except bots and MetaBots.
When Enterprise 11 or Enterprise 10 data is migrated, bots are copied as .atmx files and MetaBots are copied as .mbot files. You must convert these bots and MetaBots to the Automation 360 format before you use them.
Migration also includes migrating your IQ Bot learning instances and Bot Insight dashboards.
- IQ Bot migration
- When migrating Enterprise 11
or Enterprise 10
bots, migrate your IQ Bot learning instances. Before starting the IQ Bot migration, ensure that your Automation 360 environment is installed and set up
for use. IQ Bot migration involves migrating the
bots built to use IQ Bot as well as the IQ Bot
learning instances that have been trained for data extraction.
Use the IQ Bot server upgrade and learning instance procedures to move the information over to your new system. See Migrate to Automation 360 IQ Bot.
- Bot Insight migration
- Migration of the Bot Insight data and dashboard is performed as part of the overall migration process. It involves cloning your Bot Insight database (which is separate from your Enterprise 11 Control Room database) and using the pre-migration utility to extract your dashboard metadata (widgets, layouts, and so on).
Migration phases
Migration involves three main steps, as shown in the following image:
-
Check migration readiness
Analyze your bots using the Bot Scanner and review the generated report to verify your migration readiness.
- Prepare new Control Room for migration
Choose your deployment model (Cloud or On-Premises and request for the migration licenses. Prepare your Control Room and environment for the migration.
-
Migrate and validate bots
Convert your Enterprise 11 or Enterprise 10 bots to Automation 360 format. After migration, verify the converted bots run successfully, and update bots as required based on the migration reports or testing phase.
Note: If you encounter any error when you migrate from Enterprise 11 or Enterprise 10, you might have to review or take some actions on the migrated bots. See Migration messages.
Tools used for migration
The following tools are available for migration:
- Bot Scanner
- The Bot Scanner scans your existing bots (Task Bots and MetaBots) and generates reports. These reports provide information about the commands and variables used in these bots and how many of these commands and variables are supported for migration in Automation 360. (The scanner was previously called the pre-migration utility.)
- Bot Migration Wizard
- Integrated in the Automation 360 Control Room, this tool guides you through the process of converting the bots to the Automation 360 compatible format after you have completed the prerequisites steps. The wizard enables you to migrate multiple bots (Task Bots and MetaBots) and their dependent bots.
- Cloud Migration Utility
- This tool enables you to upload all your Enterprise 11 data to Automation Anywhere Cloud. After the data is successfully uploaded to Cloud, the Cloud Control Room is created and all the uploaded data is available for use in that Control Room. The utility migrates data from Control Room repository (bots, their dependencies, and Credential Vault) and Control Room database (users, roles, schedules, queues, and Control Room settings).
- Audit log data migration utility
- This utility enables you to export the audit log data from the Enterprise 11 Control Room to a JSON file. You must paste the JSON file in the Automation 360 repository and then migrate the audit log data.
- Bot Insight pre-migration utility
- This utility enables you to export Enterprise 11 Bot Insight dashboard metadata (widgets and layouts) and dashboard profiles as a zip file. You must paste the zip file in the Automation 360 repository to migrate the Bot Insight dashboards.
What is migrated and not migrated
Enterprise 10 : Review the information about what is migrated and what is not migrated for the On-Premises deployment model.
| Enterprise 10 | Migrated to On-Premises |
|---|---|
| Bots and their dependencies | Yes |
| Credential Vault | Yes |
| Roles | Yes |
| Users | Yes |
| Schedules (these are disabled after they are migrated to Automation 360) | Yes |
| Audit logs | No |
| Bots version control history | No |
| Devices and device pools | No |
| File system logs | No |
| IQ Bot (IQ Bot migration requires a separate process) | No |
Enterprise 11 : Review the information about what is migrated and what is not migrated for the different deployment models.
| Enterprise 11 | Cloud | On-Premises |
|---|---|---|
| Users, roles, and credential variables and lockers | Yes | Yes |
| Bots and their dependencies | Yes | Yes |
| Schedules (these are disabled after they are migrated to Automation 360) | Yes | Yes |
| Workload queues | Yes | Yes |
Bot Insight dashboards
|
Yes | Yes |
Bots transactional data
|
Yes | Yes |
| Bot execution operational data | Yes | Yes |
| Licenses | Yes (Requires unique license GUID) | Yes |
| IQ Bot learning instances (IQ Bot migration requires a separate process) | No | Yes |
| Audit logs | No | Yes |
| Device pools | No | Yes |
| Historical data | Yes | Yes |
| Control Room settings | No | Yes |
| Bots version control history | No | No |
| Devices | No | No |
| File system logs | No | No |
| Workflows | No | No |
| Bot Insight dashboards for imported bots | Yes | No |
| AASettings.xml file data | No | No |
Choose your migration path
After you have verified the migration readiness for your current version, choose your migration path based on the Automation 360 deployment model that meets your business requirements.
| If you are on this version | Start your migration |
|---|---|
| Enterprise 11 |
|
| Enterprise 10 |
Enterprise 10 to Automation
360 On-Premises
Workflow map: Click the following schematic image
to view this migration workflow in an interactive visual
format:
 Note: We do not support migration from Enterprise 10 to Automation 360
Cloud. However, you can manually migrate Enterprise 10 to Automation 360 by using the bot export
utility. For assistance, contact Automation Anywhere support: Open a support case (A-People login required).
|
If you have a large number of bots, you can run both Automation 360 and Enterprise 11 or 10 in parallel. This dual-environment method helps to eliminate downtime. Choose one of the following procedures based on your deployment model:
| If you want to use these dual environments | Use this procedure |
|---|---|
| Enterprise 11 and Automation 360 Cloud | Enterprise 11 and Automation 360 Cloud in parallel |
| Enterprise 11 and Automation 360 On-Premises | Enterprise 11 and Automation 360 On-Premises in parallel |
| Enterprise 10 and Automation 360 On-Premises | Enterprise 10 and Automation 360 On-Premises in parallel |
Other resources
- Migration resource center: Access multiple migration resources, including videos, project templates, and high-level information from one place.
-
Automation Anywhere University: RPA Training and Certification (A-People login required):
Access the Migrating to Automation 360 learning
trail.
Learn how to use Automation 360 with Automation Anywhere University for hands-on learning that is designed for beginners to advanced developers. Instructor-led training options are also available.
- XML path is not working which works fine in Enterprise 11