Read and Review Automation Anywhere Documentation

Automation 360

Close Contents


Open Contents

Prepare to manually migrate to Automation 360 On-Premises

  • Updated: 2021/11/02
    • Automation 360 v.x
    • Migrate
    • RPA Workspace
    • Process flow

Prepare to manually migrate to Automation 360 On-Premises

You can manually migrate from Enterprise 11 to Automation 360 On-Premises by creating users, roles, permissions, and other entities required by the migrated bots to run successfully.


  1. Ensure that you have completed the following tasks to check your readiness for migration

    Check migration readiness

  2. Ensure you have procured and activated your migration license.

    Get migration license

Recommended: Use the manual migration in the following scenarios:
  • You have an existing Automation 360 On-Premises instance and want to migrate your Enterprise 11 data.
  • When you want to migrate only bots and re-create all other Enterprise 11 entities such as users, roles, and credentials manually in Automation 360.
  • When you want to migrate only a few of the Enterprise 11 entities. For example, if you have 50 users and 10 user-defined roles in Enterprise 11 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.
  • When you want to migrate Enterprise 11 entities to Automation 360 using a freshly installed database and server.


  1. Install Automation 360 On-Premises:
    1. Ensure you meet the system requirements.
    2. Install Automation 360 On-Premises Control Room in custom mode to a staging environment.
      Installing Control Room using Custom mode
      Important: You must install Automation 360 with a new database.
  2. Create all the Enterprise 11 entities in Automation 360 On-Premises.
    For more information about the entities you must create, see Prerequisites for manual migration.
  3. Export all the bots and their dependencies that were created after Automation 360 was installed using Bot Lifecycle Management.
  4. Upload the bots to Automation 360 On-Premises.

Next steps

Prerequisite tasks for migrating bots

Send Feedback