# Build a single customer view without losing the source of truth Published by Britixo | 2026-10-29 | CRM & integrations Canonical page: https://britixo.com/business-guides/single-customer-view-integration/ A single customer view is a reliable way to relate information across systems, not necessarily one database that owns every field. Define the entity being matched, preserve source identifiers and decide which system is authoritative for each attribute. Show the source and freshness of important information, and keep permissions appropriate to the viewer. Start with the specific questions staff need to answer rather than collecting every available customer attribute. ## When this guide is useful Organisations that need a coherent customer view across sales, finance and support. - Sales, finance and support use different identifiers for the same account. - Staff see conflicting addresses, contact preferences or account status. - Customer activity is spread across systems with no dependable relationship. - A central dashboard presents old information as if it were live. ## Start with the questions the view must answer Choose a small set of operational questions: who owns the account, which cases are open, what orders are active and whether finance needs to be consulted. Identify the minimum data needed for those answers. A service agent may need a payment-status flag without seeing every financial document. Define whether the view represents a person, organisation, household or branch. Keep one-to-many relationships such as orders and tickets separate from identity fields. Microsoft Customer Insights describes unification as a process involving source selection, deduplication, matching and a unified view; a similar separation helps make any implementation easier to reason about. ## Build identity links that can be corrected Store a stable cross-reference between the unified identity and each source record. Use reliable identifiers where available and carefully reviewed matching rules elsewhere. Shared contact details, company renaming and acquisitions can make apparently obvious matches wrong. Microsoft's matching documentation shows that normalisation, rule order and exceptions influence results. Test your rules with known matches and known non-matches. Include an explicit process for splitting a false match or linking a missed match, and retain enough provenance to understand which source relationships were affected. - Keep placeholders and shared values out of strong-match rules. - Review ambiguous matches before exposing combined information. - Test branches, subsidiaries and customers with multiple roles. ## Resolve field ownership and freshness Choose the authoritative source for each important field and explain how conflicts are handled. A recently entered value is not necessarily more trustworthy than an older verified one. For example, an order's delivery address may differ legitimately from the account's registered billing address. Display timestamps and source links where freshness matters. Define acceptable delay separately for profile information, open cases and payment status. If a source is unavailable, retain a clear last-known state or show that the field cannot currently be confirmed rather than silently treating missing data as an empty value. ## Apply permissions to the combined result Combining data can reveal more than each system reveals on its own. Check the viewer's role and purpose before displaying sensitive fields or cross-system relationships. A central profile should not become a shortcut around the finance, HR or customer-service system's access controls. Validate the view through real user tasks and monitor reconciliation differences. Keep correction responsibilities with named source owners so the dashboard does not become another competing master record. Expand the view only when each additional data source improves a defined task and can be maintained reliably. ## Prepare for a useful conversation - A defined customer entity and a shortlist of operational questions. - Source-to-unified identifier mappings with provenance. - Tested match, non-match and manual correction rules. - Field ownership, freshness and conflict decisions. - Role-appropriate views and reconciliation responsibilities. ## How Britixo can help Britixo can help connect customer information across CRM, service, accounting and other supported systems. A scoped project can define identity matching, source ownership, APIs, role-based views and reconciliation. We can build a focused account view or integration layer without assuming every source must be replaced. The proposal should identify what is live, what is periodically synchronised and where a user must return to the authoritative application. Contact Britixo with the questions your teams struggle to answer and the systems holding the relevant records so we can design a useful first release. [Contact Britixo](https://britixo.com/contact/?enquiry_type=contact_consultation#contact-form) ## Common questions ### Do we need to replace all systems to get a single customer view? No. A view can connect existing sources through identifiers and supported integrations. Replacement is a separate decision based on each system's suitability and maintenance needs. ### Should the latest update always win a conflict? No. Establish authority by field and business process. A later unverified entry should not automatically replace a verified billing detail or approved preference. ### How do we correct an incorrect customer match? Use a controlled split or relinking process that preserves source identifiers and records the decision. Recalculate affected views and check any downstream actions that used the incorrect relationship. ## Related guides - [Fix duplicate CRM records without merging different customers](https://britixo.com/business-guides/fix-duplicate-crm-records/) - [CRM data migration checklist: move records without losing relationships](https://britixo.com/business-guides/crm-data-migration-checklist/) - [Connect CRM and accounting software without creating competing records](https://britixo.com/business-guides/connect-crm-accounting-software/) ## Sources and further reading - [Microsoft: Data unification overview](https://learn.microsoft.com/en-us/dynamics365/customer-insights/data/data-unification) - [Microsoft: Matching rules for data unification](https://learn.microsoft.com/en-us/dynamics365/customer-insights/data/data-unification-match-tables) Prepared with AI assistance and checked against linked primary documentation. [Editorial approach](https://britixo.com/business-guides/#editorial-approach). Product availability and delivery scope are confirmed for your requirements.