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.


Article content


Real time Scenario:

👉 You work for a Car Rental Company, and you have a custom CRM setup with the following tables:

Article content

==> We want to move all of this configuration data from your Development CRM to your Production CRM.

👉 This is perfect case for CMT because:

  • You have multiple related tables.
  • Lookup fields are involved.
  • You don’t want to retype everything in Production.


👉 Tools Needed:

  • Configuration Migration Tool (CMT)
  • Connection to both environments (Dev and Prod)


👉 What are we doing with this tool:

  • Create a schema for all the related tables.
  • Export data as .zip from Dev.
  • Import that data into Production.
  • Validate that everything is correct.


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.

  • Click “Create Schema”
  • Login to your Development CRM
  • Select the tables in correct order to maintain relationships:

Order to select:

  1. Car Categories
  2. Locations
  3. Cars (lookup to Car Categories)
  4. Rental Rates (lookup to Car Categories and Locations)
  5. Rental Settings

  • For each table:

Select all necessary fields (at least primary name fields and lookup fields)

  • Save the schema file as: CarRentalSchema.xml

✅ Now we have a "packing list" that includes related items.


Step 3: Export Data

==> Now we create a ZIP file of actual data.

  • In the main tool, click “Export Data”
  • Load the schema file: CarRentalSchema.xml
  • Choose a folder to save your export
  • The tool will create a file like: CarRentalData.zip

✅ 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.

  • Go back to the main tool
  • Click “Import Data”
  • Login to your Production CRM
  • Select the file CarRentalData.zip
  • Click Import

==> 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

  • Open your Production CRM
  • Check 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:

Article content


Limitations/Disadvantages


Article content


Data Import Wizard vs. Configuration Migration Tool (CMT)


Article content


✅ Done we have successfully migrated related data using CMT, Follow the same steps and try from your end.

Have a Nice Day!


To view or add a comment, sign in

Others also viewed

Explore topics