--- title: Migration Estimate Guide slug: blueprint/migration-estimate-guide docTags: yO7XZ9PJxDCKZ-Mf4TSYB createdAt: 2026-05-24T16:29:04.219Z --- :::CtaButton{label="๐ŸŸข Migrator" openInNewTab="false"} ::: 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. ::::WorkflowBlock :::WorkflowBlockItem **Collect Your Automation Estate** โ€” export your automations from your source RPA platform ::: :::WorkflowBlockItem **Import Into Blueprint** โ€” bring your estate into Blueprint and populate dashboards automatically ::: :::WorkflowBlockItem **Analyze the Estate** โ€” use Blueprint's dashboards and reports to understand size, complexity, and dependencies before committing to a plan ::: :::WorkflowBlockItem **Build Your Estimate** โ€” run the Estimator to calculate migration effort, Blueprint time savings, and remaining work ::: :::WorkflowBlockItem **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). :::hint{type="warning"} โš ๏ธ 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\:j0ZT32zTLIwXZdIAI_qra) - estate-wide size and complexity metrics - [Statistics Reports](docId\:KZwlJtmY-cQxOuBI-dXX9) - per-process breakdown of actions, commands, variables, and complexity ::embed[]{url="https://www.youtube.com/watch?v=EdchepWvcUk" indent="1"} - [Unresolved References](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): :::BlockQuote **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**: :::BlockQuote **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 :::Iframe{iframeHeight="0" code=" "} ::: 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 :::hint{type="info"} โ“˜ 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 (:inlineImage[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/MtvNZmEX21pPFD8xlaFyD_screenshot-2024-10-14-141050.png" alt caption width="18" height="17"}) 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.