Prepare for migration when using Enterprise 10 and Automation 360 On-Premises in parallel

Perform the tasks in this workflow if you want to use both Automation 360 On-Premises and Enterprise 10 in parallel. You can continue to use both environments till the time you are ready to start the migration from Enterprise 10 to Automation 360 On-Premises.

Prerequisites

  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: Create a new environment for migration to Automation 360 to avoid any issues to your existing bots because of migration activities.

Procedure

  1. We recommend that you create a backup of the Enterprise 11 database and restore it in the same or different SQL instance to avoid failure of any automation task that is using the Enterprise 11 database.
    Quickstart: Back up and restore a SQL Server database on-premises
  2. Ensure that all the credential variables used in the Enterprise 11 bots are available in the Enterprise 11 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.
  4. Complete the pre-migration tasks.
    Pre-migration tasks
  5. Create the AAApplicationPath global value in Automation 360 and set the same value as Enterprise 10.
    Variable mapping for migration
  6. Copy the Enterprise 10 data to Automation 360.
    Copy Enterprise 10 data
  7. Continue using both Enterprise 10 and Automation 360 environments in parallel.
    Note: Create all new bots and entities such as users, roles, and schedules in Automation 360.
  8. If you create any new entity such as users, roles, schedules, and bots in Enterprise 10 after installing Automation 360, create the same entity in Automation 360.
  9. When you are ready to use only Automation 360 as your production environment:
    If you have created new bots or updated the existing ones in Enterprise 10 after installing Automation 360, based on your environment, follow these steps:
    • Applies from v.24 onwards:
      1. Export all the bots and their dependencies that were created after Automation 360 was installed using the export utility.

        Migrate new or updated Enterprise 10 bots to Automation 360

      2. Import all the bots to Automation 360 using Bot Lifecycle Management.

        Import bots

    • Applies to v.23 and previous versions
      1. Copy all the bots and their dependencies from Enterprise 10 by using the Copy 10.x data option in the Automation 360.
      2. Login as the Bot Creator to upload the bots and their dependencies to the Automation 360 private workspace. Note that the folder structure of the bots and their dependencies must be same as that of version Enterprise 10.
      3. Check in the bots to the public workspace.

Next steps

Migrate Enterprise bots