Resources /
Blog

What Is Salesforce Data Cloud (Now Data 360)?

Submit your details to get a book

10
Min Read
Resources /
Blog

What Is Salesforce Data Cloud (Now Data 360)?

Download

Submit your details to get a book

10
Min Read
What is Salesforce Data Cloud: a connected hub on a hexagon platform, linked to database, cloud, chart, agent and check tiles
What is Salesforce Data Cloud: a connected hub on a hexagon platform, linked to database, cloud, chart, agent and check tiles

Salesforce Data Cloud is the data engine built into Salesforce that pulls customer data from many data sources into real-time customer profiles for segments, analytics, automation and Agentforce.

On October 14, 2025, Salesforce renamed it Data 360 (formerly Data Cloud), and the functionality did not change.

Below are the key terms and moving parts of the platform. The last section covers how to test, deploy, govern and protect it once it is live.

What is Salesforce Data Cloud?

Salesforce calls Data 360 "the only data engine native to Salesforce" in its Data 360 guide. Its marketing pages state that "Data 360 is a CDP," or customer data platform, that brings website, CRM, email, mobile app, commerce and service data into one real-time profile.

Native here means Data 360 metadata is stored as Salesforce metadata, so every Salesforce app can use it right away. Salesforce's Architects guide says Data 360 runs on Hyperforce and "does not replace existing enterprise investments."

What is Data 360 used for?

In Salesforce's Trailhead examples, marketers build audiences from first-party data for ad platforms such as Meta and Google Ads. Sales and service reps see insights like account lifetime value or open case totals right on CRM records.

The same unit describes analyzing subscription and usage data to improve sales projections and build customer segments. Data 360 also supplies the company data that Agentforce agents are grounded in, covered in the Agentforce section below.

Is Data Cloud now Data 360?

Yes. Trailhead states that "As of October 14, 2025, Data Cloud has been rebranded to Data 360" and that "the functionality and content remains unchanged."

The unit also notes: "During this transition, you may see references to Data Cloud in our application and documentation." When you search Help or Trailhead, try both names.

How does Salesforce Data 360 work?

Salesforce organizes how Data 360 works around five stages: connect, harmonize, unify, analyze and act. Data comes in, gets mapped to a common model, is matched into profiles, then drives insights and actions.

Connect: data streams and data lake objects

A data stream connects one system to Data 360 in batch, near real-time or streaming mode, using one of over 270 connectors. Ingested records land in data lake objects (DLOs), which the Architects guide calls "the core persistent storage layer within Data 360."

Harmonize: data model objects

Next, DLO fields are mapped to data model objects (DMOs), as Salesforce's guide on modeling data in Data 360 shows. The Architects guide calls DMOs "the final, harmonized and structured data layer."

Unify: identity resolution and customer profiles

This step uses match rules to decide which source profiles belong together and reconciliation rules to pick one value for fields like name. Trailhead says the result is a single customer and account view that consolidates data from various sources.

A unified profile is not a golden record that replaces the original records. The Architects guide says unified profiles "serve as a set of keys that unlock your source data," and that reconciliation "doesn't overwrite any existing data."

Analyze and act: insights, segments and activation

Calculated insights are metrics and KPIs built from batch or streaming data. The Architects guide describes segmentation as turning unified profiles into audiences, with activation as the final step that sends them to destinations.

Data actions turn data changes into automation. The Architects guide says they "continuously monitor incremental data for changes," and Trailhead says they use events and data changes to trigger flows.

Data 360 terms at a glance

Data 360 has its own vocabulary, and most of it maps to one step in the flow above. This table gives each term in plain words, with the step it belongs to.

TermWhat it isStep
Data streamA source connected to Data 360, in batch or streaming modeConnect
Data lake object (DLO)The core storage layer for ingested dataConnect
Zero copyUsing lake or warehouse data without duplicating it, in both directionsConnect
Data model object (DMO)The harmonized, structured layer mapped from DLOsHarmonize
Identity resolutionMatch and reconciliation rules that link records into unified profilesUnify
Calculated insightAn aggregated metric or KPI built from batch or streaming dataAnalyze
SegmentAn audience built from customer profilesAnalyze
ActivationSending segments to marketing, ad and other destinationsAct
Data actionAn event or data change that triggers a flowAct
Data spaceA logical container that separates data and metadata, with access set by permission setsGovern

What is zero copy in Data 360?

With zero copy, Data 360 uses data where it already lives in an external lake or warehouse instead of moving it in. Salesforce's Data 360 guide says Data 360 is "built on a Zero Copy foundation."

Salesforce says Data 360 can "securely share data bi-directionally between Data 360 and leading data lakes and warehouses." Trailhead names Snowflake, Databricks and BigQuery as zero-copy sources.

How do data spaces and governance control access in Data 360?

A data space is "the fundamental logical container for organizing all data and metadata within Data 360," according to the Architects guide. Admins create data spaces by brand, region or business unit and grant access through permission sets, as Salesforce Help explains in Secure Your Data with Data Spaces.

Data spaces control access, not where data is stored. Trailhead says plainly that "Data spaces don't solve data residency needs," so storage location is a question of data residency on Hyperforce.

Even for access, a data space is a broad filter that the Architects guide calls "coarse grained access control." Finer rules come from Data 360 Governance, which adds AI-recommended tags that mark data as HIPAA, GDPR or PII, policies at field, object and record level, and dynamic masking "without altering the underlying data."

Those controls cover Data 360 itself, and the rest of the org still needs its own rules. Our guide to Salesforce data governance best practices covers the CRM side, and a dedicated post on Data 360 governance and security is coming.

How does Data 360 power Agentforce?

Salesforce's Data 360 guide calls Data 360 "the core of Agentforce." The Architects guide describes keyword, vector and hybrid indexing over unstructured data, which supports retrieval-augmented generation (RAG) for agents.

One concrete dependency is the Agentforce Data Library. Salesforce Help says you must have Data 360 set up to use data libraries, and that they consume Data 360 credits.

Agents answer from the data they are grounded in, so errors in that data can reach their answers. That makes agents learning from the wrong data a governance problem as well as an AI one.

Teams putting agents into production should pair Data 360 controls with agent-aware governance across the org. A separate post on why agents need governed Data 360 data is planned.

What should you plan before turning on Data 360?

Several early decisions shape everything that follows. Settle these before the first data stream goes live:

  • Which data sources to ingest first, and how many data spaces you need
  • Who owns match and reconciliation rules, since those rules decide which records become one profile
  • Where changes are tested and how they reach production
  • How consent, personal and health data are tagged
  • Who watches credit consumption as volumes grow

Budget early, too. Salesforce states that Data 360 pricing is consumption-based, so check current pricing and your contract before sizing ingestion or activation.

A step-by-step Data 360 implementation checklist and a guide to Data 360 compliance for regulated industries are both on the way.

How do you run Data 360 safely?

Data 360 configuration is a Salesforce change like any other, but it now feeds marketing, analytics and agents at once. It deserves the same discipline as the rest of your releases: test first, promote through a controlled path, govern who changes what, and protect the sources.

Test in a sandbox first

Data 360 works in sandboxes, but a Data 360 sandbox holds configuration only. Production data is not copied, even in Partial Copy and Full sandboxes, though Trailhead says data streams, DMOs, calculated insights and segments are.

Unified profiles "must be built from scratch" in the sandbox, and Salesforce recommends loading sample data to test with. If you seed a sandbox with sample data, mask sensitive data in sandboxes too, and our guide on how to use Data 360 in a sandbox goes deeper.

Promote changes with data kits

Salesforce's route from sandbox to production is a DevOps data kit. Trailhead says a kit supports "controlled, repeatable promotion of configuration changes" between your own environments, and it can bundle data streams, DMOs, calculated insights, identity resolution rules and segments.

Teams can deploy a kit with the Salesforce CLI. Watch two details from Trailhead: a new data space name must exist in the target org, and a calculated insight that a segment depends on must deploy first.

The same release habits used for deploying agents through a DevOps pipeline apply here, from version control to approvals. A detailed post on deploying Data 360 changes to production will follow.

Govern who changes what

Data 360 policies control who can see data, but they don't approve a change to a match rule or segment. Add approvals, separation of duties and an audit trail, so you can show who changed what and when.

Personal and health data in profiles make this more pressing. Tie your Data 360 change process to your existing GDPR compliance controls and your HIPAA evidence.

Protect the source systems and the configuration

Ingested data is a copy of what your source systems hold, and the Architects guide describes profiles as keys back to that source data. So recovery starts with the CRM records, files and metadata that feed Data 360, plus the org configuration around it.

Review your Salesforce backup solutions with that in mind, and make sure you back up Salesforce metadata and configuration as well as records. A post on how to back up Salesforce Data 360 is planned.

Flosum DevOps runs Salesforce releases through version control, approvals and an audit trail, with one-click rollback, and sandbox management covers provisioning, seeding and masking. For data, Flosum Backup & Archive protects Salesforce data, metadata, files and attachments, the records that feed systems like Data 360.

FAQs

Is Salesforce Data Cloud now Data 360?

Yes, Salesforce rebranded Data Cloud as Data 360 on October 14, 2025, and Trailhead says the functionality did not change. The old name still appears in parts of the app and documentation, so treat both names as the same product when you search Help or Trailhead.

What is Salesforce Data Cloud used for?

Teams use Data 360 to connect Salesforce, web, mobile and warehouse data, unify it into customer profiles, and act on it. Common uses are audience segments for marketing, calculated insights on CRM records, flows triggered by data changes, and grounding Agentforce agents in company data.

What is zero copy in Salesforce Data 360?

Zero copy lets Data 360 work with data that stays in an external lake or warehouse, such as Snowflake, Databricks or BigQuery, without duplicating it. Salesforce supports it in both directions, federating external data in and sharing Data 360 data out.

Can you use Data 360 in a Salesforce sandbox?

Yes, Data 360 supports sandboxes, but it copies only configuration such as data streams, data model objects, calculated insights and segments. No production data is replicated, so teams load small sample data sets and rebuild unified profiles to test, as described in Data 360 in a Sandbox.

How do you deploy Data 360 changes from sandbox to production?

Salesforce's method is a DevOps data kit, which bundles supported Data 360 components so a team can promote configuration between its own environments. Teams can deploy the kit with the Salesforce CLI, checking that data spaces exist in the target org and that dependencies like calculated insights deploy first.

Book a demo to talk through how your team tests, releases and protects Salesforce changes.

Table Of Contents
Author
Stay Up-to-Date
Get flosum.com news in your inbox.

Thank you for subscribing

Ship Salesforce changes faster
Teams on Flosum report 40% higher development velocity and 75%
fewer merge conflicts.
Free to start  |  No credit card required