Migrate Microsoft RSAT Test Suites to Leapwork Using the Migration Wizard

Migrate Microsoft RSAT Test Suites to Leapwork Using the Migration Wizard

Overview:

Easily migrate your Microsoft RSAT test suites for Microsoft Dynamics 365 Finance & Operations into Leapwork using the guided migration wizard. The wizard walks you through the entire migration process, from analyzing your RSAT project and reviewing potential issues to applying recommended changes and importing your migrated flows into Leapwork.

The migration wizard helps you:

This new graphical interface replaces the previous command-line migration process, making the migration experience simpler and easier to manage.

Prerequisites

Before starting the migration:

Note: Always select the parent RSAT project folder. Selecting an individual flow folder will prevent the migration from working correctly.

Step 1: Launch the Migration Wizard

Open the RSAT to Leapwork Studio Migration Wizard.

The application opens with a simple graphical interface where you can perform the migration without using Command Prompt.

Step 2: Select the RSAT Project

Click Browse.

Select the parent folder that contains your RSAT project.

Note: Do not browse into an individual test suite or flow folder.

Step 3: Analyze the Project

Click Analyze RSAT Files.

The migration wizard scans the RSAT project and checks for any migration issues.

Once completed, the tool displays:

a. Test Cases

Displays the total number of RSAT test cases identified in the selected project.

b. Total Blocks

Shows the total number of blocks identified across all migrated test cases.

c. Unmigrated

Indicates the number of blocks that could not be migrated and may require your attention before export.

d. Risky

Displays the number of blocks that should be reviewed, as they may require manual updates during or after migration.

e. Active Row

Highlights blocks using the Active Row setting. Review and update the row index if required before exporting to avoid manual changes later in Leapwork.

f. Dependencies

Shows the number of project dependencies identified during the migration that should be reviewed. For example: Example: Suppose Flow 1 defines a variable called Customer ID, and Flow 3 uses the same variable during execution instead of creating a new one. In this case, Flow 3 depends on Flow 1 for that variable. The Migration Wizard identifies these dependencies so you can review them before importing the flows into Leapwork.

g. Deleted

Displays the number of blocks or items that were removed during the migration process. In this example, the Deleted count is 0, indicating that no blocks or configurations have been removed from the migrated project.

Duration

Shows the total time taken by the Migration Wizard to analyze the RSAT project. In this example, the Migration Wizard has identified 24 test cases containing 594 blocks. This overview helps you understand the scope of your migration and allows you to review and manage the migrated project directly within the wizard before exporting it to Leapwork.

Configure migration settings

The following settings are available on the Analyze RSAT Files page.

Setting Description
RSAT Input Folder Location of the parent folder that contains your RSAT project.
Output Zip File Location where the generated migration package will be saved.
Default D365 URL (Optional) The Dynamics 365 URL to use as the default for migrated flows.
Skip local RSAT title lookup (Optional) Skips the local RSAT title lookup during analysis. Use this if the local title data is unavailable or not required.
Send to Leapwork Enables the Leapwork destination settings (Controller URL, Target Folder, Team ID, API Key).

Note:

When Send to Leapwork is selected, additional destination fields are displayed:

Step 4: Review Migration Issues

If the wizard detects any issues, you can take a moment to review the recommendations before continuing. Unlike the previous migration process, where flows were imported directly into Leapwork and required you to manually update settings such as environment URLs, usernames, passwords, and other configuration details afterward, the new Migration Wizard helps you identify and address many of these items during the migration itself. This means less manual work after import and a smoother, more efficient migration experience.

For example:

Where possible, update the values directly in the wizard before proceeding. For example, if an Active Row is highlighted, change the row index (for example from 0 to 1 or 2) so users do not need to manually update it later inside Leapwork.

Review matching blocks

Some blocks display a Matching Blocks section. This section lists other blocks in the migration that share similar configurations or are related to the currently selected block.

Use matching blocks to:

Step 5: Apply Changes

After reviewing the recommendations, click Apply Changes.

Only this selected flow

Applies the changes only to the currently selected flow. Use this option when you want to update a single flow without affecting any other flows in the project.

Apply to all login blocks

Applies the same changes to every login block across all migrated flows. This is useful when the same configuration, such as the environment URL, username, or password, should be used consistently throughout the project.

The migration wizard updates the RSAT project using the selected configuration. In the following example, all the login blocks have been updated since we selected the first option.

In case of the warnings (in below image):

You can anytime make the changes and apply to fix the warnings, moreover you can also delete the blocks as per your requirements and flow needs:

Moreover, If you need more control over your migrated flows, the Migration Wizard lets you update target selectors before export. Simply enter a unique locator for the element, and the wizard will apply the updated selector, helping you tailor the migration to your application's needs.

In this above example, the target selector identifies the Modules button in a Microsoft Dynamics 365 Fusion Recorder flow. If your application uses a different or more specific locator for this element, you can update the target selector before exporting the migrated flows. For example, if you want the flow to select the Home button instead of the Modules button, simply update the locator to point to the Home button. This allows you to customize the flow to match your application's interface without making changes after the migration.

Note: You can use the available filters to quickly view specific migration results, such as deleted items, warnings, or other categories. Warnings are informational and can be skipped if you don't want to review them immediately. For items marked as Risky, the Migration Wizard explains why they require attention, which will help you decide whether any changes are needed before exporting your flows.

Review Session:

A Review Session captures the current state of your migration review, including the changes you've made. This lets you pause your work and continue later without starting over.

Reusable Preferences:

If you use the same settings across multiple migrations (for example, D365 login credentials in this case), you can save them as reusable preferences. The Migration Wizard remembers these details and automatically applies them the next time you open a project, so you don't have to enter them again. After saving your preferences, click Apply Reusable Preferences to use those saved settings automatically, so you don't have to enter them again.

Step 6: Export the Migration Package

Once the analysis part of RSAT files completes successfully, we are ready to export the package to Leapwork, simply click Export Package.

You're all set! The export is successfully completed. After the export is complete, you'll find the updated ZIP package in the selected folder, which is now ready to be imported into Leapwork.

Once the migration is complete, the wizard saves everything, including your changes in a ZIP package. You can use the following package to import your flows into Leapwork.

Step 7: Import into Leapwork Studio

Open Leapwork Studio. Create a new Flow Folder if required. You can import the migrated flows using either of the following methods.

Option 1 – Import Directly

Use Import Folder inside Leapwork Studio and select the exported migration package.

Option 2 – Import Using the Exported Package

Enable Send to Leapwork checkbox in the RSAT to Leapwork Studio tool and enter the required information.

Controller URL

Enter the URL of your Leapwork Controller. This is the Controller address where you want the migrated flows to be sent.

Example:http://localhost:xxxx or your organization's Leapwork Controller URL.

Target Folder

Choose or enter the Leapwork folder where you want the migrated flows to be imported. You can use an existing folder or create a new one to keep your flows organized.

Team ID

Enter the ID of the Leapwork team where the flows should be imported. You can copy this ID from Team Management in Leapwork studio.

API Key

Generate and enter an API Key with the required permissions to allow the Migration Wizard to communicate securely with your Leapwork environment. The API key is used to authenticate the connection and send the migrated flows directly to Leapwork.

Once you have generated the key, simply copy it and paste it in API key field.

Note: Ensure the API key includes the required permissions (such as Import/Export and Flow Hierarchy) before using the Send to Leapwork option.

Review the execution log

The Execution Log panel is available throughout the migration workspace. It displays diagnostic information generated during each stage of the migration process.

Use the execution log to:

Send the Migrated Flows to Leapwork

Once you've reviewed your changes, click Send to Leapwork to upload your migrated flows directly from the Migration Wizard. The wizard automatically creates a fresh migration package using your latest updates and imports it into the target folder you selected in Leapwork.

If the upload completes without any errors, your migrated flows are ready to use in Leapwork. Now let’s go back to our Leapwork studio and since we are in Team 1, so let's go to our flows.

There is this RSAT folder.

All the 24 flows have been successfully imported with all the changes reflected in the blocks we have made, you can click on the particular block to see the changes.

Reusing a Migration Package

The exported package can be reused later.

Once your migration is complete, you can bring your migrated flows into Leapwork in either of these two ways:

There is no need to rerun the migration wizard unless changes have been made to the original RSAT project.

Best Practices

You can check FAQs at: Click here

For any clarification, please contact on  Priority Support.