How Enterprise 10 data is copied to Automation 360

Enterprise 10 users, roles, licenses, credentials, bots, and schedules are copied to Automation 360 as part of the copy data process.

The system copies Enterprise 10 data in the following order:
  1. Roles
  2. Users
  3. Credentials
  4. Bots
  5. Schedules

If the copy process skips an item in the sequence for any reason, then all related items are also skipped and are not migrated. For example, if the Bot_Manager role is not migrated and the user Jane_Smith belongs only to that role, then that user account and any credentials, bots, or schedules associated with that role are also not migrated.

Enterprise 10 items How Enterprise 10 items are copied to Automation 360
Users

When you copy Enterprise 10 users the first time, if the system encounters a user of the same name in Automation 360, the migration process renames the Enterprise 10 username by adding a suffix such as _1, _2, and so on, and then copies the renamed user to Automation 360. For example, a duplicate username Jane_Smith is renamed as Jane_Smith_1 in Automation 360. Subsequent data copy operations will skip the previously migrated user data.

For Active Directory users, the system does not migrate duplicate users. If a domain user with the same name already exists in Automation 360, the migration process skips that user and its dependencies.
Roles

The first time you copy Enterprise 10 roles, the migration process handles duplicate system roles and custom roles differently. The migration process maps Enterprise 10 system roles to Automation 360 system roles. For example, the Enterprise 10 Admin role and Basic role are mapped to the AAE_Admin role and AAE_Basic role, respectively.

If a custom role of the same name exists in Enterprise 10 and Automation 360, the migration process renames it by adding a suffix such as _1, _2, and so on, and then copies the renamed role to Automation 360. For example, a duplicate Sales_Operations role is renamed as Sales_Operations_1 in Automation 360.

Subsequent data copy operations will skip previously migrated roles.
Licenses

The migration process automatically migrates user allocated licenses, but they are not shown in the migration report. If the Automation 360 Control Room has fewer Bot Creator or Bot Runner licenses than Enterprise 10 Control Room and all Automation 360 licenses have been consumed, then newly migrated users will not be allocated any licenses. The system migrates these users and the related data without allocating any new licenses.
Credentials

For system credentials associated with a migrated user, the system migrates only the Email Settings and Autologin Settings system credentials.

For credentials created by the Control Room administrator, the system creates the AAE_10x_Credentials locker in the Automation 360 Credential Vault and adds the credentials from Enterprise 10 as standard credentials. The system assigns the user who migrates the Enterprise 10 data as the owner of the AAE_10x_Credentials locker and all custom roles as consumers of the locker. If a locker with the name AAE_10x_Credentials already exists in Automation 360, the system adds the migrated credentials in that locker.
Note:
  • Migration of credentials with more than 50 attributes is not supported.
  • Users with only AAE_Basic role assigned to them in Enterprise 10 must be granted a custom role in Automation 360 to be a consumer of the AAE_10x_Credential locker.
For MetaBots that contain screens as assets and use password type variables in these screens, equivalent credential type variables are created in Automation 360. If the password type variable in the MetaBot is an input variable and a value to that variable is passed from the parent bot in Enterprise 10, complete the following steps before you run the migrated bots:
  1. Create the credential with the Standard option selected as input.
  2. Create a locker and use the credential you created in the previous step in that locker.
  3. In the migrated parent bot, use the credential you created to pass that credential to the child bots.
If you have used an array variable within a loop to pass multiple values to the password type variable used in the MetaBot, the migrated bot uses the credential you created to pass a single value.
Bots If a bot of the same name exists in Enterprise 10 and Automation 360, the copy data process skips the bot migration and its associated schedule. Commands that use credential variables in Enterprise 10 bots use the AAE_10x_Credentials locker after migration.
If your Enterprise 10 Control Room is configured with SVN version control, then the copy data process also copies the latest version of each bot including the dependencies from the Enterprise 10 repository to the Automation 360 repository. Use the bot migration wizard to migrate the Enterprise 10 bots to Automation 360. However, the version history of the bot and its dependencies are not copied and migrated.
Note: Migration of the production version of Enterprise 10 bots is currently not supported. As a workaround, make or set the current production version of the bots as the latest version and then migrate the bots.
Schedules

If duplicate schedules exist in both environments, the duplicate schedule is migrated and results in two schedules of the same name in Automation 360.

Migration of schedules fails if the associated user doe not exist in Automation 360.

See the following video on how to review the copied Enterprise 10 data in Automation 360: