Migrator/MigrateDashboards: License Consumption

⚠️ once a license is consumed, it cannot be reversed or restored processes cannot be un activated, and deleting an activated process does not release the license blueprint migrator blueprint migrator uses two distinct license types both are measured per main (see what counts as a main docid\ ytu76e7qocxu2dx1ec2 2 below) and both account for duplicates, so the same process is never charged twice license when it's consumed what it's for migrate dashboard automatically, on import migration specific dashboards, analysis, and estimation migration on export (or on manual activation prior to export) migrating a process from a source rpa platform to power automate desktop ⓘ migrate dashboard and migration are separate allotments consuming one does not draw down the other license types migrate dashboard license consumed automatically on import — no action required from the user powers migrator's migration specific dashboards, analysis, and estimation (for example, estimator dashboard) intended for scoping and effort estimation a migrate dashboard license does not allow a process to be exported to power automate desktop migration license consumed when a process is activated , which is what allows it to be exported to power automate desktop a process can be activated ahead of time — individually or in bulk — or, if it is not already activated, you will be given the option to activate at the point of export see activating processes docid\ ytu76e7qocxu2dx1ec2 2 below what counts as a main blueprint uses the term main to describe the unit that consumes a license — essentially the entry point of a call tree both license types are charged per main how the main is identified depends on your source tool uipath and blue prism both define a main programmatically , so the licensed unit is fixed by the platform a360 has no platform enforced main , so blueprint identifies it through dependency analysis uipath 1 uipath project = 1 main xaml = 1 migrator license blueprint reads the "main" attribute in project json to identify the licensed xaml — regardless of what the file is named invoked workflow xamls, config files, test cases, and other project files do not consume a license blue prism 1 blue prism process = 1 main page = 1 migrator license blue prism objects and additional pages within a process do not consume a license automation anywhere 360 (a360) a360 has no platform enforced entry point; blueprint uses dependency analysis to identify root task bots root task bots — task bots not called by any other process in the export — each consume 1 migrator license child task bots — task bots called by another process in the export — do not consume a license "bot" is an organizational label, not a platform concept your team may refer to a group of processes as one "bot" — but blueprint counts each licensed entry point individually a grouping of 3 root processes = 3 migrator licenses activating processes migrator licenses are consumed at the point of activation you can activate processes individually or in bulk note only "activated" processes can be exported to pad option 1 activate individually open a process in the process editor and click the activate button at the top of the page option 2 (recommended) activate in bulk on export select a project, folder, or process in the explorer select export in the top right of the main content area select export to power automate desktop in the dialog, select any processes you want to activate the dialog displays the number of licenses that will be consumed ⓘ if a single process is selected, it must be activated individually (option 1) before the export option becomes available option 3 activate in bulk via descendants view select a project or folder in the explorer click artifact editor in the top right and select descendants the contents of the selected project or folder are listed check the boxes for all processes you want to activate click actions > activate bots in the dialog, confirm the activation the dialog displays the number of licenses that will be consumed for license usage reporting, see license and activity reporting docid\ tiivvofat ccsyu2p3mmm