Current RPA estate
Choose the source platform, enter the licenses in your contract, then list the automations that are in migration scope.
UI
UiPath
Enterprise / Pro
BP
Blue Prism
Digital Workers
AA
Automation Anywhere
A360 / Enterprise
Enter licensed attended users or runners, not the number of automations.
A single license may run several automations depending on your platform and schedule.
Migration scope by complexity
Enter the automations that need to be migrated. This is separate from license count because one license can cover multiple bots or jobs depending on runtime and scheduling.
Simple
~20 days/bot
Simple automations
API-based, linear logic, 1–2 apps, no Citrix/VDI, minimal exception handling, straightforward UI interactions.
Medium
~35 days/bot
Medium automations
UI-driven across 3–5 apps, moderate exception handling, some custom code, orchestration logic or conditional branching.
Complex
~45 days/bot
Complex automations
Citrix/VDI-dependent, 6+ app integrations, heavy exception handling, reusable component libraries, SAP or mainframe.
0 bots are included in the migration effort estimate. License counts above are used only for platform cost modeling.
Current Licensing Costs
Review how we've estimated your current costs based on your inputs, then adjust if needed.
Source platform license estimate
Select a platform on the previous step
Complete Step 1 to see your pricing breakdown.
Enterprise contracts typically carry 15–35% off list price
Servers, cloud VMs, or hosted environment for running bots
VM count helper
Estimate infrastructure from virtual machine count and monthly run cost.
Use VM helper for infrastructure cost
Annual infrastructure becomes VMs x monthly cost x 12.
Estimated infrastructure: $6,000 / year
Power Automate target pricing
Edit target platform rates before the server calculates future TCO.
0 attended licenses
5 unattended licenses
Connection, machine registration, and operator coverage
Power Automate Process covers unattended run capacity. Unattended desktop flows still need a Premium user for the connection, machine registration, and operational ownership.
Optional architecture note: Microsoft Hosted Process can reduce VM infrastructure further by using Microsoft-hosted machines, but it is not included in this default ROI calculation to keep the license model simple.
Yes — automations process documents such as invoices, forms, claims, or PDFs
We will estimate Copilot Credits, monthly pack cost, and annual Microsoft document AI cost from your document volume.
Document processing comparison
Current document processing cost vs Power Automate equivalent
Current tool cost
$0/year
Enter your annual document processing, OCR, or extraction cost below. Use 0 if it is bundled or unknown.
Annual document volume
60,000 pages/year
Calculated from monthly pages or documents. Use the same unit you use for your current tool.
Credits required
40,000/mo
Estimated from Microsoft content processing rate of 8 Copilot Credits per page/image.
Estimated Microsoft AI cost
$60,000/year
$400/month equivalent
Microsoft AI / Copilot Credits estimate
The calculator estimates required credits and monthly capacity packs from document volume. Validate final pricing with Microsoft or your CSP.
Credits per page
8
Capacity pack size
25,000/mo
Pack price
$200/mo
Estimated monthly cost
$0
Seeded AI Builder credits remain usable only until November 1, 2026. For new ROI estimates, this model uses Copilot Credits capacity packs instead of asking the user to know the credit requirement.
Operational Costs
RPA savings go beyond licensing — ongoing maintenance and developer costs are a significant but often overlooked component.
Benchmark insight: Power Automate Desktop bots typically require 30–50% less maintenance than legacy RPA platforms due to native Microsoft 365 integration, automatic cloud updates, and built-in monitoring. We model a conservative 35% reduction.
Hours/month spent fixing, updating, and monitoring bots
Average fully-loaded cost per hour for RPA developers/admins
Full-time headcount dedicated to platform support, governance, and automation operations
Reference annual operations cost. Report operations line uses automation effort x 8 hours x blended FTE rate.
Migration Planning
Set your migration day rate and review the effort estimates for the bots you entered in the complexity breakdown. License counts are not used for migration effort.
Default consulting rate used for migration cost: total effort days x $300/day
Calculated from simple + medium + complex automations in Step 1
Effort per automation
Simple
2 automations in scope
API-based, linear logic, minimal UI interaction, 1–2 apps. Includes design, build, test, and UAT sign-off.
Total: ~26 days incl. UAT
Medium
2 automations in scope
UI-driven, 3–5 apps, moderate exception handling and orchestration logic. Includes full testing cycle.
Total: ~46 days incl. UAT
Complex
1 automations in scope
Citrix/VDI, 6+ apps, SAP/mainframe integration, reusable libraries, heavy exception handling framework.
Total: ~59 days incl. UAT
Testing & UAT overhead is added automatically at 30% on top of development effort — covering integration testing, parallel running, and business sign-off. This is already reflected in the "Total" hints above.
Acceleration option: Fusion Dev's RPA analyzer, AI-assisted assessment approach, and reusable Power Automate migration patterns can help validate scope and compress planning compared with a fully manual migration assessment.
Executive preview
Initial migration business case
A board-ready snapshot based on your estate, licensing, operations, and migration assumptions.
—
Payback Period
months to break-even
—
3-Year Net Savings
after migration cost
—
Annual Cost Reduction
vs current platform
Executive summary
Cost analysis
ROI projection
Migration roadmap
Assumptions
Recommendations
ROI report
—
—
Business case status
Calculated case
Review the model assumptions before sharing externally.
Business case
ROI decision summary
Executive decision summary
Calculated from your current assumptions
Payback Period
—
months to break-even
3-Year Net Savings
—
after all migration costs
Annual Cost Reduction
—
vs current platform
Migration Cost
—
effort days x day rate
Investment vs savings
Business case comparison
Complete the calculation to compare migration cost against expected savings.
Payback visual
Break-even confidence
—
0 mo12 mo24 mo36+ mo
Lower payback periods indicate a stronger near-term business case.
Operational impact
Areas to validate beyond licensing
Lower run costReduced infrastructure and support effort through Microsoft-native automation.
Governance alignmentPower Platform admin, DLP, environment strategy, and maker controls in one operating model.
Faster change cyclesCloser fit with Microsoft 365, SharePoint, Teams, Dataverse, and Azure workflows.
3-Year Cumulative Cash Flow
Break-even point — net savings after migration cost
Annual TCO: Current vs Power Automate
Stacked by cost component (USD/year)
Cost Savings Waterfall
Where the savings come from
Migration Scope by Complexity
Migration effort by tier
Detailed Cost Breakdown
Line-by-line annual costs — current platform vs Microsoft Power Automate
| Cost Component | Current Platform ($/yr) | Power Automate ($/yr) | Annual Saving |
|---|
Estimated Migration Timeline
Wave-based approach grouped by automation complexity tier
Assumptions & Methodology
All figures are directional estimates based on 2026 published list prices (pre-negotiation). Actual savings depend on your specific contract, negotiated discounts, and bot complexity.
Validate this before budget approval
Use this as a first-pass business case. A Fushion Dev assessment can validate automation complexity, migration waves, licensing assumptions, and project effort before the estimate is shared with leadership.
Disclaimer: This calculator uses 2026 published list prices for UiPath (Enterprise), Blue Prism, and Automation Anywhere as reference points. Real enterprise contracts are custom-negotiated and typically include discounts. Power Automate pricing is subject to Microsoft's current terms. All figures are illustrative estimates only. Fushion Dev Consulting accepts no liability for decisions made based on this tool's output. Always obtain formal vendor quotes before committing to a migration programme.