Migrator/MigrateDashboards: License Consumption

11 min

⚠️ 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 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 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.

"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

Open a process in the Process Editor and click the Activate button at the top of the page.

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.

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.

Migrator/MigrateDashboards: License Consumption

Blueprint Migrator

License Types

Migrate Dashboard License

Migration License

What Counts as a Main

UiPath

Blue Prism

Automation Anywhere 360 (A360)

Activating Processes

Option 1: Activate Individually

Option 2 (Recommended): Activate in Bulk on Export

Option 3: Activate in Bulk via Descendants View