Step-by-Step Guide: Using the Configuration Migration Tool (CMT) in D365 & Power Platform

The Configuration Migration Tool (CMT) is an essential utility in Microsoft Power Platform that allows users to move configuration data (such as lookup tables, settings, and metadata) between Dataverse environments. This ensures consistency across environments and simplifies data portability in Dynamics 365 implementations.
With CMT, you can export and import configuration data, maintaining relationships, primary keys, and data integrity while ensuring seamless deployment across environments.

Diagram
Move configuration data across organizations – Power Platform | Microsoft Learn

Step 1: Download & Launch the Configuration Migration Tool

1. Download the Configuration Migration Tool (CMT) from the Power Platform Tools SDK.
2. Extract the files and open DataMigrationUtility.exe.

Download and launch tools using Power Platform CLI
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/download-tools-nuget#download-and-launch-tools-using-power-platform-cli

Step 2: Connect to the Source Environment

1. Click “Create Schema” to define the data for export.
2. Authenticate using your Power Platform credentials.
3. Select the Solution & Dataverse tables/entities you want to export.
4. Enable related records if needed (e.g., lookups, references)

Step 3: Define the Data Schema

1. Use the Schema Designer to map entity relationships and Primary Keys.
2. Ensure data integrity by configuring dependencies correctly.
3. Save the Schema File (.xml) for future use

Step 4: Export Configuration Data from the Source Environment

1. Select “Export Data” and load the saved schema file (.xml).
2. Choose an output file location for the exported data (.zip).
3. Click “Export”. CMT will generate a data package.
4. Review the export logs to check for warnings or errors.

Step 5: Connect to the Target Environment & Import Data

1. Select “Import Data” and connect to the Target Environment.
2. Choose the exported .zip file from Step 4.
3. Click “Import” to migrate data into the new environment.
4. Monitor the import process and review logs for issues.

Step 6: Validate the Imported Data in the Target Environment

1. Open Power Apps / Dynamics 365 and verify the imported data.
2. Cross-check records, relationships, and metadata for accuracy.
3. Ensure that business rules, forms, and views are functioning as expected.

Best Practices for Using CMT

· Separate schemas for configuration vs. transactional data.
· Ensure data mappings are consistent across environments.
· Backup the target environment before importing data.
· Test migrations in a sandbox environment before moving to production.
· Leverage managed environments for governance and security.

Related Resources:
🔗 Configure and Deploy ALM Tools
🔗 Manage Configuration Data in Power Platform