If you've heard "Data Cloud" and "Data 360" used interchangeably recently, that's not a mistake on anyone's part — Salesforce rebranded Data Cloud to Data 360 at Dreamforce 2025. We're using both names in this post because most teams we talk to are still catching up on the rename; the underlying product and purpose haven't changed.
The scale, as Salesforce reports it
Data Cloud/Data 360 reportedly surpassed 50 trillion records in fiscal 2025, roughly doubling year-over-year — a scale that puts it among the largest enterprise data layers outside the major hyperscalers. Combined Data Cloud and AI annual recurring revenue reportedly reached $900 million in fiscal 2025, up 120% year-over-year. As with any vendor-reported figures, treat these as directional rather than audited.
Why it's the prerequisite, not a nice-to-have
The pattern we see — and the one behind our own Agentforce commentary — is that agentic AI initiatives stall for a data reason almost every time, not a model reason. An agent is only as good as the unified profile it can reason over. Salesforce's own positioning has shifted the same direction: Data 360, alongside MuleSoft and the newly added Informatica, is now framed explicitly as closing the "enterprise context" gap that limits agent reliability.
What this means practically
- If Agentforce is on your roadmap, Data Cloud/Data 360 work usually needs to happen first, not in parallel — an agent built on fragmented data just automates the fragmentation faster.
- Identity resolution — matching the same customer across systems — is unglamorous work that determines whether every downstream initiative (personalization, segmentation, agents) is trustworthy.
- "We have a data warehouse" and "we have a unified customer profile" are different claims. Data Cloud/Data 360 is built for the second one, inside Salesforce specifically.
Our take
Data Cloud/Data 360 doesn't get the attention Agentforce does, because unifying data isn't as demo-able as an agent answering a question. But in nearly every engagement where an AI initiative actually held up past the pilot, the unglamorous data foundation work happened first. That's the order we'd recommend, even when it's the less exciting phase to sell internally.
Talk to us about your Data Cloud foundation →
Sources referenced for this post
- Futurum Group — "Salesforce Q3 FY 2026: AI Agents, Data 360 Lift Bookings and FY26 Outlook"
- Futurum Group — "Salesforce Q4 FY 2026 Earnings Show Agentic AI Scaling, Guidance Steadies"
- Salesforce Trail — "Salesforce Trends 2026: 7 Shifts Every Professional Should Watch"