How to Export and Import Dynamics 365 Dataverse Records Using Configuration Migration Tool

 In this blog, we will learn how to export and import selected Microsoft Dynamics 365 / Dataverse records using the Configuration Migration Tool.

The Configuration Migration Tool is useful when you need to move configuration or test data between Dataverse environments, such as Development, Test, UAT, and Production. It also allows you to create a schema that defines which tables, columns, relationships, and records should be included in the migration.

One useful feature is the ability to use FetchXML filters so that you can export only the required records instead of exporting all records from a table.

For example, if you have thousands of Account records but want to migrate only accounts where the name is Test, you can use a FetchXML filter during schema creation.

What is the Configuration Migration Tool?

The Configuration Migration Tool is a Microsoft tool that helps administrators and developers move configuration and test data between Dataverse environments.

It can be useful for scenarios such as:

• Moving selected configuration data from Development to Test.
• Moving test data between environments.
• Migrating reference/configuration records.
• Exporting a specific set of records using FetchXML.
• Creating reusable data packages for environment setup.
• Supporting application deployment and testing scenarios.

The tool creates a schema that defines the data to be exported. The same schema can also be reused for future exports.

Prerequisites

Before starting, make sure you have:

• Access to the source Dynamics 365 / Dataverse environment.
• Access to the target environment if you are performing an import.
• Required permissions to read and migrate the selected data.
• The Configuration Migration Tool.
• A clear understanding of the tables and records you want to migrate.
• Required dependencies available in the target environment.

The Configuration Migration Tool is available through Microsoft's Power Platform tooling. The executable used in the downloaded tool is DataMigrationUtility.exe.

Download Link:

https://www.microsoft.com/en-in/download/details.aspx?id=44567

Step 1 – Open the Configuration Migration Tool

After downloading and extracting the Configuration Migration Tool, navigate to the following folder:

<Your Tool Folder>\Tools\ConfigurationMigration\

Open:

DataMigrationUtility.exe

The tool provides options such as:

• Create Schema
• Export Data
• Import Data

For our example, we will first create a schema.

Step 2 – Create a Schema

On the Configuration Migration Tool home screen:

1. Select Create schema.
2. Click Continue.

The tool will ask you to connect to your source Dataverse environment.

Step 3 – Connect to the Source Environment

Provide the required authentication details to connect to your Dynamics 365 / Dataverse environment.

If required, select the option to display the list of available organizations/environments.

After successful authentication, select the environment from which you want to export the data.

Step 4 – Select the Table

After connecting to the environment, you can select the solution and tables that you want to include in the schema.

For this example, we will use the Account table.

Select the required table and continue with the schema configuration.

·      

Step 5 – Create a FetchXML Filter

One of the useful features of the Configuration Migration Tool is the ability to filter the records that should be exported.

For example, suppose we have multiple Account records, but we want to export only the Account where the name is Test.

Open Advanced Find / the appropriate Dataverse query experience and create your required filter.

For example:

<filter type="and">
    <condition attribute="name" operator="eq" value="Test" />
</filter>

The above filter selects only the Account record where:

Name = Test

Step 6 – Configure Import Settings

After selecting the required table, open:

Tools → Configure Import Settings

Select:

Use FetchXML to filter records

A new filter window will appear.

Enter the required FetchXML filter and click OK.

Then click Save to save the schema.

·  New filter POP will get open add filter condition and click on Ok and Click on Save.

Step 7 – Save the Schema

After saving the schema, the tool will display a confirmation message indicating that the schema has been saved successfully.

The tool may also ask:

Would you like to export the data?

Select Yes if you want to continue with the export.

A schema is important because it defines the data structure and the records that should be included in the export. Microsoft recommends validating schemas and checking dependencies to help avoid incomplete data sets.

Step 8 – Export the Data

After creating the schema, specify the location where you want to save the exported data.

Select the Save to data file option and provide the required file name and location.

Then click:

Export Data

The tool will start exporting the selected records.

Step 9 – Verify the Exported Data Package

Navigate to the location where you saved the exported file.

You will find the generated ZIP package.

The package contains the information required by the Configuration Migration Tool to import the exported data into another compatible environment.

• Navigate to zip folder you can find 3 files.

Step 10 – Import the Data into Another

Environment

Once the export is completed, you can import the package into your target Dynamics 365 / Dataverse environment.

Open:

DataMigrationUtility.exe

From the main screen:

1. Select Import data.
2. Click Continue.
3. Sign in to the target environment.
4. Select the target organization/environment.
5. Select the exported ZIP file.
6. Click Import Data.

The tool will process the package and display the import progress.

Microsoft's current documentation follows the same basic flow: open the Configuration Migration Tool, select Import data, connect to the destination environment, select the exported ZIP file, and start the import.

Conclusion

The Dynamics 365 / Dataverse Configuration Migration Tool provides a convenient way to move selected configuration and test data between environments.

By creating a schema and using FetchXML filtering, you can control which tables and records are included in the export. This is especially useful when you need to migrate only specific records instead of moving an entire table.

The overall process is:

Create Schema
      ↓
Select Tables
      ↓
Configure FetchXML Filter
      ↓
Save Schema
      ↓
Export Data
      ↓
Generate ZIP Package
      ↓
Connect to Target Environment
      ↓
Import Data
      ↓
Validate Records

This approach can save time and reduce manual data entry when moving required configuration or test data between Dynamics 365 / Dataverse environments.

I hope this article helps you with your Dynamics 365 and Power Platform development journey.

If you found this article useful, please share it with other Dynamics 365 and Power Platform developers.

Happy Learning!