The Ultimate Guide To Merging Data Cloud With Salesforce CRM
Data Cloud, now called Data 360, only pays off when its unified profiles and insights show up where your sales and service teams work: on the Contact, Account and Lead record, and inside Flow. This guide walks through the whole path, from the CRM connector to related lists, copy fields and Data Cloud-triggered flows, with the limits that catch teams out.
Key Takeaways
- Merging Data Cloud with Salesforce CRM is a loop: CRM and external data flow in through data streams, get unified by identity resolution, and flow back onto CRM records as enrichments and flow triggers.
- There are now three enrichment types: related lists, Direct-DMO related lists and copy fields. Only the first and the third need a unified profile.
- Copy fields are no longer a Contact-only feature. They can write to Account, Lead, Opportunity, Case, Order, Quote, custom objects and more.
- The first copy field sync is a full sync that overwrites existing values in the target field, and they cannot be recovered. Always map to a new field.
- Related lists query Data 360 every time the page loads, and every enrichment consumes credits. Design with consumption in mind from day one.
- Data Cloud-triggered flows turn a calculated insight, such as a VIP flag, into action in CRM, but their timing depends on your data stream refresh schedule.
Most teams that buy Data Cloud do not fail at ingesting data. They fail at the last mile. The unified profile exists, the lifetime value is calculated, and then nobody in sales or service ever sees it, because it lives in a separate app instead of on the record they open fifty times a day. Merging Data Cloud with Salesforce CRM is the work of closing that gap.
This guide is a practical walkthrough for Salesforce admins, architects and RevOps leaders at growing and mid-market companies. It follows one running example: show a customer's latest transactions on the Contact page, calculate their lifetime value (LTV), and alert the Contact owner when someone becomes a VIP. It explains each Data 360 building block in the order you will configure it.
What Does Merging Data Cloud With CRM Actually Mean?
Merging Data Cloud with Salesforce CRM means ingesting CRM and external data into Data 360, unifying it into profiles with identity resolution, computing insights such as lifetime value, and then surfacing those results on CRM records and in automation, through related lists, copy fields and Data Cloud-triggered flows. It is a round trip, not a one-way export.
Salesforce describes Data 360 as a platform to "ingest, harmonize, unify, and analyze streaming and batch data" and use it across Customer 360 applications (Salesforce Help: Data 360). It stores data in a lakehouse that sits alongside your CRM org. The CRM itself does not change shape: Data 360 data appears on records through enrichments and reaches Flow through data actions.
Connect and ingest
The Salesforce CRM connector and other connectors bring records into Data 360 as data streams, in batch or streaming mode.
Harmonize and unify
Fields are mapped to the standard data model, and identity resolution links records about the same person or account.
Compute insights
Calculated insights and data transforms turn raw events into metrics such as LTV, purchase frequency or a VIP flag.
Enrich and act in CRM
Related lists, copy fields and flows put the results in front of users and trigger work inside Salesforce.
When Is Connecting Data 360 To Your CRM Worth It?
It is worth it when the data your reps and agents need lives outside the CRM, in commerce, billing, product usage, web or a data warehouse, and you need it joined to the right Contact or Account. It also fits when duplicate or fragmented customer records hide the full picture, or when you want automation and Agentforce to act on that combined data.
It is probably not worth it yet when all the data you need already lives in Salesforce objects, a roll-up summary or a report would answer the question, or one nightly integration into a custom field does the job. Data 360 consumes credits on ingestion, unification, queries and enrichment, so it should solve a problem that simpler tools cannot.
If the answer is yes, the rest of this guide follows the order in which you will actually build: setup, ingestion, unification, insights, then the enrichments and flows your users will see.
How Data Flows From CRM Into Data 360 And Back
Every Data Cloud and CRM integration follows the same five layers. Each one depends on the layer above it, which is why a broken enrichment is often a mapping or identity resolution problem upstream.
Salesforce CRM connector, starter bundles and other sources
CRM objects and external sources such as Amazon S3, a website SDK or a warehouse arrive as data streams.
Data lake objects (DLOs) mapped to data model objects (DMOs)
Raw fields are mapped to the standard Customer 360 Data Model or to custom DMOs, with relationships between them.
Unified Individual and Unified Account profiles
Match rules link source records about the same person or company. Reconciliation rules choose which value to show.
Calculated insights and data transforms
Metrics such as lifetime value, order count or a VIP flag are produced per profile.
Related lists, copy fields, data actions and Data Cloud-triggered flows
Users see the data on Contact, Account, Lead and other records, and automation reacts to changes.
How Do You Set Up Data 360 And Connect Your CRM Org?
Assign the Data Cloud Architect permission set to your admin, let Data 360 connect to its home org automatically, deploy the Sales or Service starter data bundle from the Data Streams tab, and give every other user a standard Data 360 permission set plus access to the right data space. Custom permission sets are discouraged because the standard ones update each release.
Data 360 runs in Lightning Experience on Developer, Enterprise, Performance and Unlimited editions (Salesforce Help: editions and licences). The setup sequence looks like this:
- 1
Assign admin access. The permission set formerly called Data Cloud Admin is now Data Cloud Architect. Marketing Manager and Marketing Specialist became Activation Manager and Activation Specialist, and Data Cloud User covers read-only access (Salesforce Help: permission sets). Some screens now show "Data 360" in place of "Data Cloud" in these labels.
- 2
Confirm the CRM connection. Data 360 connects to the org it is set up in automatically, and you can add connections to other orgs. Connecting an org creates the Data Cloud Salesforce Connector permission set, which controls which objects and fields are readable. Big objects cannot be ingested.
- 3
Deploy a starter data bundle. From the Data Streams tab choose New, then Salesforce CRM, then a bundle such as Sales or Service. Bundles create the data streams and map standard objects such as Account, Contact and Lead to DMOs, with relationships, so standard fields need no manual mapping (Salesforce Help: starter bundles).
- 4
Choose batch or streaming refresh. In batch mode the CRM connector checks for changes every 10 to 15 minutes. Streaming mode reflects changes as soon as they are made in the org (Salesforce Help: CRM connections).
- 5
Plan data spaces and lock down admin reach. Every org has a default data space, and more need the Data Spaces add-on. With the default "Allow All" policy, System Administrators can query every DMO, and Salesforce recommends deleting or scoping that policy.
What Are Data Streams, DLOs And DMOs?
A data stream is a connection to a source plus the data it ingests. Each stream lands in a data lake object (DLO), a storage container that keeps the source's shape. You then map DLO fields to data model objects (DMOs), the harmonized model every Data 360 feature reads from. Enrichments, insights and flows all work on DMOs, not DLOs.
| Building block | What it holds | In the running example |
|---|---|---|
| Data stream | The connection to a source and its ingested data, batch or streaming | A CRM stream for Contacts and an Amazon S3 stream for transactions |
| DLO | Raw ingested data in its source shape, categorized as Profile, Engagement or Other | A Transactions DLO categorized as engagement data |
| DMO | Harmonized data on the standard Customer 360 Data Model or a custom model | A custom Transactions DMO with a relationship to Individual |
| Fully qualified key | A source key plus a key qualifier, so IDs from two systems never collide | The S3 customer ID qualified separately from the Salesforce Contact ID |
Starter bundles pre-map standard CRM fields. Custom objects and custom fields still need manual mapping, and an external source such as transaction data always does. In the running example, you would create a custom Transactions DMO, map every DLO field to it, and add a relationship from the transaction's customer ID to the Individual DMO, so every purchase can later be traced to a person (Trailhead: map and unify data).
Choose the DMO category carefully. Salesforce generally does not allow you to change a DMO's category after it is created (Salesforce Help: data model objects).
How Does Identity Resolution Create A Unified Profile?
Identity resolution applies a ruleset to your mapped profile data. Match rules decide which source records belong to the same person or account, and reconciliation rules decide which value to display. The result is the Unified Individual (or Unified Account) DMO, which related list and copy field enrichments use to find the right CRM record.
Match rules combine one or more criteria, all of which must be met. Methods include exact, fuzzy and normalized matching for email, phone and address. Adding more match rules widens matching (Salesforce Help: match rules). Reconciliation rules offer Last Updated, Most Frequent and Source Priority, set per object and overridable per field (Salesforce Help: reconciliation rules).
Two points are commonly misunderstood. First, Salesforce states that unified profiles "aren't golden records": identity resolution links records and never overwrites the source data in your CRM. Second, rulesets process anywhere from every 60 minutes to every 24 hours depending on the source, so a new Contact does not appear in a unified profile instantly (Salesforce Help: identity resolution). A practical starting ruleset is fuzzy name plus normalized email. Then check the consolidation rate, the share of source profiles that merged, before you tighten or loosen it.
Calculated Insights Or Data Transforms: Which Should Compute Your Metrics?
Use a calculated insight when you need a metric per profile, such as lifetime value, that you will also segment on or copy to a record. Use a data transform when you need to clean, join or reshape data into a new data object. For real-time signals from web or mobile events, use streaming insights.
| Tool | Best for | Runs | Can feed CRM enrichment? |
|---|---|---|---|
| Calculated insight | Metrics at profile, segment or population level, built visually or in SQL | Batch | Yes: a copy field can read an aggregatable calculated insight object directly |
| Streaming insight | Rolling-window aggregations on real-time engagement data, from one minute | Streaming | Through data actions; not usable in segments or activations |
| Batch data transform | Node-based cleansing, joins, aggregates and filters, on demand or scheduled | Batch | Yes, once its output DLO is mapped to a DMO related to the individual |
| Streaming data transform | Continuous record-by-record reshaping in SQL | Streaming | Yes, through its mapped output DMO |
For the running example, either route works. A calculated insight can sum transaction amounts per Individual to produce LTV and derive a VIP flag above a threshold. A batch data transform can aggregate the Transactions DLO, join it to Contacts and write to a new LTV DLO. That DLO must then be mapped to a DMO and related to the Individual. What matters for CRM enrichment is the last step: the output must be linked back to the individual or unified individual, or the enrichment has nothing to match on (Salesforce Help: insights, batch data transforms).
Related Lists, Direct-DMO Lists And Copy Fields: Side By Side
Data 360 offers three CRM enrichment types. Related lists show Data 360 rows live on Account, Contact and Lead pages through the unified profile. Direct-DMO related lists show rows linked straight to a CRM record ID, with no identity resolution. Copy fields write Data 360 values into real Salesforce fields that reports, formulas and automation can use.
| Question | Related list | Direct-DMO related list | Copy field |
|---|---|---|---|
| Target objects | Account, Contact, Lead | Account, Asset, Case, Contact, Contract, Lead, Opportunity, Order, Product, Work Order, custom objects and more | Account, Asset, Case, Contact, Contract, Invoice, Lead, Opportunity, Order, Product, Quote, custom objects and more |
| Needs identity resolution? | Yes, a Unified Individual or Unified Account | No | Only for unified lookup matching methods |
| Where the data lives | Stays in Data 360, queried on page load | Stays in Data 360, queried on page load | Written into a Salesforce field |
| Usable in reports, formulas, automation | No | No | Yes |
| Best for | Engagement history, such as transactions | Records already keyed to a CRM ID | Single values, such as LTV or a VIP flag |
Object lists from Salesforce Help, enrichment considerations and Direct-DMO related lists, checked October 2026. Data 360 ships features monthly, so confirm against current documentation.
How To Add Data Cloud Related Lists And Copy Fields To A Record
Related list enrichment
Show engagement historyBest for: Showing a customer's recent transactions, orders or web events on the Contact, Lead or Account page.
In Setup, open Object Manager, select Contact, Lead or Account, and choose Data Cloud Related Lists (labelled Data 360 Related Lists in some orgs). Click New, choose Related List, select the data space and the DMO (in the example, Transactions), pick the lookup field, give the list a label and add it to page layouts. Access is controlled by the parent record unless you use enhanced data space security. You then configure columns and order on the page layout, the same way as a standard related list (Salesforce Help: create a related list enrichment).
Engagement-data related lists return only the last seven days by default. To show more, add a date filter or use a dynamic related list. The filter must cover every field mapped to Event Time, or the list silently falls back to seven days.
Direct-DMO related list
No unification neededBest for: Data that already carries a Salesforce record ID or unique key, such as service events keyed to an Asset or Case.
This type needs a many-to-one relationship from the DMO to an ID or text field on the CRM object, and no identity resolution. From Winter '26, Person Account fields can be used as matching fields. Rows cannot hyperlink to a CRM record. If CRM records are merged, refresh the CRM data stream so ID-based lists keep matching (Salesforce Help: Direct-DMO related lists).
Copy field enrichment
Write values into fieldsBest for: A single value, such as lifetime value or a VIP flag, that reps should see, report on and automate from.
1. Create a new target field on the CRM object, such as a currency field for LTV, with a type that matches the source field. 2. Grant the integration user access: in the Customer 360 Data Platform Integration permission set, give Read, Edit, Delete, View All and Modify All on the object and Edit on the target field. The permission set only appears once at least one data action and data action target exist. 3. Create the enrichment under Setup > Integrations > Enrichments > Copy Fields (or from Object Manager). Choose the data space and source object, and pick one of six ID matching methods: Individual, Account, Unified Individual or Unified Account lookup, Primary Key, or Non-Primary Unique Key. Then choose the target object and fields and an optional filter, and select Save and Start Sync (Salesforce Help: create a copy field enrichment).
Under the hood, each copy field uses one data action and one data action target from your licence. The first sync is a full sync through bulk jobs. It can run for hours or days and overwrites any existing values in the target field. After that, syncs are incremental. A transaction with more than 250,000 changes switches back to a full sync, and Salesforce recommends restarting the sync periodically, because incremental syncs can miss data in transactions over 100,000 changes (Salesforce Help: syncing copy fields). Track progress on the Sync History tab.
How Do Data Cloud-Triggered Flows And Data Actions Work?
A Data Cloud-triggered flow starts when conditions you define are met on a data model object, such as a VIP flag turning true. It then runs ordinary Flow elements against Salesforce data, such as sending a custom notification to the Contact owner. Data actions, which power these flows, can also send events to Platform Events, webhooks and other targets.
In Flow Builder, choose New Flow, Start From Scratch, then Data Cloud-Triggered Flow. Select the object and entry conditions (Salesforce Help: trigger flows with Data 360 data). For the VIP example, add a Decision on the VIP flag. Next, get the custom notification type and send it to the owner ID carried on the DMO, with the Contact ID as the notification target. Three rules apply:
- A DMO only triggers the flow if it is mapped as part of a data stream.
- Delays depend on change volume, flow complexity and the data stream's refresh schedule. A batch stream means batch-speed alerts.
- Behind the scenes the flow uses data action functionality, so it shows up as a read-only data action target managed by Flow Integration.
Data actions can also be used directly. They watch DMO and calculated insight object changes and send events to a Salesforce Platform Event, a webhook, Marketing Cloud Engagement or Amazon Kinesis (Salesforce Help: data actions). Flow can also orchestrate Data 360 itself, chaining ingestion, identity resolution, calculated insights and segmentation in an autolaunched flow. These runs are throttled per 24 hours: ingestion four times per stream, identity resolution four times per ruleset, calculated insights three times, and segmentation and activation six times (Salesforce Help: workflow limits).
Other Ways To Bring Data 360 Into Salesforce CRM
Engagement Timeline
A Lightning App Builder widget that shows up to 10 engagement types on Account, Contact, Lead and Person Account records. Viewers need a Data 360 licence and data space access (Salesforce Help).
CRM Analytics, without loading
Explore in Analytics lets CRM Analytics query DLOs, DMOs and calculated insight objects without loading the data. CRM Analytics is an extra-cost licence (Salesforce Help).
Zero copy federation
Query federation and file federation read Snowflake, Databricks, BigQuery, Redshift and others without copying the data in. Optional caching refreshes every 15 minutes to 7 days (Salesforce Help).
Agentforce grounding
Data 360 grounds Agentforce, Tableau and Flow in structured and unstructured data, with vector and hybrid search indexes (Salesforce Help).
For the warehouse side of that story, see our guide to Snowflake and Salesforce Data Cloud, and for relationship-aware profiles, data graphs in Data Cloud.
Common Data Cloud CRM Enrichment Pitfalls (And How To Avoid Them)
Most of these come straight from Salesforce's own considerations and troubleshooting pages (enrichment troubleshooting, enrichment costs). Each one is cheap to design around and expensive to discover in production.
Which Enrichment Should You Use? A Decision Framework
When To Bring In A Data 360 Implementation Partner
The configuration steps above are documented. The hard part is the design behind them: which sources to ingest, how to key them, how strict identity resolution should be, which values deserve a copy field, and how to keep credit consumption predictable. Those decisions are hard to reverse once enrichments are live and users rely on them.
Twopir Consulting helps growing and mid-market companies, as well as enterprise teams, connect Salesforce Data 360 to Sales Cloud, Service Cloud and Agentforce. We implement, rescue, optimize, and integrate complex CRM and revenue systems. That includes the integrations that feed Data 360 and the enrichments and flows that put its data to work. If you are planning a Data Cloud implementation or grounding agents in it through Agentforce data integration, we can map the architecture with you before anything is built.
Get Data 360 Working Inside Your CRM
Book a discovery call with a Twopir Salesforce architect. We will review your sources, identity resolution approach and enrichment plan, and tell you which records, fields and flows will deliver value first.
Schedule a Discovery CallThe Bottom Line
Data 360 earns its cost when its output reaches the people and processes that run your revenue. Build the loop in order: connect and map cleanly, unify with rules you can explain, compute the few metrics that change decisions, and only then enrich records and trigger flows. Pick the enrichment type by how the data will be used, and design for sync behaviour and credit consumption from the start.
- 1
Data Cloud is now Data 360. The features are the same, but labels in Setup and Flow Builder vary.
- 2
Related lists and copy fields depend on identity resolution and a relationship to the individual. Direct-DMO related lists do not.
- 3
Copy fields are the only enrichment that reports and automation can use, and their first sync overwrites the target field.
- 4
Data Cloud-triggered flows react to DMO changes at the speed of the underlying data stream.
- 5
Every enrichment consumes credits, so filter, scope data spaces and monitor usage.
Frequently Asked Questions
Yes. Salesforce rebranded Data Cloud to Data 360 on October 14, 2025, and states that the functionality is unchanged. Setup menus, Flow Builder and documentation still show both names during the transition, so labels such as Data Cloud Related Lists and Data Cloud-Triggered Flow remain in use.
For related list enrichments, yes: they require a completed identity resolution ruleset and a Unified Individual or Unified Account. Direct-DMO related lists do not, because they match directly on a CRM record ID or key. Copy fields only need it when you choose a unified lookup matching method.
Copy fields can write to Account, Asset, Case, Contact, Contract, Invoice, Lead, Opportunity, Order, Product, Quote, custom objects and a few industry objects. The source can be a mapped DMO, Unified Individual, Unified Account or an aggregatable calculated insight object. Person account contact fields cannot be targets.
Yes. The first sync is a full sync that overwrites existing values in the target field, and they cannot be recovered. Later incremental syncs can also overwrite changes users make. Salesforce's guidance is to map copy fields to new, dedicated fields rather than fields people edit.
The most common cause is that the user has no access to the data space the related list reads from. For engagement data, also check the date range: related lists show only the last seven days by default unless a date filter covers every field mapped to Event Time.
Yes. In Flow Builder choose Data Cloud-Triggered Flow, then select a data model object and the conditions that start it. The object must be mapped in a data stream, and timing depends on change volume, flow complexity and the data stream refresh schedule.
Yes. Related list and copy field enrichments are billed as Data 360 queries against Data Services Credits or Flex Credits, depending on your contract. Related lists query each time a page loads. Copy field filters can reduce consumption, and the Digital Wallet shows usage in near real time.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. Since 2014 our team of 40+ consultants and architects has delivered Salesforce Sales Cloud, Service Cloud, Data Cloud and Agentforce, alongside HubSpot and integration platforms such as MuleSoft and Workato, for clients across the US, UK, Australia, UAE and Canada.