Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Recommended workflow for Cloud migration

  • Updated: 7/22/2021
    • Automation 360 v.x
    • Explore
    • RPA Workspace

Recommended workflow for Cloud migration

Review the process of how Enterprise 11 data is migrated to Automation 360 Cloud, particularly when you maintain separate development, testing, and production environments.

Important: This is the recommended workflow for migrating from Enterprise 11 to Automation 360 Cloud.

In some scenarios, there might be separate Enterprise 11 environments for development (Dev), testing (UAT), and production (Prod) based on the requirements and each of these environments might have multiple Control Room instances. The number of Cloud Control Room licenses you request must be the same as the total number of Control Room instances in all of your Enterprise 11 environments. For example, if you have separate environments for Dev, UAT, and Prod, and each of these environments has two Control Room instances, you must request six Cloud Control Room licenses.

When you migrate from Enterprise 11 to Automation 360 Cloud, you must copy all the bots from the production and testing environments to the development environment using Bot Lifecycle Management. This ensures that all new or modified bots available in the production and testing environments are available in the development environment before you start the migration process.

The following image shows the Enterprise 11 to Automation 360 Cloud migration workflow:

Cloud migration workflow

  1. Optional: Copy bots from the Enterprise 11 Prod environment to the Dev environment using Bot Lifecycle Management.

    Bot Lifecycle Management (BLM) - an overview

  2. Optional: Copy bots from the Enterprise 11 UAT environment to the Dev environment using Bot Lifecycle Management.

    Bot Lifecycle Management (BLM) - an overview

  3. Analyze your bots and identify commands and variables used in the bots that are supported for migration to Automation 360.

    Scan bots using Bot Scanner | Analyze reports

  4. Upload Enterprise 11 data to Dev Cloud Control Room using the Cloud Migration Utility.

    Install Cloud Migration Utility | Upload Enterprise 11 data using Cloud Migration Utility

  5. Upload Enterprise 11 data to UAT Cloud Control Room using the Cloud Migration Utility.
  6. Upload Enterprise 11 data to Prod Cloud Control Room using the Cloud Migration Utility.
  7. Complete the following steps on Automation 360 Cloud Dev environment:
    1. Convert the bots (TaskBots and MetaBots) in .atmx and .mbot format to the .bot Automation 360 format using the Bot Migration Wizard.
    2. Copy the converted bots to the Automation 360 Cloud UAT environment using Bot Lifecycle Management.

      Bot Lifecycle Management

    3. Test the converted bots in the Automation 360 Cloud UAT environment.

      If any of the migrated bots are not working as expected and require some modification, move such bots to the Automation 360 Cloud Dev environment.

      After the bots are modified, move them to Automation 360 Cloud UAT environment for testing. Repeat this process until all of the migrated bots work as expected.

    4. After all the converted bots are tested and work as expected, copy these bots to the Automation 360 Cloud Prod environment.
Send Feedback