Home
Get Community Edition - FREE
LOG IN
Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Bot migration package

  • Updated: 8/13/2021
    • Automation 360 v.x
    • Build
    • RPA Workspace

Bot migration package

The Bot migration package contains the Migrate bot action that enables you to migrate a bot (TaskBots and MetaBots) from Enterprise 10 and Enterprise 11 to Automation 360.

See Supported versions for migration.

Important: We recommend you to use the Bot Migration Wizard to migrate Enterprise 11 or Enterprise 10 bots to Automation 360.

The Bot migration package does not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot.

Action in the Bot migration package

The Bot migration package includes the following action:

Action Description
Migrate bot Migrates the Enterprise 11 and Enterprise 10 and bot file to Automation 360 format and uploads the migrated file to the specified location in your private repository with the same name as .atmx and .mbot file. This action only migrates the bot you specify, but does not migrate its dependencies. Dependencies are the bots and other files that are required to run the bot. You must migrate the dependent bots separately and upload other files manually to Control Room.
All the bots migrated using the Bot migration package are stored in the Bots folder in Automation 360. If you have migrate a parent bot and its child bots separately using the Bot migration package, you must create the same folder structure as in Enterprise 11 or Enterprise 10 and move the dependent bots to these folders for the parent bot to run successfully.
  • Use the Control Room file, Desktop file, or Variable tab to specify the location of the bot you want to migrate.
  • In the Output folder path field, specify the location where you want to save the log files generated for the bot migration.
    Note: Ensure that the location you have specified exists on the device.

    The system does not upload the bot if it fails during the migration process. The system creates an XML report at the same location that provides information that helps you to troubleshoot if the system encounters an error during migrating the bot file.

  • Select the Overwrite the file if exists check box to overwrite an existing bot file.
  • Set a time-out value for migrating the bots within the range of 3 through 90 minutes (default value is 90 minutes).

    If the migration of any specific bot is not completed within the set time, the bot will display a timeout message with the reason for the failure and the migration process will move on to the next bot.
Send Feedback