Salesforce Data Cloud Is Now Data 360: What Changed, What Didn't
If you learned this product as Salesforce Data Cloud, you now have to search for it as Data 360. The rename landed at Dreamforce 2025 and went global on 13 October 2025, folded into the wider Agentforce 360 announcement. Nearly a year on, the confusion has not settled: the Trailhead exam guide still lives at a Salesforce-Certified-Data-Cloud-Consultant-Exam-Guide URL, half the Help articles say one name, half say the other, and every consultancy deck built before October 2025 is now using vocabulary that no longer matches the product.
This post is the short version of what actually changed under the name, what did not, and the two or three places where the rename has real consequences for how you work.
Last verified against Salesforce Help and Trailhead on 13 September 2026.
The short answer
Data 360 is Data Cloud. Same engine, same data model, same objects, same limits, same billing meters. The rename is a positioning change, not a re-platform. Nothing you built in Data Cloud needs migrating, re-pointing, or re-certifying because of it.
What did change in the same window is the story the product is asked to tell. Data Cloud was sold as a CDP — a place to unify customer records and push segments into marketing channels. Data 360 is sold as the grounding layer for Agentforce: the thing that decides whether an AI agent answers from your real, governed, current data or hallucinates something plausible.
That shift is why the rename matters more than a find-and-replace. It changes which capabilities get roadmap attention, which ones get deprecated quietly, and which questions an exam will ask you.
This is the sixth name, not the first
| Era | Name |
|---|---|
| Original | Customer 360 Audiences |
| Rebrand | Salesforce CDP |
| Marketing Cloud era | Marketing Cloud Customer Data Platform |
| 2022 announcement | Salesforce Genie |
| 2023–2025 | Salesforce Data Cloud |
| Oct 2025 onward | Data 360 |
Six names for one lineage. This is worth knowing for a practical reason, not a trivia one: when you search for how to do something, you will land on documentation, blog posts and Stack Exchange answers written under any of those six names, and the older ones describe a genuinely different product surface. A Genie-era post about "data streams" is not wrong, but a CDP-era post about segment builder may describe a UI that has since been replaced twice.
Rule of thumb: if a result predates October 2023, treat the concepts as valid and the clicks as fiction.