Studio user guide

Purpose of the Activity Migrator​

• Automate the migration process by simplifying and streamlining the transfer of process configuration and dependencies.
• Reduce manual effort and errors by ensuring consistency and accuracy during migration, instead of manually transferring dependencies and activities.

Supported migration scenarios​

Project framework migration​

1. Improved performance: Windows projects run faster and more efficiently due to better integration with .NET Core and modern Windows APIs.
2. Better compatibility with external libraries: Windows projects support newer versions of libraries and dependencies, making it easier to integrate with external systems.

Access to modern UI Automation capabilities​

Deprecated Outlook activities migration​

Activity Migrator vs. the Studio Windows - Legacy converter​

• You only need to convert projects from Windows - Legacy to Windows one by one.
• No activity migrations are required.

• You want to convert multiple Windows - Legacy projects to Windows (bulk conversion supported).
• Migration of UI Automation or Mail activities is needed.
• Any combination of the above scenarios applies.

Where to get the Activity Migrator​

1. Navigate to UiPath Automation Cloud.
2. Select the Help button in the top-right corner.
3. Under Resources, select Downloads.
4. Under the Feature Download list, select Activity Migrator Tool.
5. Select the download link.

Requirements​

• If the tool is used on a machine where Studio is not installed, install .NET Desktop Runtime 8.0.
• Open migrated projects with Studio versions 2024.10 or higher.

How to use the Activity Migrator​

Analyze a project​

Migrate a project​

Bulk repository migration​

Examples​

UiPath.Upgrade.exe analyze -p C:\to-migrate\LegacyProcess -v
UiPath.Upgrade.exe analyze -p C:\to-migrate\LegacyProcess -v

UiPath.Upgrade.exe upgrade -p C:\to-migrate\LegacyProcess -o C:\to-migrate\WindowsProcess --uia-package-version=25.10.27 -v
UiPath.Upgrade.exe upgrade -p C:\to-migrate\LegacyProcess -o C:\to-migrate\WindowsProcess --uia-package-version=25.10.27 -v

UiPath.Upgrade.exe upgrade --project-path=C:\to-migrate\LegacyProcess --config=C:\to-migrate\connection.json
UiPath.Upgrade.exe upgrade --project-path=C:\to-migrate\LegacyProcess --config=C:\to-migrate\connection.json

UiPath.Upgrade.exe bulk -p C:\to-migrate -c analyze
UiPath.Upgrade.exe bulk -p C:\to-migrate -c analyze

Configuration file​

{
  "{reserved-configuration-key}": "{value}",
  "...": "...",
  "{path-to-workflow} > {activity-display-name}": {
    "{property-name}": "{property-value}"
  }
}
{
  "{reserved-configuration-key}": "{value}",
  "...": "...",
  "{path-to-workflow} > {activity-display-name}": {
    "{property-name}": "{property-value}"
  }
}

Getting the ConnectionId from Orchestrator​

1. Navigate to your connection in Orchestrator: Go to the Orchestrator folder where your Microsoft Outlook 365 connection is located.
2. Open the connection: Click on the connection to view its details.
3. Check the URL: The ConnectionId is visible in the browser URL with the following format: https://cloud.uipath.com///orchestrator_/connections//edit/tid=

Setting Connection IDs for Productivity activities​

{
    "* > *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000001"
    },
    "*\\Projects\\MailMigration\\Main.xaml > Get *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000002"
    },
    "*\\Projects\\MailMigration\\* > Send Mail": {
        "ConnectionId": "00000000-0000-0000-0000-000000000003"
    }
}
{
    "* > *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000001"
    },
    "*\\Projects\\MailMigration\\Main.xaml > Get *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000002"
    },
    "*\\Projects\\MailMigration\\* > Send Mail": {
        "ConnectionId": "00000000-0000-0000-0000-000000000003"
    }
}

• * > * matches all activities and acts as a fallback when there are no matching entries below.
• *\\Projects\\MailMigration\\Main.xaml > Get * matches any activity whose display name starts with Get in Main.xaml.
• *\\Projects\\MailMigration\\* > Send Mail matches the Send Mail activity across all workflows in the MailMigration folder.

Post-migration UI Automation Application Scope behavior​

Limitations​

UI Automation activities​

• The minimum supported target version of UiPath.UIAutomation.Activities is 25.10.21.
• Some activity properties have migration limitations. See the supported activities lists:
  • UI Automation supported activities
  • UI Automation unsupported activities
• Migrated workflows using modern UI Automation activities may execute more slowly than the original workflows using classic UI Automation activities.

Productivity activities​

• The minimum supported target version of UiPath.MicrosoftOffice365.Activities is 3.6.10.
• See the supported activities lists:
  • Mail supported activities
  • Mail unsupported activities

Tool limitations​

• By default, the Activity Migrator tool uses NuGet feeds configured in NuGet.config: Official, Local, and Marketplace. To include Orchestrator library feeds, use the options for the analyze, upgrade, and bulk commands: --orchestrator-url, --orchestrator-tenant, --orchestrator-pat, --orchestrator-application-id, and --orchestrator-application-secret.
• Activities that use dynamically generated types or assemblies (for example, some Excel activities may have column names as properties in a dynamically generated type) may cause a Type not found error in .xaml files after migration.

Studio Workflow Analyzer rule​

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

Migration best practices​

Before migrating​

1. Back up your projects: Always create a full backup before running any migration commands.
2. Update Studio and activity packages: Use the latest version of UiPath Studio and ensure target package versions meet the minimum requirements (UiPath.UIAutomation.Activities >= 25.10.21 and UiPath.MicrosoftOffice365.Activities >= 3.6.10).
3. Analyze before upgrading: Run the analyze command first. Use UiPath.Upgrade.exe analyze -p -v to generate a SARIF report and identify potential issues without modifying the project.
4. Verify dependencies and NuGet feeds: Confirm that the Official, Local, and Marketplace feeds are correctly configured in NuGet.config.
5. Migrate the libraries first when a project depends on library projects: Only then migrate the projects that consume them.

During migration​

5. Start with a single project: Test migration on one project using UiPath.Upgrade.exe upgrade -p -v before running a bulk operation.
6. Use bulk migration for multiple projects: Once validated, run UiPath.Upgrade.exe bulk -p -v. Ensure the folder structure is clean and consistent.
7. Provide a configuration file for Connection IDs: For Microsoft 365 or GSuite activities, create a config file with the required ConnectionId values and pass it with --config:

{
    "* > *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000001"
    }
}
{
    "* > *": {
        "ConnectionId": "00000000-0000-0000-0000-000000000001"
    }
}

After migrating​

8. Review the SARIF report: Check the .upgrade folder in the project directory and address any flagged issues.
9. Open the migrated project in Studio and run Analyze Project: Review the results of the ST-AMG-001 Workflow Analyzer rule (available in Studio 2025.10.8 LTS / Studio 2026.0.189 STS or higher) to identify activities that require post‑migration actions.
10. Validate application scopes: Confirm that merged scopes behave as expected. Test workflows with Use Application/Browser activities.
11. Run end-to-end tests: Execute migrated workflows in a controlled environment before deploying to production.

Performance and maintenance​

12. Optimize UI Automation selectors: After migration, review selectors for accuracy and stability.
13. Monitor execution time: Modern activities may run slower initially. Optimize where needed.
14. Document your changes: Keep a record of migrated projects, target versions, and applied configurations for audit and rollback purposes.