ConfigMigrate

Purpose

ConfigMigrate provides controlled movement of ERP configuration between Microsoft Dynamics 365 Finance & Supply Chain Management environments.

ConfigMigrate supports repeatable and controlled configuration movement as part of Application Lifecycle Management and implementation activities, enabling organisations to promote configuration safely through the deployment lifecycle.

This chapter describes concepts and behaviour; step-by-step operating guidance sits outside this reference.

Overview

Configuration deployment is a core part of the application lifecycle.

Configuration must move from development through test, UAT, and into production in a controlled, validated manner.

ConfigMigrate enables this movement using supported mechanisms while maintaining consistency and control.

What ConfigMigrate does

ConfigMigrate is used to:

• Generate Data Management Framework (DMF) packages from configuration
• Move supported configuration between environments using DMF
• Update configuration using OData-based scenarios
• Support repeatable configuration movement patterns
• Maintain consistency across environment promotions
• Enable automated deployment workflows

Supported configuration movement

ConfigMigrate supports controlled movement of ERP configuration using:

• Data Management Framework (DMF): standard D365 package generation and import mechanism.
• Data Entities: semantic representations of business data for reliable movement.
• OData updates: direct API-based configuration updates for supported scenarios.

A single configuration setting is rarely safe to move in isolation: settings often need to remain consistent with related settings that a narrowly scoped movement has no knowledge of. For small, well-understood changes, direct manual adjustment, supported by context-aware form navigation (described in this chapter), is often the appropriate mechanism. For larger changes, movement through Data Entities and DMF export files keeps related configuration together and consistent.

Context-aware form navigation

ConfigMigrate provides context-aware navigation to the actual configuration forms.

When reviewing comparison results, users can right-click on any Difference and open the related form directly in either the source or target system (depending on which Snapshot was selected).

This enables:

• Better understanding: see the actual form and configuration context.
• Manual validation: verify configuration before automated movement.
• Direct editing: make manual adjustments when needed.
• Informed decisions: compare side by side before automated migration.
• Quick remediation: fix issues directly in the source system before promoting.

Rather than relying solely on automated movement, this feature bridges ConfigCompare analysis with direct system access for informed configuration management.

Configuration movement scenarios

ConfigMigrate supports several configuration movement patterns:

Gold configuration promotion

Promote approved reference configurations from a GOLD environment to regional or operational deployments.

Environment refresh

Move baseline configuration to refreshed environments so that configuration remains consistent after an environment copy.

Deployment automation

Automate configuration movement as part of continuous integration / continuous deployment (CI/CD) pipelines.

Multi-environment rollouts

Promote configuration consistently across multiple environments in a phased rollout.

Test environment setup

Populate test environments with approved configuration from GOLD baselines.

Integration with Application Lifecycle Management

ConfigMigrate supports the Application Lifecycle Management pillar.

It enables controlled configuration promotion through the deployment pipeline:

1. Configuration is developed in the DEV environment.
2. ConfigMigrate promotes it to TEST.
3. ConfigCompare validates the promotion.
4. ConfigMigrate then promotes the validated configuration to UAT.
5. Approval for production follows successful UAT validation.
6. ConfigMigrate deploys the approved configuration to PROD.

This controlled promotion reduces deployment risk and keeps configuration consistent through the pipeline.

ConfigMigrate and ConfigCompare

ConfigMigrate and ConfigCompare serve complementary purposes:

• ConfigMigrate: enables movement of configuration between environments.
• ConfigCompare: validates that movement was successful.

A typical workflow:

1. ConfigMigrate promotes configuration from DEV to TEST.
2. ConfigCompare compares DEV and TEST to validate promotion success.
3. ConfigMigrate promotes validated configuration to UAT.
4. ConfigCompare validates UAT matches expectations.

Together, they provide both the movement mechanism and the validation evidence.

Business outcomes

Typical outcomes from adopting ConfigMigrate include:

• Controlled promotion: configuration moves through environments in a structured, auditable manner.
• Reduced deployment risk: movement uses validated, repeatable patterns.
• Deployment automation: configuration promotion is automated as part of CI/CD pipelines.
• Consistency: configuration is promoted consistently across similar environments.
• Audit evidence: records exist of what configuration moved, when, and how.
• Speed: manual configuration movement tasks are automated.
• Repeatability: the same proven movement patterns are used across projects.

Relationship to the platform

ConfigMigrate operates alongside the other platform components, each with a single clearly defined responsibility; the full component list is described in Chapter 01: The ConfigCompare Platform.

---

Related topics

• Chapter 01: The ConfigCompare Platform
• Chapter 04: ConfigCompare
• Chapter 06: Snapshots
• Chapter 11: ConfigTrack
• Chapter 13: Application Lifecycle Management