Salesforce Data Cloud, Data 360 & Agentforce: What the Licensing Change Means for Enterprise Buyers

From Data Cloud to Data 360: What Actually Changed

At Dreamforce 2025, Salesforce announced that Data Cloud would be renamed Data 360. The rebrand is not cosmetic. Data 360 repositions the product as the data backbone of the entire Agentforce 360 platform, which encompasses AI agents, automation, industry-specific cloud products, and partner applications. Where Data Cloud was primarily a customer data platform — ingesting, unifying, and activating customer profiles — Data 360 is designed to serve as the grounding layer for AI agent actions across the full Salesforce ecosystem.

For existing Data Cloud customers, the practical implications of the rename are significant. Contracts referencing Data Cloud SKUs will eventually be transitioned to Data 360 SKUs. Salesforce has a documented history of using product renames as an opportunity to introduce commercial changes — new pricing tiers, modified credit consumption rates, and updated terms of service. Any enterprise with an active Data Cloud contract should review their renewal terms carefully and seek explicit contractual continuity provisions that lock current pricing and consumption rates through the transition.

What Data 360 Includes

Data 360 provides the following core capabilities: unified customer profile management (ingesting and harmonising data from multiple Salesforce and third-party sources), real-time segmentation and audience activation, AI model grounding (providing contextual customer data to Agentforce agents so they can take informed actions), data transformation and enrichment workflows, and data sharing through Salesforce's zero-copy architecture with compatible cloud data warehouses.

What Data 360 does not include by default: advanced data governance and lineage tools (available as add-ons or through the Informatica integration Salesforce announced in early 2026), Data Spaces for multi-brand or multi-org data partitioning, and Data Cloud One for cross-organisation data sharing. These capabilities require additional SKUs or consumption credit allocations beyond the base Data 360 contract.

The Agentforce 360 Platform and Its Pricing Structure

Agentforce 360 is Salesforce's umbrella platform for AI agent deployment. It combines Agentforce (the AI agent runtime), Data 360 (the data grounding layer), Einstein AI (prediction and generation capabilities), and Salesforce Flows (automation). The commercial model for Agentforce 360 operates on two parallel billing units: Flex Credits and Agentforce Conversations.

Flex Credits: The Universal Currency

Flex Credits replace the legacy Data Services Credits that Data Cloud used previously. They are designed as a universal consumption currency that spans Data 360 operations (data ingestion, profile unification, segmentation runs), Agentforce agent actions, Einstein AI prompts, speech and voice services, and any other consumption-based Salesforce service connected to the platform. Flex Credits are priced at $500 per 100,000 credits at list.

The credit consumption rate varies by operation type. Data ingestion from Salesforce native sources — Sales Cloud, Service Cloud, Marketing Cloud Engagement, and Commerce Cloud — is now free of charge, which represents a material improvement from the previous model where all ingestion consumed credits. Non-native data source ingestion, profile unification at scale, complex segmentation queries, and agent action executions all carry consumption rates that Salesforce publishes but does not prominently disclose at the point of sale. Enterprises should map their expected usage patterns to published consumption rates before signing any Agentforce 360 or Data 360 contract.

Agentforce Per-Conversation Pricing

Agentforce charges per conversation — the interaction between an AI agent and a user (customer or internal employee) from initiation to resolution. The list price is $2 per conversation. Volume discount tiers reduce this rate for high-volume deployments, and Agentforce Enterprise Edition ($175 per user per month) and Unlimited Edition ($350 per user per month) include conversation allowances that reduce effective per-conversation cost for licensed users.

The per-conversation model creates a structural overage risk that is unlike traditional per-seat licensing. A customer service deployment handling 50,000 AI-assisted interactions per month generates $100,000 in monthly Agentforce conversation fees at list price — $1.2 million per year — entirely separate from base Salesforce licences and Data 360 credits. Organisations deploying Agentforce for customer-facing use cases must model conversation volumes carefully and negotiate tiered pricing caps into their contracts before going live.

The Annual Uplift Problem in a Consumption Model

Every Salesforce Order Form contains an annual price uplift clause of 8 to 10 percent. In a traditional per-seat contract, the uplift applies to a predictable base. In a Flex Credit or per-conversation contract, the uplift applies to the credit pool or conversation allowance purchased, not to actual consumption. This means that even if your consumption stays flat, your credit costs increase by 8 to 10 percent annually through contract escalation, before any volume growth is factored in.

Salesforce's fiscal year ends January 31. The January 31 fiscal year-end and October 31 Q3 quarter-end are the windows of maximum commercial flexibility. Buyers who engage in structured renewal negotiations during these windows — with documented competitive alternatives and a credible willingness to reduce scope — consistently achieve uplift caps of 4 to 5 percent and material reductions in per-credit and per-conversation list pricing.

Five Contractual Protections Every Data 360 Buyer Needs

1. Consumption Rate Locks

Salesforce has the ability to modify credit consumption rates between contract terms. A credit purchased at one consumption rate may deliver fewer operations when rates are updated. Require your contract to lock credit consumption rates — the number of credits consumed per operation type — for the duration of the agreement. This prevents Salesforce from reducing the effective purchasing power of your credit pool without your consent.

2. Credit Rollover Provisions

Unused Flex Credits expire at the end of the contract year in the standard model. For enterprise organisations with variable consumption patterns — seasonal businesses, project-driven data operations — this creates forced credit expenditure or waste. Negotiate credit rollover rights for at least 25 percent of unused credits from each contract year into the following year.

3. Agentforce Conversation Caps

Without a contractual cap, Agentforce conversation charges accumulate without limit. Negotiate a maximum annual spend cap on Agentforce conversations with automatic throttling or notification triggers when the cap approaches. Salesforce will resist hard throttling (preferring to sell overage credits at list), but notification obligations and pricing protection above the cap threshold are achievable negotiating positions.

4. SKU Continuity on Rename

As Salesforce transitions Data Cloud contracts to Data 360, require explicit contractual mapping of all existing SKUs to their Data 360 equivalents at the same commercial terms. Do not accept a voluntary transition process that Salesforce can time to coincide with a renewal conversation. The continuity mapping should be a contract exhibit, not a verbal assurance from an account executive.

5. True-Down Rights

Credit pools and conversation allowances negotiated at contract signature may exceed actual consumption, particularly in the first year of a new Agentforce or Data 360 deployment. Negotiate the right to reduce your contracted credit volume at renewal if consumption falls below 70 percent of the contracted pool. Without true-down rights, unused capacity becomes pure cost with no avenue for reduction.

How Redress Compliance Approaches Data 360 and Agentforce Engagements

Salesforce's transition to consumption-based licensing through Flex Credits and per-conversation Agentforce pricing fundamentally changes the risk profile of a Salesforce enterprise agreement. The cost of a Data Cloud or Agentforce deployment is no longer deterministic at contract signature — it scales with usage patterns that are often impossible to predict accurately in year one.

Our approach begins with consumption modelling: mapping the organisation's planned use cases to published Salesforce credit consumption rates and Agentforce conversation volume projections. We then identify the contract protections — consumption rate locks, credit rollover, conversation caps, true-down rights — that create predictability and limit downside risk. Finally, we engage in structured commercial negotiation using Salesforce's fiscal calendar and competitive alternatives to achieve pricing that reflects the uncertainty inherent in consumption-based licensing.

Across our Salesforce engagements, organisations that commission independent consumption modelling before signing Data Cloud or Data 360 contracts identify 20 to 40 percent higher cost exposure in their initial Salesforce proposals than they would have accepted without analysis. The same modelling exercise also identifies specific contract terms that Salesforce includes as standard but that are negotiable with appropriate leverage.