Migrate Enterprise bots

The bot migration process uses the Bot Migration Wizard to convert Enterprise 11 or Enterprise 10 bots (Task Bots and MetaBots) in .atmx and .mbot format to the .bot format used in Automation 360 and uploads the successfully migrated bots to the Control Room public workspace.

Prerequisites

Ensure you have completed all the prerequisite tasks for migrating bots: Prerequisite tasks for migrating bots.

All manual dependencies of bots are automatically converted as Control Room dependencies during migration. The Copy Control Room file action copies these dependencies from the Control Room to the respective locations.

Procedure

  1. Log in to your Automation 360 staging environment.
  2. Click Administration > Migration.
    Note: If you have migrated bots from Enterprise 10 to Enterprise 11, the information about that migration is not displayed on the Migration List page.
  3. On the Bot Migration Wizard screen, click Migrate bots.
    Settings tab
  4. Select the options and configuration as required in the the Settings tab.
    OptionAction
    Name Enter a migration name or use the default one. The default migration name shows the name of the user who is logged in, current date, and time stamp.
    Description Enter a description for the migration.
    Overwrite if a bot with the same name exists Select this option to overwrite an existing bot if a bot with the same name exists in the folder.
    Exclude bot dependencies Select this option to exclude child bots of sub-tasks from migration or updating. By selecting this flag, you can now choose to migrate parent and child bots separately or independently.
    Use "Excel Cell Row" legacy behavior Select this option if you are migrating from a version earlier than Version 11.3.0 or you want to retain the legacy behavior of the Excel Cell Row system variable.
    Use outgoing Email server settings Select this option if your bot contains the Send Email command. Use these settings to specify the type of email server to use.
    Include web service settings Select this option for custom proxy configuration support. When you select this option, the REST commands with Custom proxy configurations that use the following global variables are migrated:
    • AAProxyHost for Hostname
    • AAProxyPort for Port
    Convert bots built using Internet Explorer to Edge with Internet Explorer mode Select this option if you want to migrate Enterprise 10 or Enterprise 11 bots that use Internet Explorer to Automation 360 bots that use Microsoft Edge with IE mode.
    Convert \n characters to \r\n in Log to File action Select this option to convert \n characters (LF) into \r\n characters (CRLF), which automatically take new line in migrated bots using Log to File action.
    Tag bots and variables for analytics Select this option when Bot Insight data exists in the Enterprise 11 bots, and you also want to migrate the Bot Insight data with those bots. When you select this option, the Bot Insight Open and Close actions are created.
    Note: To migrate Bot Insight data, you must enable this option.

    When you migrate Bot Insight data along with bot migration, ensure that the Bot Insight prerequisites are met.Bot Insight prerequisites | Cloud Migration Utility prerequisites

    If the Bot Insight prerequisites are not met, Cloud migration with Bot Insight might become stuck in the In Progress state.

    Also, regardless of whether the Bot Insight and the Cloud Migration utility prerequisites are met or not, import or upload of the .atmx file > Migrate. This issue is observed on both On-Premises and Cloud deployments.
  5. Click Next.
  6. Select the bots and the folders that contain the bots (Task Bots and MetaBots) that you want to migrate.
    The ability to select a folder eliminates the effort required in selecting individual bots from that folder.
    • If you selected a folder, all subfolders within that folder and the bots within these subfolders are automatically selected for migration.
    • If the folder is empty, the migration process encounters an error.
    The Last Migrated column indicates when the bot was migrated previously. N/A means the bot has not been migrated before.
    Bots tab
  7. Click Next.
  8. Select one or more usernames from the list to run the migration and click the right arrow.
    Usernames can display either the message Picked at run time or the device name in the Device column. A device name indicates the registered device for that user. Picked at run time is shown when a user does not have a default device, for example, a user who has not registered a device and a system administrator has assigned a device to that user. A default device must be configured for all Bot Runners you have selected.
    • Bots are distributed across selected Bot Runner users in a round-robin method.
    • The first Bot Runner user on the selected list is the first one used.
    • A parent bot and its dependencies are assigned to a single Bot Runner user.
    Select bot runners from the bot runner tab
  9. Click Next.
  10. Optional: Review the dependent Task Bots and MetaBots on the Bot and Dependent Bots page before you migrate them.

    If you have selected a folder and bots from the Bots page, that folder and dependencies of the selected bots are displayed in the table.

    Dependent bots (Task Bots and MetaBots) are migrated before the primary bot.
    The table shows the primary bot at the bottom and its dependencies above. For example, the following information means that Sample05.atmx has a dependency on Sample04.atmx, and Sample04.atmx has a dependency on MessageBox.atmx and MetaTask.mbot.
    Type Name Path
    MetaBot (mbot) MetaTask.mbot Bots\My Metabots\MetaTask.mbot
    Task Bot (atmx) MessageBox.atmx Bots\MyTasks\MessageBox.atmx
    Task Bot (atmx) Sample04.atmx Bots\MyTasks\Sample04.atmx
    Task Bot (atmx) Sample05.atmx Bots\MyTasks\Sample05.atmx
  11. Click Migrate bots.
    The system validates whether the user who initiated the migration and the Bot Runner users selected have the required permissions to perform the migration. The system verifies whether all of the following permissions are granted to the user performing the migration and the Bot Runners you have selected:
    • User performing migration:
      • View Migration permission
      • Manage Migration permission
      • Permission on the folders containing the bots and MetaBots you want to migrate
      • A role that has access to Bot Runners that you want to select for running the migration (on the Administration > Migration > Run As page)
      • View & edit ALL credentials attributes value permission
    • Bot Runners:
      • An unattended Bot Runner license
      • Autologin Set status
      • Allow a bot-runner user to run migrations permission
      • Create standard attributes for a credential permission
      • Create folder permission
      • View package permission
      • Register device permission
      • View my bots and Run my bots permissions
      • Check-in and Check-out permissions for the My Tasks and My Metabots folders in Automation 360
      • Default device settings
    If any of the required permission is not granted, the system displays those permissions in the validation results. You must grant the required permissions and start the migration process again.
    If all the required permissions are granted to the users, the system starts migrating the selected bots and their dependent bots.
    After the migration, the system uploads successfully migrated bots, the associated Bot Insight data, and the published dashboards to the public workspace of the Automation 360 Control Room (in the same folder in which the .atmx file is available). Only bot migrations initiated from the Control Room are stored in the public workspace.
    Validation error details for each bot are displayed in the bot migration results. The error details include the line number, error details, and the reason and recommendation.

    The Bot migration results display the number of bots migrated, along with their individual statuses. Click the Status column to filter bots with specific statuses for quick analysis.

    In the Reasons column, click the View Migration issues option to see detailed reasons for the error. The View Migration issues dialog box displays the line number where the error occurred, a summary of the error, and a detailed error report for your review.

    1. Check out the bot to migrate the private dashboards associated with that bot.
      The private dashboards are migrated only for the user who checked out the associated bot for the first time.
    2. View in-progress migration activities from the Activity > In progress page.
    Review dependencies for the selected bots and migrate bots
    See the following video on how to migrate Enterprise 11 or Enterprise 10 bots:

See the following resources if you encounter errors during migration:

Next steps

Verify the bot migration | View migration reports