Salesforce AI · 9 min read · May 2026
Salesforce Data 360 and Agentforce: The Readiness Work Behind the Reorg
By Thinklytics Partners, Salesforce Data & Agent Practice
Salesforce just reorganized the whole company around Agentforce and Data 360, with Agentforce past $1.2B ARR. The agents only work on a clean data foundation. Here is the readiness work that decides whether your rollout ships.
Frequently asked questions
What changed with Salesforce Data 360 and Agentforce in FY27?
Starting FY27, Salesforce reorganized its reporting into two engines: Agentforce Apps (Sales, Service, Marketing, Commerce, Slack) and Data 360 / Headless Platform (Data 360, MuleSoft, Tableau, Informatica). Agentforce passed $1.2 billion in annualized ARR, up 205 percent, and Data 360 ingested 52 trillion records, up 136 percent. The company is now organized around agents and data, not the old product clouds.
What is Salesforce Data 360?
Data 360 is Salesforce's renamed data layer (formerly Data Cloud): the unified, governed customer data that Agentforce, Sales Cloud, and the rest read from. It resolves identity across systems and is the foundation an agent grounds on. Getting Data 360 right is the prerequisite for everything agentic on the platform.
Why do Agentforce projects need a data foundation first?
An agent acts on the data it reads. If identity is not resolved, definitions are not certified, or feeds are stale, the agent acts confidently and wrong, with no human in the loop. More than half of Agentforce and Data 360 bookings are existing customers expanding, and the ones who succeed fixed the data layer before scaling the agents.
Where does MuleSoft fit in the new structure?
MuleSoft sits in the Data 360 / Headless Platform segment, the faster-growing one. It is how data from systems outside Salesforce arrives reliably for Data 360 and the agents. Integration is the bottleneck for agentic rollouts, not the model, which is why MuleSoft is now part of the data engine rather than a standalone product.
Is this a Salesforce admin job or a data and architecture job?
Increasingly the latter. Salesforce is moving toward an API, MCP, and agent-operable platform, so the value shifts from clicking in the UI to architecting the data, integration, governance, and agents. That is data and AI foundation work, which is the lane we operate in alongside your Salesforce team.
How do we get ready?
Unify and govern your data in Data 360, certify the metric definitions the agents will use, wire reliable integration through MuleSoft, and put governance, audit logging, and human review around the agents before they touch customers. A readiness assessment scopes which of those gaps is yours.