Blueprint FAQ
GeneralGeneral
DeploymentDeployment
Products & LicensingProducts & Licensing
Generative AIGenerative AI
Migration SupportMigration Support
PAD Code CompletionCompleting PAD Code
General
Blueprint is a software tool purpose-built to support and accelerate migrating from legacy RPA tools to Microsoft Power Automate Desktop (PAD), as well as managing a PAD automation estate at scale. It offers three products:
- MAP (Migration Analysis & Planning) analyzes an existing RPA estate to generate effort estimates, complexity insights, and migration sequencing recommendations before conversion begins.
- Blueprint Migrator converts automations from UiPath, Automation Anywhere A360, and Blue Prism into PAD flows algorithmically, reducing the time and manual effort required for migration.
- ALC (Automation Lifecycle Control) governs PAD flows across their full lifecycle — from ideation and build through operation and retirement — providing visibility into flow health, quality, and change history.
See Change Your Password.
Deployment
Both options are supported. Blueprint can be deployed as a cloud-hosted service or installed on-premise.
Yes. Cloud-hosted deployments offer significant long-term advantages — including reduced infrastructure overhead, faster access to updates, and lower operational maintenance burden — that outweigh the upfront approval effort.
Products & Licensing
Blueprint licenses three products:
MAP (Migration Analysis & Planning) — Analyzes and estimates an RPA migration to PAD before conversion begins. Used to assess your automation estate, generate effort estimates, identify complexity, and prioritize migration sequencing. Often referred to as an assessmentmigration assessment.
Migrator — Converts automations from legacy RPA tools — UiPath, Automation Anywhere Automation360, and Blue Prism — to Microsoft Power Automate Desktop (PAD). Handles code conversion algorithmically, resolving actions, subflows, variables, and dependencies to produce PAD flows.
ALC (Automation Lifecycle Control) — Governs and improves PAD flows across their full lifecycle — from initial ideation and build through to operation and retirement. Provides visibility into flow health, change history, and quality, enabling teams to manage their PAD automation estate at scale.
Each product is licensed separately. You purchase a set number of Bot licenses, and each Main within that Bot that you work with consumes one license.
- MAP: Licenses are consumed upon import.
ⓘ MAP Example: If you purchase 25 licenses, you can assess 25 automations. Assessing additional automations requires purchasing additional licenses.
- Migrator: Licenses are consumed upon conversion (export).
ⓘ Migrator Example: If you purchase 10 licenses, you can convert the code of 10 automations. Converting additional automations requires purchasing additional licenses. Re-converting the same automation — for example, with different Blueprint tool conversion settings — does not consume additional licenses, provided the source automation code remains unchanged.
- ALC: Licenses are concurrent.
ⓘ ALC Example: If you purchase 5 licenses on a 1-year term, you can work with up to 5 PAD flows in ALC at any one time. You can change which flows are active throughout the year, but the maximum concurrent count is fixed at 5.
Licenses are consumed per Main. How Mains are counted varies by source platform:
- UiPath: Each project includes a Main.xaml file. The total Main.xaml count equals the license count.
- Blue Prism: Each process contains one Main page. The total Main page count equals the license count.
- Automation Anywhere A360: A360 does not define Mains in its architecture. Blueprint counts root Task Bots as Mains.
A bot is the root entry point of an automation and everything it calls during execution — its full call tree or dependency tree.
RPA Platform | A Bot maps to... |
|---|---|
UiPath | The Main .xaml in a Process, plus all referenced .xaml files |
Blue Prism | The Main page in a Process, plus all referenced process and object pages |
Automation Anywhere 360 | A root Task Bot (not called by any other bot), plus all referenced Task Bots |
Power Automate Desktop | A desktop Flow |
A main is the only root entry point of an automation — it is where execution begins and does not include the full call tree or dependency tree. The term varies by platform:
RPA Platform | A main maps to... |
|---|---|
UiPath | The main .xaml in a Process |
Blue Prism | The main Page in a Process |
Automation Anywhere 360 | A root Task Bot (not called by any other bot) |
Power Automate Desktop | The main subflow of a desktop Flow |
No, there are no user limits in any Blueprint tool.
Yes. There are technical limits on data volume as follows:
- Migrator: PAD limits flows to a total of 1 million characters. Blueprint provides features to help split automations that exceed this threshold into multiple PAD flows.
- Migrator & MAP:
- There is a limit of 100,000 actions per project. If you exceed this during import, create a new projectcreate a new project to continue.
- Imported RPA files are subject to a 50MB compressed file size limit. This is rarely encountered and is usually caused by embedded images, which Blueprint does not require. To resolve: decompress the file, remove all images, then recompress before importing into Blueprint.
See License and Activity ReportingLicense and Activity Reporting.
No. Blueprint detects previously imported identical components and flags them as duplicates. Duplicates are excluded from license consumption and separated out in Dashboards & ReportsDashboards and Reports.
When remaining licenses fall below approximately 20% of the total purchased, Blueprint displays a warning during activation to prompt users to procure additional licenses. Contact Blueprint SupportBlueprint Support or your Success Manager for assistance.
When a user attempts to import or activate processes that require more licenses than are available, Blueprint returns an error. Additional licenses must be procured to continue. Contact Blueprint SupportBlueprint Support or your Success Manager for assistance.
Contact your Blueprint Sales Representative, your Success Manager or Blueprint Support.
Generative AI
Yes. This requires a small amount of development work by Blueprint. You will need to provide a technical specification for your in-house GenAI solution so we can build the appropriate connector. Contact your Success Manager for more information.
Blueprint uses OpenAI. GenAI capabilities are bundled as part of the product license — you do not need to provide your own OpenAI account.
No. See the General FAQ and Model Training FAQ sections of OpenAI Enterprise Privacy.
It depends on the product.
Product | Uses GenAI | Details |
|---|---|---|
MAP | ✅ | Uses GenAI for its Analyze capabilities — the features that interpret and describe source RPA code. The migration-specific analysis capabilities in MAP do not use GenAI. |
Migrator | ✖️ | Does not use GenAI. |
ALC | ✅ | Uses GenAI for most, but not all, of its features. |
GenAI can be disabled across all products by an administrator using a single setting. See GenAI Settings for details.
Migration Support
To learn more about Migration Output in PAD, please see Why Migrated Flows Look Different in PAD.
- UiPath (including UiPath StudioX)
- Blue Prism
- Automation Anywhere Automation360
Blueprint's conversion logic is largely algorithmic rather than table-based, which means whether a specific action — with its associated parameters and settings — converts is determined when the algorithms run against your actual data. To get a precise picture for your automation estate, import your RPA data into Blueprint and generate the conversion reports. These will show exactly what converts and what does not for your specific dataset.
For most datasets, Blueprint achieves a conversion rate above 95%.
UiPath Custom Actions can be built using low-code (e.g. UiPath Studio) or pro-code (e.g. C#). Blueprint handles each case as follows:
- Low-code custom actions: Blueprint converts the custom action code to a PAD flow.
- Pro-code custom actions: The developer will need to re-create the action in Power Platform. However, Blueprint resolves all usages of that custom action across the automation estate, so no manual work is required for each call. Note that if there are any pro-code custom actions in your data they are shown in the Custom Actions tab of rules after you generate rules. Refer to Using Rules
In the case of Custom VBOs the code within the VBO action itself is converted to PAD actions. Blueprint converts calls to standard VBOs into PAD actions. When Blueprint detects that a standard VBO has been extended:
- Actions that have not been modified are converted to PAD actions.
- Actions that have been modified or added are converted to PAD flows or subflows.
In Blue Prism libraries are essentially VBOs. Standard VBOs are converted directly to PAD actions. Where custom actions have been created, which is the case for extended standard VBOs or custom VBOs, Blueprint will convert those actions at every point they are called, or you can make the equivalent of a reusable library by using Blueprint's "Export as VBO" feature. Refer to Exporting Libraries as Reusable Flows
In UiPath libraries can be created using lo-code (Studio) or pro-code (e.g. C#). Those created using pro-code will appear as Custom Actions in Blueprint rules where you choose the mapping approach using a Rule. Refer to Map Custom Actions. For those created using lo-code Blueprint will convert the workflows to PAD subflows in every flow created, or you can make the equivalent of a reusable library by using Blueprint's "Export as Library" feature. Refer to Exporting Libraries as Reusable Flows.
No. Feature differences between source and target RPA tools mean bots will not be fully migrated. Developer code completion work is required before migrated bots are production ready.
Migrated bots aim for functional equivalence but will require post-migration completion work before they are production ready. Platform differences between source and target RPA tools mean one source action may expand into multiple PAD actions to preserve the intended behavior. Blueprint offers Rules and supports AsEnumerable and XmlDocument mappings, mid-value wildcard matching, and region-based image selectors to improve fidelity and reduce manual fixes. Blueprint also embeds comments into the PAD code to help you complete them.
Blueprint adds code to preserve functional equivalence between source and target RPA tools. One source action may require multiple PAD actions to behave the same way.
Ex: An action in UiPath may need to be migrated as many actions in PAD in order to function similarly.
Where no combination of standard PAD actions can replicate the source logic — or where the result would be overly verbose — Blueprint may use a .NET script instead.
Blueprint also adds optional elements such as TODO comments, Regions, and Logging. These can be toggled off in Migration Preferences if they're not required for your migration.
Blueprint offers the option on export to utilize PAD local variables. If you decide not to use local variables, Blueprint simulates scope and prevents variables from colliding or overwriting one another by adding prefixes to variable names per subflow. Variable prefixing is configurable — See Variable Prefixing for more details.
PAD handles variable typing at runtime and supports a core set of datatypes. Blueprint maps or converts others as needed. Collection data migrates via AsEnumerable support, converting lists into PAD datatables. XML payloads use native XmlDocument support. Both reduce manual datatype adjustments while preserving bot behavior.
By default, Blueprint inlines subflows that are called only once or are very short — these will appear embedded within their parent flow in PAD rather than as separate subflows. To locate inlined logic or adjust this behavior:
Verify your Export Wizard OptionExport Wizard Options selections
Check the RPA Import LogRPA Import Log in your project folder for import failures. The log file is appended with an asterisk (*) when a problem is encountered during import. Failures appear at the top of the log.
Use Bulk Reimport and Recalculate to force a fresh migration of chosen processes.
In Export Wizard OptionsExport Wizard Options, change your Call or Embed Settings from System Recommended to Call Everything to prevent inlining and keep all subflows discrete
Resolving TODOs and Compiler Errors will make your migrated code functionally complete and compilable, but runtime validation is still required. Selectors in particular often need to be reviewed, retested, and re-spied against your target applications after an initial test run — Blueprint cannot validate selectors during migration because we do not have access to your applications. Other runtime errors may also surface during testing. Contact Blueprint Support for assistance with any post-migration issues.