Comparison Types

Purpose

This chapter describes the comparison scenarios ConfigCompare supports. Every comparison type reports Matches as well as Differences, so results show where configuration is identical as well as where it varies.

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

Environment-to-environment comparison

Environment-to-environment comparison compares configuration between two Dynamics environments.

Examples:

• DEV to TEST.
• TEST to UAT.
• UAT to PROD.
• GOLD to UAT.
• GOLD to PROD.
• PROD to SANDBOX.
• CRP to GOLD baseline (to validate the final CRP configuration before walking it into production).

This comparison type supports Application Lifecycle Management, release validation, deployment validation, and support triage.

Same environment over time

Same environment over time comparison compares Snapshots from the same environment at different points in time.

Examples:

• PROD today to PROD yesterday.
• PROD before a release to PROD after a release.
• UAT before testing to UAT after testing.
• CRP start to CRP end (to identify all changes made during the Conference Room Pilot).

This comparison type supports governance, audit, drift detection, support triage, and implementation phase validation. For implementation projects, same-environment-over-time comparison is particularly valuable for tracking configuration evolution through CRP, UAT, and readiness phases.

Company-to-company comparison

Company-to-company comparison compares configuration between legal entities or companies.

Examples:

• Company A to Company B.
• USMF to DEMF.
• A newly created company to an approved template company.

In comparison setup this is the One vs One mode, naming an explicit Company A and Company B; comparisons across every company use the All companies mode.

This comparison type supports rollout consistency, global template governance, and multi-company implementation control.

N:1 company comparison

N:1 company comparison compares many companies against a single approved reference company or golden template.

Example:

All US manufacturing companies can be compared against one approved US manufacturing template.

In comparison setup this is the All vs One mode, with the reference company as the pivot.

N:1 comparison is important for organisations with many legal entities, regions, countries, business units, plants, warehouses, franchises, or operating companies.

Typical governance patterns include:

• Regional templates.
• Global templates.
• Industry templates.
• Shared service organisations.
• Phased rollouts.

N:1 comparison supports governance across large ERP estates where many organisations are expected to conform to a common configuration standard.

Cross-tenant or cross-instance comparison

ConfigCompare supports Configuration Governance across multiple Dynamics 365 instances and Microsoft tenants. Cross-tenant operation is delivered through the Cross-Tenant capability.

This is especially relevant for enterprise groups, acquired companies, regional deployments, and partners managing multiple customer ecosystems.

AX 2012 to D365 comparison

ConfigCompare can support AX 2012 Snapshots and compare them with Dynamics 365 Finance & Supply Chain Management Snapshots for upgrade path analysis.

This supports organisations preparing to migrate from AX 2012 to D365.

Metadata Comparison

Metadata Comparison analyses structural Differences in the application rather than only configured data.

Metadata Comparison is useful for Upgrade Analysis, Microsoft One Version changes, ISV impact assessment, customisation review, and structural drift detection.

Related topics

• Chapter 04: ConfigCompare
• Chapter 05: Comparison Engine
• Chapter 06: Snapshots
• Chapter 16: Upgrades