How to Build a Single Customer View in Dynamics 365

Ask five people in your company what they know about the same customer and you will get five different answers. Sales knows the last meeting, finance knows the open invoices, support knows the unresolved ticket, and in Dynamics 365, that customer often exists as three separate records, each holding a fragment of the truth. A single customer view fixes that: one record per customer, holding everything the business knows about them.

What is a single customer view?

A single customer view (also called a single view of the customer, SCV, or a 360-degree customer view) is one complete, accurate record for each customer, combining their identity, transactions, communications and service history in one place. In Dynamics 365 terms: one Account or Contact record per real-world customer, with every activity, opportunity, case and invoice attached to it, and no duplicates competing for that history.

The definition is simple. Getting there is not, because CRM data does not fragment by accident once, it fragments continuously, from a handful of predictable sources.

Why customer data fragments in Dynamics 365

1. Duplicate records

The biggest single obstacle to a single customer view is duplication. “Novo Nordisk”, “Novo Nordisk A/S” and “NovoNordisk” get created as three accounts by three colleagues, and from that moment the customer’s history splits three ways. Native Dynamics 365 duplicate detection catches exact matches but misses spelling variations, phonetic lookalikes and formatting differences, which is why duplicates accumulate even in well-run environments. We cover the mechanics in depth in our complete guide to Dynamics 365 deduplication.

2. Data imports and migrations

Every list import, every migration from a legacy system, every acquisition brings records that overlap with what you already have. Without matching at the point of entry, an import of 5,000 leads can quietly create hundreds of duplicate contacts.

3. Integrations writing in parallel

Marketing automation, ERP connectors, web forms and Power Automate flows all create and update records. Two systems writing to Dynamics 365 with different matching logic will eventually create parallel versions of the same customer.

4. Inconsistent data entry

Free-text fields fill up with variations: phone numbers with and without country codes, names in different cases, addresses formatted three ways. Each variation makes matching harder and reporting less reliable.

What fragmented customer data actually costs

A missing single customer view is not a cosmetic problem:

• Sales works blind. An account manager opens record A and never sees the complaint logged on record B, then calls the customer with an upsell pitch.
• Reporting is wrong. Pipeline, customer counts and revenue-per-customer are all inflated or split across duplicates. Decisions get made on numbers that do not add up.
• Automation misfires. Customer journeys, scoring models and Copilot answers are only as good as the record they read. AI on fragmented data confidently gives fragmented answers.
• Compliance risk grows. A GDPR deletion or consent update applied to one record and missed on its duplicate is a real liability, not a theoretical one.

How to build a single customer view in Dynamics 365: five steps

Step 1: Measure the damage first

Before fixing anything, find out how fragmented your data actually is. Run duplicate detection across Accounts, Contacts and Leads with fuzzy and phonetic matching, not just exact matching, and profile your key fields for completeness. This gives you a baseline number, and a baseline is what turns data quality from a feeling into a project.

Step 2: Standardize before you match

Matching works dramatically better on standardized data. Normalize phone numbers to one format, casing on names, country and address fields to consistent values. Standardization rules that run automatically keep this from regressing the week after you finish.

Step 3: Deduplicate, and merge with history intact

Detection is only half the job. Merging is where the single view is actually created: activities, cases, opportunities and child records from the duplicates must survive onto the master record. Doing this one record at a time through the native merge dialog does not scale past a few dozen duplicates, for thousands, you need bulk merge with rules deciding which record wins. Our guide to merging duplicate records in Dynamics 365 walks through both the native tools and the bulk approach.

Step 4: Close the front door

Deduplicating once and stopping is how organizations end up running the same cleanup project every two years. Prevention means duplicate checking at the point of entry, on manual creation, on imports, and on records arriving through integrations, so the single view you built stays single.

Step 5: Monitor continuously

Data quality decays at a measurable rate: people change jobs, companies rebrand, phone numbers churn. A data quality dashboard in Dynamics 365 that tracks duplicate rates and field completeness per table turns maintenance into a habit instead of a rescue mission.

Native Dynamics 365 tools vs. what they miss

Dynamics 365 ships with duplicate detection rules, a manual merge dialog and import-time checking, and for small, clean environments they can be enough. Their limits show up at scale: exact-match-only logic misses “Jon”/”John” and “Müller”/”Mueller”, merge is manual and two-records-at-a-time, and there is no ongoing measurement of data health. If your duplicate detection rules exist but duplicates keep appearing, the rules are not broken, they are doing exactly what exact matching does.

How the Data Quality App gets you there faster

The Data Quality App for Dynamics 365 and Power Apps was built for exactly this workflow: fuzzy and phonetic duplicate detection across millions of records, bulk merge with configurable master-record rules that preserve full history, standardization rules that run automatically, and dashboards that show data health per table over time. It runs natively inside your Dynamics 365 environment, so there is no data leaving your tenant.

That is not hypothetical: MHI Vestas and Wonderful Copenhagen both used it to consolidate fragmented customer data into records their teams can actually trust.

The bottom line

A single customer view in Dynamics 365 is not a product you install, it is the result of five repeatable steps: measure, standardize, merge, prevent, monitor. The organizations that have one all treat it as an ongoing process with tooling behind it, not a one-off cleanup. Start with the measurement step this week: once you can see the duplicate rate, the rest of the path is obvious.

Frequently asked questions