UiPath Activity Migrator is Generally Available

Luiza_Surdu-Bob · April 8, 2026, 11:30am

UiPath Activity Migrator is Generally Available!

We’re thrilled to announce that UiPath Activity Migrator 25.10.0 is now Generally Available!

Following the successful Public Preview period and valuable community feedback, the Activity Migrator is ready for production use, giving your teams a streamlined, automated way to modernize legacy automation projects at scale.

What Is the Activity Migrator?

The Activity Migrator is a command-line interface (CLI) tool that streamlines the transfer of process configuration and dependencies when migrating your projects from Windows - Legacy to the Windows compatibility mode.

With the Activity Migrator, you can:

Bulk convert Windows - Legacy projects to Windows, improving performance and compatibility with external libraries.
Migrate classic UI Automation activities to the modern UI Automation framework, enabling access to features such as Unified Target and Healing Agent.
Transition from classic Mail activities to Integration Service activities, moving away from the deprecated Classic Outlook API to Microsoft 365 integration.

While the Activity Migrator handles combined conversion scenarios (framework upgrade + activity migration in one pass), you can still use Studio’s built-in Windows-Legacy Converter for single projects that don’t require activity-level changes.

What’s New Since Public Preview

Workflow Analyzer Rule: ST-AMG-001

We’ve added a new Workflow Analyzer rule — ST-AMG-001: Identify activities with post-migration action required annotations, to help you catch any remaining items that need your attention after migration.

When this rule flags an activity, it means a post-migration annotation was left on it indicating that further action is required.

Recommendation: Review and resolve the post-migration action required annotations on the flagged activities, then remove them using the activity option: Annotations > Delete Annotation.

The ST-AMG-001 Workflow Analyzer Rule is available starting with Studio 2025.10.8 LTS and Studio 2026.0.189 STS.

WaitActive / WaitNotActive Property Migration

Migration of the WaitActive and WaitNotActive properties for the following activities is now supported:

Find Element - WaitActive
On Element Appear - WaitActive
On Element Vanish - WaitNotActive
Wait Element Vanish - WaitNotActive

Minimum required version: UiPath.UIAutomation.Activities 25.10.29 or higher. To enable this functionality, the version must be specified in the command line: --uia-package-version=25.10.29.

How to Get It

The Activity Migrator is available through:

Automation Cloud Download Center
Customer Portal
Direct download as a CLI archive

Supported Migration Scenarios

UI Automation

Migrates classic activities (Click, Type Into, browser operations, etc.) to their modern equivalents. For a full list of supported and unsupported activities, refer to the documentation.

Minimum required version: UiPath.UIAutomation.Activities 25.10.21 (25.10.21 is used by default if not explicitly specified)

Mail Activities

Converts classic Outlook Desktop Mail activities to Office 365 equivalents via Integration Service.

Minimum required version: UiPath.Office365.Activities 3.6.10 (3.6.10 is used by default if not explicitly specified)

Core Functionality

The UiPath Activity Migrator is a standalone tool that runs independently of UiPath Studio.

Feature	Description
Command-line execution	`analyze`, `upgrade`, and `bulk` commands
Pre-migration summary	Use `analyze` before upgrading to preview what will change
Post-migration summary	SARIF report with a breakdown of migrated activities
Post-migration recommendations	Annotations on activities that need further manual action
Workflow Analyzer integration	Rule ST-AMG-001 flags activities with unresolved post-migration annotations

Learn More

cprima · April 8, 2026, 4:18pm

Wait, what? Workflow Analyzer can read annotations? o_O

postwick · April 8, 2026, 4:33pm

How does the migrator handle when there is no Windows version of a dependency that’s used in the Legacy version?

loginerror · April 8, 2026, 4:46pm

This depends on the situation, but in general, you either get warnings or, in this specific case, the report will tell you to migrate the underlying library activity project first.

Having said that, any case where an existing UiPath activity throws this exception is a reason to contact us for future improvements

postwick · April 8, 2026, 6:08pm

Well I’m asking because when we converted our internal libraries to Windows, we changed the names. So now to upgrade a project from Legacy we have to manually uninstall the Legacy internal libraries, install the Windows internal libraries, and then modify (manually in Notepad) the references at the top of the XAML files.

It would be nice if there were a “replace” function on the Project tab in Studio. Right-click a library, select Replace, and choose a new library to install in its place - updating all the necessary references automatically.

cprima · April 8, 2026, 6:46pm

@loginerror

Ah, found it: SDK - UiPath.Studio.Analyzer.Models

AnnotationText

Now I can do, without my previous parallel xaml-reading trick, something like this:

  public override InspectionResult Inspect(IActivityModel activity, IAnalyzerConfigurationService config)
  {
      // Per-instance annotation suppression
      if (IsSuppressed(activity))
          return null;

      // ... my rule logic
  }

  private bool IsSuppressed(IActivityModel activity)
  {
      var annotation = activity.AnnotationText;
      if (string.IsNullOrEmpty(annotation))
          return false;

      return annotation.Contains($"@ignore: {Id}", StringComparison.OrdinalIgnoreCase);
  }

loginerror · April 8, 2026, 7:56pm

I’ll keep this in mind to ask the team about it.

To me, it isn’t much different from our migration rules, which do just that – replace one activity namespace with another and map between them (if needed). So if it’s not there yet, I think it would be relatively easy to extend it to cover your use case. I’m sure our devs follow this thread, but I’ll forward it to the right channel as well just to be sure

ClaytonM · April 13, 2026, 7:42am

Thank you for bringing this up @postwick . however, using Notepad to fix the missing Library references in the XAML is a pretty cool party trick.

postwick · April 13, 2026, 1:43pm

It’s not difficult, it’s just annoying to have to do - especially when you have multiple XAML files in one project, you have to do each one separately.

Open each XAML file in Notepad and in the first line you will see xmlns references to the library.  Rename the reference to each upgraded library and save the file.  For example, the old reference for FirstHorizon.Utilities_Windows will look like this:

xmlns:f="clr-namespace:FirstHorizon_Utilities_Windows;assembly=FirstHorizon Utilities_Windows"

Change it to:

xmlns:f="clr-namespace:FirstHorizon_Utilities;assembly=FirstHorizon.Utilities"

This is how we fix it after migrating to Windows compatibility and then installing our Windows libraries (FirstHorizon.Utilities is one of them).

cprima · April 13, 2026, 4:46pm

+1 for Notepad / NotePad++

And another option: Any terminal AI code agent like Claude Code, Codex or Copilot does that very reliably (to rename namespaces and imports).

I think ~70% of my xaml files are already written by such an agent. And I saw that UiPath is polishing their CLI tool for release, so why not try such repairs and “frontrun”?

sonaliaggarwal47 · April 14, 2026, 3:28pm

How to get it?

I am not able to download it from automation cloud.

Are there any pre-requisites for download

loginerror · April 14, 2026, 6:25pm

@sonaliaggarwal47

I think there is something wrong with the link when you click it…

In the meantime, you can copy the link (right click → copy link), and then manually paste it in a new tab to navigate to it. It will work.

sonaliaggarwal47 · April 14, 2026, 6:42pm