Migration Estimate Guide

migrating your rpa estate to microsoft power automate desktop is a multi step process blueprint supports every phase — from collecting your source automations through delivering a migration estimate to stakeholders collect your automation estate — export your automations from your source rpa platform import into blueprint — bring your estate into blueprint and populate dashboards automatically analyze the estate — use blueprint's dashboards and reports to understand size, complexity, and dependencies before committing to a plan build your estimate — run the estimator to calculate migration effort, blueprint time savings, and remaining work deliver the plan — export and present your estimate using blueprint's reporting and dashboard tools step 1 collect your automation estate before importing into blueprint, export your automations from your source rpa platform each platform exports to a specific file format that blueprint can ingest for export instructions by platform, see exporting source rpa files docid\ cyhzzmddxkxcgp5h gmbi step 2 import into blueprint once your automation files are collected, import them into blueprint dashboards and reports populate automatically upon import for import instructions, see importing rpa files to migrator docid\ td9tcfofalwo0p8mvj0is ⚠️ if you plan to generate an assessment report docid\ ap78dzb10ftoym9p4eta1 , enable also import to analyze during import — this cannot be applied retroactively step 3 analyze the estate with your estate imported, use blueprint's dashboards and reports to understand what you're working with before building an estimate key resources statistics dashboard docid\ f7eiz jmxcz0dxgc7lqeg estate wide size and complexity metrics statistics reports docid\ kzwljtmy cqxoubi dxx9 per process breakdown of actions, commands, variables, and complexity applications dashboard docid\ skqsvaklm8s0wmibnyiqe application interactions across the estate applications report docid 15eoozwvo8 bkyv6fbifu process level application drill down missing processes report docid 5v56vfblaxvvhidurtnsx processes being called that weren't included in the import reuse report docid 5vlyxagygif 9clrikb4m components called multiple times across the estate mains report docid 4ew9bvp1kmxhbsbfkocb5 call tree level aggregate metrics assessment report docid\ ap78dzb10ftoym9p4eta1 a comprehensive pre migration report that draws data from migrator and analyze to produce a complete picture of your rpa automations step 4 build your estimate the estimator dashboard simulates a pad export for your scope and produces the three figures you need for a migration proposal how long manual migration would take, how much effort blueprint saves, and how much work remains after blueprint converts the code the dashboard presents these as two estimates side by side without blueprint (manual rewrite) and w ith blueprint (automated conversion) — along with hrs saved and % faster indicators adjust parameters all productivity rates used in estimator calculations are adjustable directly on the dashboard to reflect your organization's actual velocity as you change any rate, the estimates, the hrs saved and % faster indicators, and the effort breakdown update in real time manual migration effort how long it would take a developer to manually rewrite the estate in pad without blueprint shown under without blueprint , it is the total actions in scope divided by your team's manual rewrite speed (actions/hr, default 10) total actions ÷ actions per hour = hours of manual effort adjust actions/hr to match the realistic speed at which your team can manually rewrite source actions in pad example 7,039 total actions ÷ 10 actions/hr = 703 9 hours of manual effort blueprint time savings how much effort blueprint eliminates through automated migration shown under with blueprint , the estimated completion effort is the total remaining work after blueprint converts the code — the sum of the effort breakdown below blueprint compares this to the manual rewrite baseline and displays the hrs saved and the % faster manual migration effort − estimated completion effort = hrs saved use the team size selector (1, 2, 3, 5, or 5+) to spread the completion effort across your team this does not change the total hours; it produces the estimated calendar time, shown as an approximate number of weeks remaining work to complete migrated code after blueprint converts the code, some manual work remains in pad the effort breakdown divides this into three categories, each calculated as its item count divided by an adjustable fixes/hr rate (default 5) todos — items flagged with blueprint todo comments that a user must address to make the bot production ready compiler errors — errors in the generated pad code that must be resolved for the flow to compile selectors — ui selectors that may need attention after migration for more information on estimator dashboard, see estimator dashboard glossary docid\ urfvridoikrtnatax6i v step 5 deliver the plan with your estimate built, blueprint provides tools to package your findings into a client ready deliverable — from a scoped excel workbook to multi project consolidated reports and custom dashboards export your estimate to excel the dashboard estimate in step 4 gives you a fast, easy to calculate estimation the estimator template to excel template is a substantially more detailed and accurate estimation — a line item workbook with contingency factors, per tool complexity classifications, adjustable per category productivity, and full cost modeling it's the version built for high accuracy, client facing proposals, and it goes well beyond what the preceding step can produce from the estimator dashboard , open the actions dropdown and select export estimator template to excel this generates a pre built workbook designed for client facing migration proposals the template includes instructions — guidance for using and customizing the workbook estimate with categories — primary estimation workspace; edit white background cells to adjust values; summary aggregates data across all sheets to calculate total project time and cost ref constants — list of supported source rpa tools; no edits needed ref contingencies — apply contingency factors for variables known to influence productivity rate; assign weights and scores to adjust the estimate with categories output ref bot classifications tables — define complexity criteria (low / medium / high / very high) per source rpa tool; affects time calculations in estimate with categories drv work — todo and compiler error types in the selected scope with adjustable productivity metrics per category drv bot classification — complexity criteria definitions per rpa tool bp bot metrics — metrics for each bot in scope; read only bp estimate data todos — all todos for the scope; read only bp estimate data cerrors — all compiler errors for the scope; read only ⓘ any cell with a white background can be edited navigate to the jobs page and click the download icon on the right side of the row ( ) when the export is ready reporting across multiple projects if your client's estate spans more than one blueprint project, use bulk reporting docid\ ilvvabzt0qysp86rotpxk to generate consolidated statistics and estimator reports across up to 10 projects simultaneously — rather than running and combining reports manually per project