RPA- migration from UI path to Power automate desktop

(2) Share

Report

Posted on by SayanikaSM Microsoft Employee

Hi ,

I am working on an engagement where RPA is getting migrated from UIPath to Power Automate desktop.

I understand there are separate tools to do that. But I am trying to use GITHub copilot to analyse the UI path script and convert it to a PAD compatible format.

However, I am seeing that GITHub copilot is not providing much information in context of PAD solution/components. There is only a Flow file getting generated in GitHub copilot. Any idea if there is any way to do this?

Thanks

Categories:

AI Builder

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Nived_Nambiar 18,138 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @SayanikaSM

I am not aware of any tools for same - but best way would be analyze the UiPath script - understand the logic and see the actions used there can be used here (or equivalent actions may present).

Thanks & Regards,
Nived N

Stay connected:
LinkedIn | YouTube | Blogs

Was this answer helpful?
If yes, please mark it as the solution by selecting the checkbox in the discussion thread.
Your feedback motivates me to keep contributing. Thank you!

Was this reply helpful? Yes No
Suggested answer

cfb-bots 6 on at

Like (0)

Report
Copy link

Link copied!

Currently, the LLMs are not very helpful in terms of converting UiPath scripts to PAD.

One reason is the huge differences between both RPA platforms. Simply put, a lot of UiPath activities don't map well to PAD actions.

For example, consider the UiPath activity “Log Message”. While PAD offers a similarly named “Log message” action, it is a premium-only feature, available only with a paid subscription. And even then, the mapping is imperfect. Specifically, in UiPath’s “Log Message” activity, there are a total of 5 log levels–Trace, Info, Warn, Error, and Fatal. Whereas in PAD, the “Log message” action only has 3 log levels–Info, Warning, and Error.

There is simply too much variability and judgement required during such migration that human inputs are still required.

If you are interested to learn more, do check out this blog post: How to Migrate from UiPath to Power Automate. It provides a clear breakdown of the challenges and considerations.

Happy automating!

Was this reply helpful? Yes No