Prepare for Enterprise 10 to Automation 360 On-Premises migration

Perform the tasks in this workflow to migrate from Enterprise 10 to Automation 360 On-Premises, including migration of your bots to Automation 360.

Prerequisites

Workflow map: You can also view this migration workflow in an interactive visual format by clicking the following schematic image:
10x-a360-onprem schematic mapMigrating from Enterprise 10 to Automation 360 On-Premises
  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

Note: Install Automation 360 on a separate server to ensure that your Enterprise 10 environment is not impacted by the migration activities.

Procedure

  1. We recommend that you create a backup of the Enterprise 10 database and restore it in the same or different SQL instance to avoid failure of any automation task that is using the Enterprise 10 database.
  2. Ensure that all the credential variables used in the Enterprise 10 bots are available in the Enterprise 10 Control Room.
  3. 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.
    3. Configure the same authentication in Automation 360 as in Enterprise 10.
      Do not switch authentication types between Enterprise 10 and Automation 360. For example, if Active Directory is set as authentication in Enterprise 10, you must configure Active Directory as authentication in Automation 360 as well.
  4. Copy the Enterprise 10 data to Automation 360.
  5. Create the AAApplicationPath global value in Automation 360 and set the same value as Enterprise 10.
  6. Complete the pre-migration tasks.

Next steps

Migrate Enterprise bots