Platform
Salesforce reversed the Agentforce rebrand: your 2026 product-name map
A year after renaming two dozen products under the Agentforce brand, Salesforce put the old names back on its site the week before Dreamforce, with no announcement. Sales Cloud is Sales Cloud again. Here is the map of what reverted, what kept its new name, and why none of it should change a line of your config.
Sometime around September 14, 2026, Salesforce put the old names back. Sales Cloud, which had spent the previous year as “Agentforce Sales,” was Sales Cloud again on the pricing page.
The Headless 360 Platform was Salesforce Platform again. No press release, no keynote slide, just quiet edits to product pages the week before Dreamforce 2026.
If you spent last autumn updating your wiki, your onboarding deck, and your SOW templates to say “Agentforce Sales,” you are allowed to be annoyed. Before you change everything back, though, one sentence matters more than the map: nothing underneath the label changed either time.
Not the data model, not your Flows, not your Apex, not the API, not your contract. The name moved. The product didn’t. This post is the map, so you can answer the two questions your stakeholders will ask this month, then get back to work.
What Salesforce did, twice
At Dreamforce 2025, Salesforce renamed roughly two dozen products under the Agentforce brand. Sales Cloud became Agentforce Sales. Service Cloud became Agentforce Service. Marketing and Commerce Cloud got the same treatment.
Data Cloud was renamed Data 360 on October 14, 2025, and the whole AI stack was gathered under Agentforce 360. The pitch was coherence: one brand for the agentic era, stamped across the portfolio.
It did not land the way the brand team hoped. The community named it “Renameforce,” half joke and half complaint, and someone built a site whose only job is tracking Salesforce renames. Buyers who had known “Service Cloud” for a decade now had to learn their license was called something else, while the capabilities sat exactly where they’d always been.
A year later came the correction. Reporting on September 14 noted that Salesforce had restored the familiar names on its website, reversing much of the 2025 rebrand days before this year’s Dreamforce.
Salesforce has not published a rationale. The reported reading is simple: customers already understand Sales Cloud and Service Cloud, and bolting “Agentforce” onto each one added terminology without adding clarity. Putting the names back lets Salesforce sell AI as a capability inside applications people already know, rather than asking them to relearn the catalog.
The clean way to read the reversal: Agentforce is the AI you turn on inside Sales Cloud, not a new product that replaced it.
The name map for September 2026
Here is where the core products stand now, against what they were called during the Agentforce-branded year. Track the middle column mainly so you recognise it in a year-old document.
| Product | Agentforce-era name (2025) | Name now (Sept 2026) |
|---|---|---|
| Sales Cloud | Agentforce Sales | Sales Cloud |
| Service Cloud | Agentforce Service | Service Cloud |
| Marketing Cloud | Agentforce Marketing | Marketing Cloud |
| Commerce Cloud | Agentforce Commerce | Commerce Cloud |
| Salesforce Platform | Headless 360 Platform | Salesforce Platform |
| Data Cloud | Data 360 | Data 360 (kept) |
| The AI / agent layer | Agentforce 360 | Agentforce 360 (kept) |
The confirmed reverts in the reporting are Sales Cloud and Salesforce Platform. The other core clouds moved back as part of the same rollback of the application names. Two names did not revert, and that is the tell for what Salesforce treats as new.
Data 360 kept its name. The 2025 rename from Data Cloud was never part of the Agentforce experiment; it repositioned the data layer as the third pillar next to Customer 360 (the apps) and Agentforce 360 (the agents). Every post we’ve written about Data 360 pricing, retrievers, and zero-copy still uses the current name.
Agentforce 360 kept its name too, because Agentforce is the new part: the agent platform, the reasoning engine, the builder, and the runtime. So the AI layer keeps its Agentforce identity while the applications it acts inside got their old, load-bearing names back. Keep the new name on what is new, take it off what isn’t.
What did not change, which is almost everything
This is the part that saves you a project. A marketing rename, in either direction, does not touch what your org runs on.
Your contract, licenses, and pricing carry over. The rename doesn’t reopen your agreement or reset your renewal date, and the price of a capability doesn’t move because the label did.
That is a separate event from the Core, Advanced, and Max edition repricing that landed on September 3, 2026. That one moved real money around, and it’s the one to model. The name reversal, on its own, changes nothing on the invoice.
One caveat worth stating plainly: the reporting confirms the reversal on marketing pages, and how far it propagates into contract paper and support consoles isn’t clear yet. If the name on your renewal quote and the name on the website disagree for a while, that’s expected. Buy the capability, not the label.
Your data and automation are untouched. There is no migration. Opportunities are still Opportunities, Cases are still Cases, and your omni-channel routing, Flows, and Apex behave exactly as they did the day before the name flipped.
The API and metadata names never followed the marketing names in the first place. This is the fact that should let a nervous integration owner sleep. API names, metadata type names, and the developer names of things like permission set licenses are assigned when a feature ships, and Salesforce does not rev them to match a brand refresh.
The cleanest proof sits in every CPQ org: the product’s marketing name has changed more than once, and its metadata still carries the original SBQQ__ namespace prefix. Your integrations bind to API names, your deploys move metadata types, and neither noticed the rebrand or its reversal. If an integration didn’t break when Sales Cloud became Agentforce Sales, it won’t break on the way back.
So the real scope of work for most orgs is small: update the words humans read, and change nothing a machine reads.
What to do this week
The task is mostly hygiene.
- Fix the human-facing copy that names products: onboarding decks, wikis, runbooks, proposal and SOW templates, and any customer-facing page where you wrote “Agentforce Sales.” Search for “Agentforce ” followed by Sales, Service, Marketing, or Commerce and roll those back.
- Leave the technical references alone. Don’t rename permission sets, don’t touch API names in integrations, don’t rewrite deployment scripts. There is nothing to change there, and editing them “to match” only adds risk.
- Write the capability, not the brand, in durable docs. “Service Cloud case management with an Agentforce service agent for tier-1 deflection” survives the next rename. “Agentforce Service” does not.
- Give sales and procurement the one-liner: when a rep says “Agentforce Sales,” it means Sales Cloud with Agentforce turned on. Same product, AI included.
Stop chasing the label
Salesforce has renamed products often enough that a cottage industry of cheat sheets exists to keep up, and community coverage treats the renaming habit as a real friction cost, not a cosmetic one. The defence isn’t memorising the current catalog. It’s building your own references against the layer that doesn’t churn.
Anchor your documentation, your data dictionary, and your integration specs to two stable things: the capability, meaning what the feature does for your business, and the API or metadata name your code and deploys reference. Those are the parts Salesforce leaves alone.
Marketing names are a presentation layer over that, and presentation layers get redesigned. The teams that felt nothing this month are the ones who never wrote a brand name into a place that mattered.
The reversal is good news, mostly, because it puts familiar names back on familiar things and confirms the sane model: Agentforce is the AI you switch on, and the clouds are still the clouds. Update your slides, keep your architecture, and get back to the work the names were always sitting on top of.
Understanding the basics
Is Sales Cloud still called Agentforce Sales?
No. Around September 14, 2026, Salesforce restored the name Sales Cloud on its website, reversing the 2025 rebrand that had renamed it Agentforce Sales. Service, Marketing, and Commerce Cloud moved back to their familiar names in the same rollback. The product is the same one you already licensed; only the marketing label changed, twice.
Do I need to change anything in my org because of the rename reversal?
Only human-facing copy. Update decks, wikis, runbooks, and proposal templates that say “Agentforce Sales” or “Agentforce Service.” Leave permission sets, API names, integrations, and deployment metadata alone, because those never referenced the marketing names, and your contract, pricing, and renewal date carry over unchanged.
What is the difference between Agentforce and Sales Cloud now?
Sales Cloud is the CRM application: accounts, opportunities, forecasting, the objects and automation your reps use. Agentforce is the AI agent layer you enable inside it. The 2025 rebrand merged the two into “Agentforce Sales”; the reversal separates them again, which better reflects how they work. You run Sales Cloud, and Agentforce is a capability you turn on.
Did Data Cloud revert to its old name too?
No. Data Cloud was renamed Data 360 in October 2025, and that name stuck through the reversal. The change repositioned the data platform as one of the “360” pillars rather than part of the Agentforce branding, so Data 360 remains the current name.
Why does Salesforce rename products so often?
Salesforce reorganises its brand to match its strategy of the moment, and in the agentic era that meant briefly stamping “Agentforce” across the catalog before deciding the familiar cloud names carried more trust. The practical defence is to document capabilities and API names rather than marketing labels, because those are the parts that don’t change when the branding does.
Trying to work out what you really own after a year of renames, or which Agentforce capabilities are worth turning on inside the clouds you already run? Talk to us. We map engagements to what the platform does for your business, not to whatever it is called this quarter.
