Migrating from UiPath to Power Automate is worth it when your organization already runs on Microsoft 365 and Azure and your UiPath renewal is climbing faster than the value the bots return. The move typically cuts RPA licensing by 40-50% for Microsoft-centric shops, but there is no button that converts a UiPath project into a Power Automate flow - you are redesigning automations, not porting them, so the real work is process reassessment, not code translation.

This guide is written for IT directors, automation leads, and finance owners who are staring at a UiPath renewal and asking whether Power Automate can carry the same estate for less. It gives you the honest cost math, the technical gotchas, a phased migration plan, and a clear test for which bots should move and which should stay.

Key Takeaways

• The savings are real but not automatic: Microsoft-centric organizations commonly cut RPA licensing 40-50% by consolidating UiPath onto Power Automate, because much of the platform is already bundled with existing Microsoft 365 and Azure agreements.
• There is no lift-and-shift: No mature tool converts UiPath XAML directly into Power Automate flows, so every automation is re-architected - VB.NET expressions become Power Fx, and UI selectors become native connectors where possible.
• Power Automate RPA is licensed by mode: attended desktop RPA rides on the $15/user/month Premium license, while unattended bots need the $150/bot/month Process plan or $215/bot/month Hosted Process.
• Phase it, do not flip it: Successful migrations move process-by-process through discovery, a pilot, and staged conversion - not a single cutover - to keep business operations running.
• Not every bot should move: Brittle UI-scraping bots are candidates for redesign as API-first integrations, and some belong on Copilot Studio agents rather than a like-for-like RPA rebuild.

The short answer: should you migrate from UiPath to Power Automate?

Migrate if three things are true. First, you are already paying for Microsoft 365 and Azure, so Power Automate's cloud flows and attended RPA are partly sunk cost. Second, your UiPath renewal - commonly $60,000 to $100,000 or more per year for enterprise licensing - is outpacing the measurable return from your bots. Third, your automation estate is dominated by rules-based, Microsoft-adjacent processes rather than deep, high-throughput UI automation on non-Microsoft systems.

Hold or go hybrid if your estate leans on high-volume, latency-sensitive unattended automation, complex orchestration UiPath handles natively, or specialized UiPath capabilities you would have to rebuild from scratch. The decision is rarely all-or-nothing - most enterprises migrate the majority of a portfolio and leave a minority in place.

• Strong fit to migrate: Microsoft 365 and Azure tenant, rules-based approvals and data movement, moderate bot volumes, appetite to consolidate vendors.
• Proceed with caution: Heavy unattended throughput, deep non-Microsoft UI automation, tight SLAs, large libraries of custom UiPath components.

How much does Power Automate cost compared to UiPath?

The savings come from two places: Power Automate's list pricing is lower per bot, and much of the digital-process-automation layer is already included with Microsoft 365. Microsoft's published Power Automate pricing is the anchor for any business case, and it is structured by automation mode rather than by seat alone.

Power Automate RPA licensing at a glance

Power Automate Premium

• Price: $15 per user per month, billed annually.
• What it covers: Cloud flows, premium connectors, and attended desktop RPA for an individual user.

Power Automate Process

• Price: $150 per bot per month, billed annually.
• What it covers: Unattended RPA and cloud flows tied to a single automation, not a person.

Power Automate Hosted Process

• Price: $215 per bot per month, billed annually.
• What it covers: Unattended RPA on a Microsoft-hosted machine, so you do not manage the VM infrastructure.

Add-ons stack on top. Power Automate add-ons cover extra capacity, AI Builder credits, and storage, and Process Mining is a separate tenant-level add-on that runs around $5,000 per tenant per month. The headline savings are credible - one published migration found UiPath attended and unattended licenses cost roughly 8.9x and 5.6x more than the Power Automate equivalents - but they only materialize after you right-size how many unattended bots you actually need.

Can you convert UiPath XAML to Power Automate automatically?

No. This is the single most important expectation to set before a project starts. UiPath workflows are authored in XAML with VB.NET or C# expressions, and Power Automate desktop flows use a different action model with Power Fx. There is no reliable direct XAML-to-flow converter, so a migration is a redesign, not a translation.

Practically, that means each automation is re-implemented: UI selectors are re-mapped, expression logic moves from VB.NET to Power Fx, and central UiPath assets become managed Power Platform connections. The upside of a rebuild is that it forces a process audit - many UiPath bots accumulated years of patched exception handling that can be simplified or replaced with an API-first integration entirely.

The moment you accept that migration is a redesign, not a port, the project stops being a code-conversion exercise and becomes a chance to retire the automations you should never have built as bots.

This is where a fixed-fee assessment pays for itself. BabyBots runs process-discovery and RPA-modernization assessments that inventory every UiPath automation, score each one for migrate, redesign, or retire, and turn that into a phased plan with real numbers - before you commit a renewal budget to the wrong strategy.

What does a UiPath to Power Automate migration actually involve?

Treat it as a phased program, not a cutover. A dependable sequence, drawn from enterprise migration blueprints, moves risk to the front and keeps production running throughout.

1. Discovery and rationalization: Inventory every bot, capture run frequency and business owner, and cut automations that are dead, redundant, or better solved with a native integration.
2. Assessment and mapping: Categorize each automation by complexity, then map UiPath activities to Power Automate cloud actions, desktop actions, and connectors.
3. Pilot: Rebuild two or three representative automations end-to-end to validate effort estimates and expose platform gaps early.
4. Connection and data architecture: Stand up shared connections, Dataverse, and environment strategy so bots are not each wired up in isolation.
5. Conversion and validation: Rebuild in waves, run old and new in parallel where feasible, and validate outputs against the UiPath baseline before decommissioning.
6. Governance and ALM: Put a Center of Excellence, solution-based ALM, and monitoring in place so the new estate stays maintainable.

How long does a UiPath to Power Automate migration take?

It depends almost entirely on estate size and complexity, not on the tooling. A small portfolio of simple, rules-based bots can move in a few weeks; a large, entangled estate is a multi-month program. As a reference point, one global media agency migrated 100-plus bots in under five months and unlocked roughly $1.95 million in savings using an accelerator-led approach.

The variables that stretch a timeline are the number of unattended, high-complexity automations, the volume of custom components, and how much of the logic depends on brittle UI selectors that must be rebuilt as integrations. Discovery is what makes the estimate real - never commit a date before you have inventoried and scored the estate.

Attended vs unattended: which Power Automate license does each bot need?

Getting this split right is where most of the savings - or the overspend - lives. Microsoft's premium RPA features draw a hard line between the two modes.

Attended versus unattended RPA in Power Automate

Attended RPA

• Runs: With a signed-in user present at the machine.
• License: Included in the $15/user/month Premium user license.
• Best for: Human-in-the-loop tasks where a person supervises and handles exceptions.

Unattended RPA

• Runs: On a machine with no user present, on a schedule or trigger.
• License: Requires the $150/bot/month Process plan, or $215/bot/month for a Microsoft-hosted machine.
• Best for: High-volume, lights-out back-office processing.

A common mistake is porting every UiPath unattended bot to an unattended Power Automate bot one-for-one. Some of those workloads can be consolidated, rescheduled onto fewer bots, or re-built as cloud flows on connectors - each of which drops the bot count you have to license.

Where UiPath to Power Automate migration is heading

The migration conversation is shifting from cost consolidation to platform modernization. Increasingly, the right answer for a UI-scraping bot is not a rebuilt RPA flow at all - it is an API-first integration or a Copilot Studio agent that reasons over the process instead of mechanically replaying keystrokes. Enterprises that treat a UiPath migration as a pure like-for-like rebuild miss the larger opportunity to retire fragile automation entirely.

The organizations that win here use the renewal deadline as a forcing function: they inventory honestly, migrate what should be migrated, retire what should never have been a bot, and land on a governed Microsoft-native estate that costs less and breaks less often.

Frequently Asked Questions

Is Power Automate cheaper than UiPath?

For organizations already licensed for Microsoft 365 and Azure, yes - most see 40-50% lower RPA licensing after consolidating onto Power Automate, and some published migrations report UiPath licenses costing several times more than the Power Automate equivalent. The savings depend on right-sizing your unattended bot count, since unattended automation is the most expensive tier in both platforms.

Can UiPath bots be converted to Power Automate automatically?

No. There is no reliable tool that converts UiPath XAML into Power Automate flows, so each automation is redesigned rather than ported. Expression logic moves from VB.NET to Power Fx, and UI selectors are re-mapped or replaced with native connectors during the rebuild.

Does Power Automate support unattended RPA at enterprise scale?

Yes. Unattended automation runs under the Process plan at $150 per bot per month, or the Hosted Process plan at $215 per bot per month for Microsoft-managed machines. Enterprises scale by adding bot licenses and machines, and by pairing desktop RPA with cloud flows for orchestration.

How long does a UiPath to Power Automate migration take?

Small, simple estates can migrate in a few weeks, while large or complex estates run for several months. One documented enterprise moved more than 100 bots in under five months. The timeline is driven by the number of complex unattended automations and how much logic must be rebuilt from brittle UI selectors.

Should every UiPath bot be migrated to Power Automate?

No. Discovery usually reveals bots that are dead, redundant, or better replaced with an API integration or a Copilot Studio agent. Migrating those one-for-one wastes effort and licensing - the point of the exercise is to move what should move and retire the rest.

What are the biggest risks in a UiPath to Power Automate migration?

The top risks are underestimating rebuild effort because teams expect a lift-and-shift, over-licensing unattended bots, and cutting over without parallel validation against the UiPath baseline. A phased plan with a pilot, shared connection architecture, and governance in place mitigates all three.

Ready to scope your migration?

If a UiPath renewal is forcing the question, get a straight answer before you sign. Book a BabyBots UiPath-to-Power-Automate migration assessment - in a focused working session we inventory your bots, score each one for migrate, redesign, or retire, size the Power Automate licensing, and hand you a phased plan with the real cost math. Fixed fee, no staff-aug, a decision you can take to finance.

Sources

• Microsoft - Power Automate pricing
• Microsoft Learn - Types of Power Automate add-ons
• Microsoft Learn - Premium RPA features
• Kanerika - UiPath to Power Automate Migration: A Step-by-Step Enterprise Guide (2026)
• Innovational Office Solution - UiPath to Power Automate Migration: Enterprise Blueprints (2026)
• Innovational Office Solution - Technical Engineering Blueprint (2026)
• CFB Bots - Case Study: UiPath to Microsoft Power Automate Migration
• iOPEX - Global Media Agency Migrates Automation Bots from UiPath to Power Automate (2026)
• Automation Atlas - Power Automate Pricing Explained (2026)