Metabot Migration - Best Practices
In this article we'll be going over the best practices when migrating metabots from AAv10/AAv11 to Power Automate Desktop.
Metabots can be migrated in two different ways:
- (Recommended) Metabot Logic can be migrated separately to become their own Power Automate Desktop Flows. This decreases the amount of redundant subflows across an automation estate, and makes it easier to manage and reuse the original Metabot logic.
- Metabot Logic can be migrated as dependencies of .atmx files. When that happens, Metabots will migrate as subflows in Power Automate Desktop
If users decide to migrate Metabot Logic as separate Power Automate Desktop Flows, Blueprint offers the ability to map calls to metabots to preexisting Desktop flows using our Framework Mapping - AA Metabots Sheet. After the sheet is filled out, all processes calling the Metabot turned Power Automate Desktop Flow will have the proper Run Desktop actions instead of a TODO comment.
- Migrate all Metabot Logic to PAD as separate Desktop Flows.
- This process can either be done manually, or with Blueprint's migration utility. We recommend migrating using Blueprint, as any logic or commands within the metabot will migrate to PAD similar to a taskbot. Many Metabots from Automation Anywhere contain DLLs, which currently are not supported by Power Automate Desktop. These DLLs will migrate as TODOs and will need to be refactored manually
- This process can either be done manually, or with Blueprint's migration utility. We recommend migrating using Blueprint, as any logic or commands within the metabot will migrate to PAD similar to a taskbot.
- Export the prepopulated Metabot Mapping sheet. This will fill automatically fill out all columns relating to calling the Automation Anywhere metabot for all metabots called in the selected scope of the Statistics Dashboard.
- Resolve any TODOs or compiler errors
- Currently, all variables migrate as Flow variables in PAD. Users will need to move Input/Output Variables from Flow Variables to the Input/Output Variable section in PAD.
- Follow the instructions on the Framework Mapping - AA Metabots Sheet to fill out and upload the Metabot Mapping Sheet