Part 3 - Data Migration using Configuration Migration Tool(CMT)
1. What is Configuration Migration Tool?
===> The Configuration Migration Tool (CMT) is a free tool provided by Microsoft (in the Power Platform Tools)
===> It helps to Export and import configuration data (Reference Data) between environments.
===> It helps to move data like lookup values, reference data, settings, or other master data.
===> It’s mainly used for moving configuration data, not big volumes of transactional data (like leads or orders).
2. When to Use CMT?
===> We use CMT when we want to move Option Sets, Lookups, Reference Data (like Countries, Regions, Categories).
===> We use CMT when we want to Migrate data from Dev to Test, or Test to Production.
===> We use CMT when we want to Pre-load values into lookup tables (example: list of industries, states).
Example: School Management System
==> If you are building a School CRM App in Dynamics 365 CRM.
==> Your app has a table called “Class Types” (Online, Offline, Hybrid)
==> This is used in dropdowns when users create a new class.
Problem:
==> We have created Class Type table and values in Dev, but now we are ready to move the table to Test and Production.
==> If we don’t move this data, users will see a blank dropdown. They won’t be able to create new Classes.
3. What Type of Data Can We Move Using the Configuration Migration Tool (CMT)
===> The Configuration Migration Tool (CMT) is designed specifically to move configuration/reference data — the kind of data that supports how your app works.
Real time Scenario:
👉 You work for a Car Rental Company, and you have a custom CRM setup with the following tables:
==> We want to move all of this configuration data from your Development CRM to your Production CRM.
👉 This is perfect case for CMT because:
👉 Tools Needed:
👉 What are we doing with this tool:
Step 1: Open the Configuration Migration Tool
==> Go to the folder where you installed it (from Power Platform Tools).
==> Run this file: ConfigurationMigration.exe
Step 2: Create Schema for Related Tables
==> This tells CMT what tables and fields to include.
Order to select:
Select all necessary fields (at least primary name fields and lookup fields)
✅ Now we have a "packing list" that includes related items.
Step 3: Export Data
==> Now we create a ZIP file of actual data.
✅ We have packed all the config data from Dev into a zip.
Step 4: Import Data to Production CRM
==> Now switch environment to Test or Production.
==> It will process each record and maintain relationships because you exported in correct order.
✅ All configuration data is now copied to Production.
Step 5: Validate the Data
1. Car Categories exist
2. Locations are added
3. Cars are linked to Car Categories
4. Rental Rates are correct and linked
5. Rental Settings are in place
Tips:
Limitations/Disadvantages
Data Import Wizard vs. Configuration Migration Tool (CMT)
✅ Done we have successfully migrated related data using CMT, Follow the same steps and try from your end.
Have a Nice Day!