Salesforce renamed the best-selling product in its own history without waiting for the next contract cycle. At Dreamforce '25, in October 2025, Sales Cloud became Agentforce Sales — a change that took effect with the Spring '26 release in February 2026. Anyone who signed a Sales Cloud contract last year didn't migrate to a new platform. They bought the same product, which now shows up under a different name in the catalog, the documentation, and the admin screen.
The easiest question to answer is the one most people ask first: does anything change in my contract right now? No. The question worth the reading time is different — what does this rename signal about where Salesforce will invest its next product cycle, and does that affect anyone already paying for the old license.
What actually changed — and what stayed the same
The Sales Cloud rebrand didn't arrive in isolation. It was part of a name reorganization announced as a block at Dreamforce '25, under what Salesforce calls Agentforce 360:
- Sales Cloud became Agentforce Sales.
- Service Cloud became Agentforce Service.
- Field Service Lightning became Agentforce Field Service.
- Revenue Cloud became Agentforce Revenue Management.
- Data Cloud became Data 360 — an earlier rebrand from October 2025 that we already covered when the pricing overhaul landed in March.
At the licensing layer, the change is cosmetic: the Sales Cloud license stays valid, the org doesn't change, and data and customizations stay exactly where they were. There's no forced platform migration and no announced deadline for the old name to disappear from documentation.
What changes is what ships bundled with the new name. Lead prospecting and enrichment with general availability targeted for February 2026, a new Sales Workspace with an embedded Tableau dashboard, the Accounts Researched feature shipped in Winter '26, automatic opportunity updates drawn from emails and calls, and an Agent Activity column in the Pipeline Inspection view. Part of that capability comes from an acquisition — Bluebirds — and from partnerships with ZoomInfo and 6sense to cross third-party data with account history.
Renaming the license doesn't migrate anyone. But it decides where the next product feature gets built — and that feature is rarely free.
Why renaming isn't "just marketing"
The reaction from the Salesforce admin and partner community, covered by Salesforce Ben, mixes skepticism with fatigue. Part of the criticism is about timing: Agentforce still faces open questions about performance, pricing, and ROI, and launching a corporate rebrand on top of a product still proving its value sounds premature to people implementing it day to day. Another part is about the brand itself: Sales Cloud is the product that supports the rest of the portfolio, and dropping "Salesforce" for "Agentforce" in the flagship's name reads, to part of the ecosystem, as walking away from two decades of brand recognition without a clear technical need.
The pattern, though, has already played out once. Data Cloud became Data 360 in the same October 2025 wave, and the pricing overhaul that followed four months later wasn't cosmetic: it consolidated segmented credits, created a per-profile SKU, and — more relevant here — pulled native ingestion out of credit consumption while keeping the operation multiplier as the real source of budget risk. The name changed first; the billing model changed later, once Salesforce decided the new product architecture deserved a new price scale.
Sales Cloud → Agentforce Sales follows the same script so far: new name, old license intact. But the agents that ride along with the new name — Lead Qualification, Lead Nurturing, Account Management — require, depending on edition and contract, an additional Agentforce license. That's not a retroactive change to the license you already pay for. It's the same logic as always — just wrapped in a name that now suggests the agent already comes included.
- The rebrand itself doesn't charge anything extra. Existing Sales Cloud customers pay nothing more just because of the new name.
- The specific agents in the package tend to require a separate license. Agent-driven prospecting, lead qualification, and nurturing come as an add-on, not an automatic part of the current contract.
- Data Cloud's recent history shows that a rename and a pricing overhaul can arrive in sequence, not in the same announcement — which means "no cost change today" is no guarantee of "no cost change in 2027."
Three questions for anyone who already has Sales Cloud
Before deciding whether to adopt the new capabilities packaged under the Agentforce Sales name, three questions in the right order:
- Does the new capability solve a real problem in my operation, or is it a slide feature? Accounts Researched and automatic opportunity updates only earn their investment if the team genuinely loses time today researching accounts or typing manual follow-up. If the real bottleneck is elsewhere — data quality, a poorly defined qualification process — the agent doesn't solve it, it just automates the problem faster.
- Which of these capabilities requires an Agentforce license outside my current contract? Ask the partner this before signing any expansion. "Comes with Agentforce Sales" isn't the same as "comes with the license you already pay for."
- Is the partner selling the rename as a mandatory upgrade? There's no forced migration. Anyone presenting the name change as a decision deadline is using the Dreamforce announcement as a sales trigger, not a technical fact.
The name changed; the ROI question didn't
The framework that decides whether Salesforce pays off is still the same one that existed before the rebrand: average customer ticket, process complexity, team operational maturity, and acceptable return horizon. Agentforce Sales doesn't touch any of those four variables — it only adds one new, agent-specific decision line on top of an axis that already existed.
That holds even for anyone re-evaluating whether Salesforce still fits the current budget. A new name in the catalog doesn't move the calculation between a low ticket and platform cost — it only adds one more optional capability to the list of things to consider. A company that already had a reason to question the investment still has the same reason, just relabeled.
Anyone who treats the rebrand as a signal about future investment — without confusing it with an obligation to buy right now — walks away with free information. Anyone who signs the next add-on just because the product name now includes "Agentforce" is paying for marketing, not for capability validated in their own operation.
Questions that keep coming back
To close, the three most common questions about the Sales Cloud rebrand.
Does Sales Cloud still exist, or was it discontinued?
It still exists, just under a different name. Sales Cloud was renamed to Agentforce Sales at Dreamforce '25 (October 2025), effective with the Spring '26 release (February 2026). It's not a discontinuation or a platform migration — it's the same product, license, and org, showing up with new terminology in the documentation and the interface.
Do I need to migrate to Agentforce Sales?
No. The rebrand doesn't force a technical migration: your Sales Cloud org, data, customizations, and license stay exactly as they were. What does require a decision is adopting the new agent capabilities — Lead Qualification, Lead Nurturing, Account Management — which, depending on edition and contract, need an additional Agentforce license. Adopting those capabilities is optional, not an automatic consequence of the new name.
What really changed — just the name, or the price too?
So far, just the name — the Sales Cloud license hasn't been repriced because of the rebrand. But Data Cloud's precedent, renamed to Data 360 in the same October 2025 wave, shows that a name reform and a pricing reform can arrive in sequence, not together: Data Cloud's credit overhaul only landed four months after the rename. Anyone already paying for Sales Cloud has no reason to act now, but also no guarantee that "no cost change" still holds in 2027.