Salesforce Data 360 Data Unification: Process, Identity Resolution, Data Model & Best Practices

Learn how Salesforce Data 360 unifies customer data using DLOs, DMOs, data mapping, identity resolution, match rules and unified profiles.

Salesforce Services

What Is Salesforce Data 360 Data Unification?

Salesforce Data 360 data unification is the process of bringing customer and business data from multiple systems together, mapping it to a common data model, resolving identities and creating a connected view of the customer.

An enterprise might have customer information spread across:

Salesforce CRM
ERP systems
Marketing platforms
E-commerce platforms
Websites
Mobile applications
Customer service systems
Data warehouses
Legacy databases
External applications

Each system may use different identifiers, field names and data structures.

For example:

CRM

Customer ID: 10452

Email: [email protected]

ERP

Customer Number: C-88421

Email: [email protected]

Website

User ID: 77892

Email: [email protected]

Marketing

Subscriber Key: VS884

Email: [email protected]

These may all represent the same person.

Data 360 provides an architecture for ingesting and harmonizing these different datasets, applying identity resolution and creating unified profiles that can be used across Salesforce applications and other business processes. Salesforce describes identity resolution as a capability that transforms disparate data from multiple sources into unified profiles.

The objective is not simply to collect more data.

It is to make fragmented data usable as connected context.

Why Data Unification Matters

Without data unification, organizations often operate with fragmented customer information.

A sales representative may see:

CRM account information

Marketing may see:

Campaign engagement

Finance may see:

Orders and invoices

Service may see:

Support cases

The customer, however, experiences all of these interactions as one relationship.

This creates a gap between how the organization stores information and how customers actually interact with the business.

Data unification attempts to close that gap.

A unified architecture can connect:

Customer
│
├── CRM
├── Marketing
├── Sales
├── Service
├── Commerce
├── ERP
├── Website
└── Product Usage
↓
Data 360
↓
Unified Customer Context

Salesforce Data 360 Data Unification vs Data Integration

These concepts are related but different.

Data integration

Data integration focuses on connecting systems and moving or accessing data.

Example:

SAP → Data 360

Data unification

Data unification focuses on understanding how those datasets relate to the same entities.

Example:

SAP Customer 123

CRM Account 456

Website User 789 → Same Customer

A company can have excellent integrations and still have poor data unification.

That happens when:

Customer identifiers are inconsistent
Records are duplicated
Schemas do not align
Data quality is poor
Relationships are missing
Identity rules are not defined

Therefore:

Integration gets the data connected. Unification gives the data context.

Salesforce Data 360 Data Unification Architecture

A simplified architecture looks like this:

SOURCE SYSTEMS
┌────────┬────────┬────────┬────────┬──────────┐
│  CRM   │  ERP   │Website │Marketing│ Commerce │
└───┬────┴───┬────┴───┬────┴────┬────┴────┬─────┘
│        │        │         │          │
└────────┴────────┴─────────┴──────────┘
↓
CONNECTORS / APIs
↓
DATA INGESTION
↓
DATA LAKE OBJECTS
↓
DATA TRANSFORMATION
↓
DATA MODEL OBJECTS
↓
DATA HARMONIZATION
↓
IDENTITY RESOLUTION
↓
UNIFIED PROFILES
↓
INSIGHTS / SEGMENTS / GRAPHS
↓
ACTIVATION

Salesforce's Data 360 architecture includes data ingestion, data modeling, identity resolution, unified profiles, insights and activation capabilities.

The Data Unification Process

A strong Data 360 unification program can be broken into eight major stages:

Source discovery
Data profiling
Data ingestion
Data mapping
Data harmonization
Identity resolution
Unified profile creation
Activation

Let's examine each stage.

1. Source Discovery

Before unifying data, identify where customer information exists.

Create a source inventory covering:

System	Data	Owner	Update Frequency	Identifier
CRM	Accounts/Contacts	Sales	Real-time	Contact ID
ERP	Orders/Invoices	Finance	Daily	Customer Number
Marketing	Engagement	Marketing	Near-real-time	Subscriber ID
Website	Behavior	Digital	Real-time	User ID
Service	Cases	Support	Real-time	Contact ID

This creates visibility into the current data landscape.

The source inventory should also capture:

Data volume
Data quality
Data sensitivity
API availability
Data ownership
Retention requirements
Business criticality
Latency requirements

2. Data Profiling

Data profiling identifies what is actually inside each source.

For example, a CRM might contain:

First Name

Last Name

Email

Phone

Account

Country

Customer ID

The ERP might contain:

Customer Number

Legal Name

Billing Email

Phone

Tax ID

Country

The website might contain:

User ID

Email

Device ID

Cookie ID

Location

The objective is to determine:

Which fields overlap
Which fields are unique
Which fields are reliable
Which fields are missing
Which fields should be used for identity
Which fields need transformation

3. Data Ingestion

Once the sources are understood, data can be brought into Data 360 through appropriate integration mechanisms.

Salesforce supports multiple data integration approaches including connectors, APIs, MuleSoft, batch ingestion, streaming and federation patterns.

The appropriate method depends on the source.

Example

Historical ERP data:

Batch

Website behavior:

Streaming

Existing warehouse:

Zero-copy or appropriate federation pattern

Custom application:

API

Complex enterprise landscape:

MuleSoft

The architecture should be driven by the business requirement rather than forcing one ingestion mechanism onto every source.

4. Data Lake Objects

In Data 360, ingested source data is represented through Data Lake Objects, or DLOs.

DLOs provide the source-oriented layer of the architecture.

For example:

SAP Customer File → SAP Data Stream → SAP Customer DLO

And:

CRM Contact → Salesforce Data Stream → CRM Contact DLO

The DLO layer allows source data to be brought into the platform before it is harmonized into the common data model.

Salesforce documentation describes DLOs as containers for data brought into Data 360.

5. Data Mapping

Different systems rarely use identical field names.

For example:

CRM:

customer_id

ERP:

customer_number

Commerce:

customer_key

Website:

user_id

A data mapping layer establishes how source fields relate to the Data 360 model.

Example:

Source Field	Source System	Target Concept
Customer_ID	CRM	Customer identifier
Customer_Number	ERP	Customer identifier
Email_Address	Marketing	Email
User_Email	Website	Email
Phone_Number	CRM	Phone
Billing_Phone	ERP	Phone

This mapping is one of the most important parts of a unification project.

Incorrect mappings can create incorrect relationships.

6. Data Model Objects

After source data is mapped, it can be represented using Data Model Objects, or DMOs.

DMOs provide a standardized business representation of data.

The simplified flow is:

Source Data → DLO → Mapping → DMO → Harmonized Data

For example:

CRM Contact

ERP Customer

Marketing Subscriber

Website User → Individual / Contact-related model

The exact mapping depends on the business model and implementation.

Salesforce's Customer 360 Data Model provides standardized structures for connecting customer and business information across domains.

DLO vs DMO in Data Unification

Understanding DLO and DMO is critical.

DLO	DMO
Source-oriented	Business-oriented
Represents ingested data	Represents harmonized data
Closely related to source schema	Uses standardized model
Supports ingestion	Supports downstream use
Preserves source context	Creates common meaning

A practical way to remember it:

DLO = What came from the source

DMO = What that data means in the enterprise model

7. Data Harmonization

Data harmonization makes information from different sources consistent.

Consider:

CRM:

United States

ERP:

USA

Website:

US

These may represent the same country.

Similarly:

CRM:

+1 312 555 1234

ERP:

312-555-1234

Website:

13125551234

These values may represent the same phone number.

Harmonization can involve:

Standardization
Normalization
Transformation
Data type conversion
Value mapping
Date normalization
Address normalization
Phone normalization
Currency handling

The goal is to make different datasets comparable and usable together.

8. Identity Resolution

Identity resolution is where data unification becomes substantially more powerful.

Suppose Data 360 receives:

Record A

Name: Vivek Sharma

Email: [email protected]

Source: CRM

Record B

Name: V Sharma

Email: [email protected]

Source: Marketing

Record C

Name: Vivek S.

Phone: +91 XXXXX XXXXX

Source: Support

The platform needs to determine whether these records represent the same individual.

Salesforce describes identity resolution as the process of resolving disparate source records into unified profiles.

How Identity Resolution Works

Identity resolution generally involves two important concepts:

Match Rules

Determine whether records should be considered a match.

Reconciliation Rules

Determine which information should be used when multiple source records contain different values.

For example:

CRM Email:

[email protected]

Marketing Email:

[email protected]

Website Email:

[email protected]

These records have a strong matching signal.

But suppose:

CRM Phone:

+91 XXXXX1111

ERP Phone:

+91 XXXXX2222

The architecture needs rules for determining which value should be trusted or how both should be represented.

This is why identity resolution should be designed as a business-governance process, not simply a technical configuration.

Match Rules in Data 360

Match rules can be designed around attributes such as:

Email
Phone
Name
Address
Customer ID
External ID
Account identifier
Other business identifiers

The right combination depends on the organization.

For example:

Strong Match

Exact Email

+

Exact Customer ID

Broader Match

Normalized Name

+

Phone

+

Postal Code

A good implementation should balance:

False positives

Two different customers incorrectly merged.

and:

False negatives

The same customer incorrectly kept as separate profiles.

Reconciliation Rules

Matching answers:

Are these records related?

Reconciliation answers:

Which source should be trusted for this attribute?

For example:

Attribute	Preferred Source
Invoice Status	ERP
Opportunity Owner	CRM
Campaign Engagement	Marketing
Product Usage	Application
Support Case Status	Service
Customer Email	CRM or governed master source

This creates a source-priority model.

Without reconciliation rules, conflicting source information can become difficult to manage.

Unified Profile

After identity resolution, Data 360 can create a unified profile representation.

Conceptually:

CRM Record

+

ERP Record

+

Marketing Record

+

Website Record

+

Support Record → Unified Profile

The unified profile can connect related source records rather than requiring the organization to replace every source system with one master record.

This distinction is important.

A unified profile is not necessarily a replacement for the organization's systems of record.

The ERP can remain authoritative for financial transactions.

The CRM can remain authoritative for sales ownership.

The marketing platform can remain authoritative for campaign interactions.

Data 360 provides a connected view across those systems.

Data Unification and Customer 360

Customer 360 is the business outcome that many organizations want from data unification.

A unified customer view may include:

Identity

Name
Email
Phone
Address
Customer identifiers

Sales

Accounts
Opportunities
Products
Pipeline
Revenue

Marketing

Campaigns
Email engagement
Journey activity
Preferences

Commerce

Orders
Products
Cart activity
Purchase frequency

Service

Cases
Service interactions
Entitlements
Support history

Behavioral

Website activity
Application activity
Product usage

Together, these create a more complete customer context.

Data Unification for B2B Organizations

B2B unification is more complex than simple person-level matching.

A business relationship may involve:

Parent Company → Subsidiary → Account → Contacts → Buying Committee → Opportunities → Orders → Contracts → Service Cases

Data 360 architecture therefore needs to represent both:

Individual identity
Account relationships

This can help organizations understand not only who a customer is but also which organization they belong to and how their activities relate to the broader account.

Data Unification for B2C Organizations

B2C organizations often face a different problem.

A customer may interact anonymously before becoming known.

For example:

Anonymous Visitor → Cookie ID → Device ID → Email Signup → Known Customer → Purchase

The architecture needs to connect these interactions when sufficient identity signals become available.

This can support:

Personalization
Customer journey orchestration
Retention
Commerce
Marketing
Service

Identity resolution therefore becomes a critical component of B2C architecture.

Data 360 Unification for Sales

Sales teams can benefit when customer information is fragmented across CRM, ERP and other systems.

A unified architecture could connect:

Account

+

Contacts

+

Opportunities

+

Orders

+

Revenue

+

Product Usage

+

Service History

This provides sales teams with broader context for account planning.

Potential use cases include:

Account prioritization
Cross-sell identification
Upsell opportunities
Customer health
Revenue analysis
Renewal planning

Data 360 Unification for Customer Service

Service teams often need information from several systems to resolve a customer issue.

A support representative may need:

Customer identity
Product ownership
Order history
Warranty
Previous cases
Subscription
Payment status
Customer preferences

A unified profile can connect these data points.

Customer → Orders

+

Products

+

Cases

+

Subscriptions

+

Interactions

This can reduce the need for agents to search across multiple applications.

Data 360 Unification for Marketing

Marketing teams can use unified data to build audiences based on more complete customer context.

For example:

Customer

+

Purchase History

+

Engagement

+

Website Activity

+

Preferences → Unified Profile → Segment → Campaign

Instead of targeting customers based only on email engagement, marketing can incorporate transactional and behavioral signals.

Data Unification and AI

AI systems need context.

Consider an AI assistant answering:

"Why did this customer contact us three times this month?"

CRM data alone might show the support cases.

But a unified customer profile could potentially connect:

Previous cases
Recent orders
Product usage
Marketing interactions
Account status
Customer preferences

This creates a richer context layer.

Data 360's role in an AI architecture is therefore not simply data storage.

It can serve as a source of trusted, connected business context.

Salesforce's current Data 360 architecture positions unified data as a foundation for AI, automation and agentic experiences.

Data Unification and Agentforce

Agentforce can benefit from broader customer context when Data 360 connects information across enterprise systems.

A simplified architecture is:

Enterprise Systems → Data 360 → Identity Resolution → Unified Customer Context → Agentforce → Reasoning → Action

For example, a service agent could potentially use:

Customer profile
Order history
Service cases
Product information
Knowledge
Customer preferences

to provide a more contextual response.

The quality of the AI experience depends heavily on the quality, accessibility and governance of the underlying data.

Data Quality in Salesforce Data 360 Unification

Unification cannot compensate for fundamentally poor source data.

Consider:

John Smith

[email protected]

Jhon Smith

[email protected]

John S.

[email protected]

The architecture needs enough evidence to determine which records relate to the same person.

Before implementing identity resolution, organizations should assess:

Duplicate rates
Missing emails
Invalid phone numbers
Address quality
Identifier consistency
Null values
Formatting differences
Historical data quality

Data quality should therefore be treated as a core implementation workstream.

Data 360 Data Unification Best Practices

1. Start With Priority Use Cases

Do not attempt to unify every data source on day one.

Start with use cases that have measurable value.

Examples:

Customer 360 for sales
Service agent context
Marketing segmentation
Customer retention
AI agent grounding

2. Identify the Most Important Identity Attributes

Determine which attributes provide reliable matching signals.

Potential attributes include:

Email
Phone
Customer ID
Account ID
External ID
Name
Address

Do not assume that every attribute is equally reliable.

3. Define Source Ownership

Document which system owns each important attribute.

For example:

ERP → Invoice

CRM → Opportunity

Marketing → Campaign Engagement

Service → Case

Commerce → Order

This makes reconciliation easier.

4. Use the Standard Data Model Where Possible

Avoid creating unnecessary custom structures.

Use the standard Customer 360 Data Model where it fits.

Extend it only where business requirements justify customization.

5. Separate Identity From Enrichment

Identity determines:

Who is this?

Enrichment determines:

What do we know about them?

Keep these concepts separate.

6. Monitor Match Quality

Measure:

Match rate
Duplicate rate
False-match rate
Unmatched records
Source-specific quality
Identity confidence

Do not assume that a high match rate automatically means high-quality unification.

7. Design for Continuous Improvement

Identity rules should evolve as the organization learns more about its data.

Review:

New data sources
New identifiers
Duplicate patterns
Business changes
Customer lifecycle changes

Common Data 360 Unification Challenges

Challenge 1: Different Customer IDs

Each system uses its own identifier.

Solution: Establish a cross-system identity strategy.

Challenge 2: Duplicate Customers

Multiple systems contain duplicate records.

Solution: Use carefully designed matching and reconciliation rules.

Challenge 3: Conflicting Data

Different systems contain different values.

Solution: Establish attribute-level source priorities.

Challenge 4: Poor Data Quality

Missing or incorrect data reduces match quality.

Solution: Implement data-quality processes before and during unification.

Challenge 5: Over-Unification

Two similar records are incorrectly merged.

Solution: Use conservative match rules for sensitive entities.

Challenge 6: Under-Unification

The same customer remains fragmented.

Solution: Introduce additional identity signals where appropriate.

Challenge 7: Unclear Business Ownership

Technical teams may configure identity rules without business context.

Solution: Involve data owners and business stakeholders in identity governance.

Salesforce Data 360 Data Unification Implementation Roadmap

Phase 1: Business Discovery

Define:

Business objectives
Priority use cases
Users
Data consumers
Success metrics

Phase 2: Data Discovery

Inventory:

Systems
Objects
Fields
Identifiers
Data owners
Data quality

Phase 3: Data Modeling

Define:

DLOs
DMOs
Relationships
Standard objects
Custom objects

Phase 4: Data Quality

Assess:

Duplicates
Missing data
Invalid values
Standardization requirements

Phase 5: Identity Strategy

Define:

Match rules
Reconciliation rules
Identity attributes
Source priorities
Duplicate strategy

Phase 6: Integration

Implement:

Connectors
APIs
Data streams
Transformations
Middleware
Federation where appropriate

Phase 7: Unification

Validate:

Identity resolution
Unified profiles
Relationships
Data quality
Match accuracy

Phase 8: Activation

Use unified data for:

Segmentation
Marketing
Sales
Service
Analytics
AI
Agentforce

Phase 9: Governance

Continuously monitor:

Match quality
Data quality
Source changes
Identity rules
Security
Business outcomes

Data 360 Unification KPIs

A Data 360 implementation should measure more than the amount of data connected.

Useful KPIs include:

Data Quality

Duplicate rate
Missing-value rate
Invalid-record rate
Data freshness

Identity

Match rate
Unmatched rate
False-match rate
Profile completeness

Integration

Ingestion success rate
Processing latency
Failed records
API errors

Business

Marketing conversion
Sales productivity
Service resolution time
Customer retention
Cross-sell rate
AI response quality

The business KPIs should ultimately determine whether the unification program is delivering value.

Salesforce Data 360 Data Unification Checklist

Discovery

Source systems identified
Data owners identified
Priority use cases defined
Business KPIs established

Data

Data quality assessed
Customer identifiers documented
Source-of-truth defined
Field mappings created
Data model designed

Identity

Match rules defined
Reconciliation rules defined
Identity attributes selected
Duplicate strategy established
Match quality tested

Architecture

DLO strategy defined
DMO strategy defined
Integration patterns selected
Transformation strategy defined
Activation architecture designed

Operations

Monitoring implemented
Data-quality dashboards created
Error handling configured
Governance ownership assigned
Continuous optimization process established

How MoreYeahs Can Help With Salesforce Data Unification

Data unification becomes most valuable when it is connected to the broader Salesforce architecture.

MoreYeahs provides Salesforce implementation and integration services and states that it has developed integrations with SAP, NetSuite, Dynamics 365 and custom systems using real-time APIs, near-real-time middleware and batch approaches. The company also highlights data mapping, error handling and monitoring within its Salesforce integration work.

For organizations implementing Data 360, the practical work can include:

Source-system assessment
Data architecture
Data modeling
Integration design
Data mapping
Identity strategy
Salesforce integration
Data quality
Activation
AI and Agentforce readiness
Ongoing optimization

The goal should be to create a connected data architecture that fits the organization's existing systems rather than forcing every business process into a single platform.

Final Takeaway

Salesforce Data 360 data unification is not simply about putting customer records into one platform.

The real challenge is making information from different systems understandable as one connected business context.

A successful architecture follows this progression:

Source Systems → Ingestion → DLO → Mapping → DMO → Harmonization → Identity Resolution → Unified Profile → Insights → Activation

Every stage matters.

Integration connects the systems.

Data modeling creates common meaning.

Harmonization makes different formats comparable.

Identity resolution determines which records belong together.

Reconciliation establishes how conflicting information should be handled.

Unified profiles provide connected customer context.

Activation turns that context into business action.

That is why data unification should be treated as both a technical architecture initiative and a data-governance initiative.

When those two sides work together, Data 360 can provide a foundation for more connected sales, service, marketing, analytics and AI experiences.

Frequently Asked Questions

Salesforce Data 360 data unification is the process of connecting data from multiple systems, harmonizing it through a common data model, resolving identities and creating unified customer or business profiles.

Identity resolution determines which records from different sources represent the same individual or entity and uses that information to create unified profiles.

Integration connects systems and moves or accesses data. Unification determines how records from those systems relate to the same customers, accounts or other entities.

Data Lake Objects represent data brought into Data 360 and provide a source-oriented layer before data is harmonized into the Data Model Object layer.

Data Model Objects represent harmonized data using the Data 360 data model and provide standardized structures for downstream use.

Match rules determine whether records from different sources should be considered related during identity resolution.

Reconciliation rules help determine how conflicting attributes from multiple matched records should be represented or prioritized.

Not necessarily. Salesforce describes unified profiles as connecting matching source records rather than simply replacing all source-system records with one master record.

Yes. Data 360 can integrate with external enterprise systems, allowing CRM, ERP and other datasets to be modeled and connected within a broader customer-data architecture.

Yes. Salesforce documents real-time capabilities for supported Data 360 scenarios, including real-time identity resolution and downstream actions.

Data 360 can connect customer information from multiple systems, harmonize the data, resolve identities and provide a unified customer context for sales, service, marketing, analytics and AI.

Unified Data 360 information can provide broader customer and business context for Salesforce AI and Agentforce use cases, subject to the specific architecture, permissions and implementation.