If you work with Salesforce, you may have noticed that keeping up with the technology is sometimes easier than keeping up with what everything is called.
Data Cloud became Data 360.
Sales Cloud became Agentforce Sales… and now Sales Cloud is making a comeback.
Revenue Cloud became Agentforce Revenue Management.
Marketing Cloud Next became Agentforce Marketing.
Headless 360 arrived and Salesforce Platform promptly re-entered the conversation.
And now, following Dreamforce 2026, we have another name to learn: AIforce.
Confused?
You’re definitely not the only one.
So rather than simply listing the latest Salesforce terminology, we’ve pulled together a guide to what has actually changed, what’s genuinely new, and which familiar names you can safely continue using.
What you’ll find in this blog
- The biggest Salesforce product name changes
- Which changes are simply rebrands and which represent new technology
- What’s changed again following Dreamforce 2026
- What the new terminology actually means for Salesforce customers
First, why does Salesforce keep changing the names?
There is actually some logic behind much of it.
Salesforce has spent the last couple of years moving away from positioning its products as separate “clouds” and towards a much more connected platform built around data, AI agents and shared services.
That shift accelerated with Agentforce.
During 2025 and 2026, the Agentforce name began appearing across Salesforce’s portfolio as the company increasingly positioned AI agents as part of the core platform rather than an optional extra.
But ahead of Dreamforce 2026, something interesting happened.
Some of those familiar product names started coming back.
So let’s translate.
Sales Cloud → Agentforce Sales → Sales Cloud
This might be the best example of why Salesforce customers can be forgiven for losing track.
Sales Cloud became Agentforce Sales, reflecting Salesforce’s push to embed AI agents directly into the sales process.
Then, shortly before Dreamforce 2026, Salesforce started using Sales Cloud prominently again.
The underlying direction hasn’t reversed. Agentforce capabilities remain part of Salesforce’s sales proposition. What’s changed is the label being put on the box.
So if somebody says Sales Cloud, you haven’t missed another new product.
They’re talking about the sales platform you already know.
Service Cloud → Agentforce Service
Service Cloud has also been increasingly presented as Agentforce Service.
Again, this reflects more than Salesforce simply deciding it fancied a new name.
Agentforce is being built into service workflows so AI agents can work alongside human service teams, resolve routine requests and support employees across channels.
You’ll still see both Service Cloud and Agentforce Service terminology across Salesforce materials, so don’t be surprised if the names are used interchangeably for a while.
Data Cloud → Data 360
This one is much simpler.
Data Cloud is now Data 360.
Same product. New name.
Data 360 remains Salesforce’s real-time data platform, bringing information from different sources together and making that trusted data available across Salesforce.
The new name reflects its increasingly important role beyond traditional customer data use cases, particularly as the data foundation underneath AI and Agentforce.
If someone says Data Cloud, they’re talking about what Salesforce now officially calls Data 360.
Revenue Cloud → Agentforce Revenue Management
This one needs a little more explanation.
Salesforce now refers to Revenue Cloud as Agentforce Revenue Management.
But this shouldn’t be interpreted as Salesforce simply changing the logo at the top of the screen.
Agentforce Revenue Management represents Salesforce’s broader approach to managing the revenue lifecycle, bringing areas including product configuration, pricing, quoting, contracts, orders and billing closer together.
It’s particularly important for businesses still using Salesforce CPQ.
And what about Salesforce CPQ?
Salesforce CPQ hasn’t simply been renamed Agentforce Revenue Management.
They’re not the same thing.
CPQ is the established configure, price and quote product many Salesforce customers still use today.
Agentforce Revenue Management represents Salesforce’s newer revenue architecture and broader direction of travel.
For organisations using CPQ, the important question therefore isn’t:
“What’s CPQ called now?”
It’s:
“What does Salesforce’s revenue roadmap mean for our existing CPQ implementation?”
That’s a much more useful conversation.
Pardot → Marketing Cloud Account Engagement
This is one of the older name changes, but it’s still probably the one we hear ignored most often.
Pardot officially became Marketing Cloud Account Engagement, usually shortened to MCAE.
The product didn’t disappear overnight and plenty of people in the Salesforce ecosystem still call it Pardot.
So if somebody says Pardot in a meeting, nobody needs to correct them.
We all know what they mean.
Marketing Cloud → Marketing Cloud Engagement
The established Salesforce marketing platform became Marketing Cloud Engagement, or MCE.
This distinction became increasingly important when Salesforce started building its next-generation marketing platform.
Which brings us to…
Marketing Cloud Next → Agentforce Marketing
Salesforce introduced Marketing Cloud Next as its next-generation marketing platform, built natively on the Salesforce Platform and closely connected with Data 360 and Agentforce.
That platform is now being positioned as Agentforce Marketing.
This isn’t simply Marketing Cloud Engagement with another new name.
It’s part of Salesforce’s newer marketing architecture, designed around unified data, automation and AI agents capable of doing more of the campaign work themselves.
At Dreamforce 2026, Salesforce expanded that vision further with Campaign Agent, which can help create content, assemble audiences and campaigns, select channels and optimise activity against a marketer-defined goal.
So this is one of the name changes where the technology underneath really does matter.
Einstein → Agentforce… sort of
This is another area where it’s tempting to create a neat before-and-after arrow.
Unfortunately, reality isn’t quite that tidy.
Salesforce used the Einstein brand for AI capabilities for years, with names including Einstein AI, Einstein GPT and Einstein Copilot.
Agentforce has increasingly become the umbrella for Salesforce’s agentic AI capabilities.
But Einstein hasn’t simply been renamed Agentforce everywhere.
You’ll still encounter Einstein terminology within Salesforce products and features.
It’s better to think of this as an evolution of Salesforce’s AI strategy rather than a straightforward product rename.
Headless 360 → Salesforce Platform
Here’s one of the newest additions to the list.
Earlier in 2026, Salesforce introduced Headless 360, an architecture designed to expose Salesforce data, workflows, business logic and actions through APIs, MCP tools and other developer interfaces.
Ahead of Dreamforce, Salesforce began putting the Salesforce Platform name front and centre again.
The technology and “headless” strategy haven’t disappeared.
In fact, they’re central to one of the biggest announcements from Dreamforce 2026.
And now meet AIforce
If you only learn one genuinely new Salesforce term from Dreamforce 2026, make it this one.
AIforce is Salesforce’s new live interface layer.
The idea is that people and AI agents shouldn’t necessarily have to open Salesforce to use everything stored and configured inside it.
Instead, Salesforce can bring its data, workflows, permissions, business logic and actions into the interface where someone is already working.
That could be Slack.
It could be Claude.
It could be another AI interface.
Or it could still be Salesforce itself.
Underneath AIforce sits the technology Salesforce has been developing through its headless architecture.
So Headless 360 hasn’t exactly vanished. Its underlying approach has become part of a much bigger story.
Salesforce is increasingly separating where the work happens from where the business logic and data live.
That’s a significant shift.
Claudeforce is another name you’ll start hearing
Yes. There’s another one.
Claudeforce comes from Salesforce’s expanded partnership with Anthropic.
It brings Salesforce context and actions into Claude so users can work with Salesforce data, workflows and business logic directly through Anthropic’s AI interface.
Unlike Data Cloud → Data 360, this isn’t a product rename.
It’s an integration and partnership proposition.
Still, expect to hear the name a lot.
And apparently we’re calling it Slackforce now too
Dreamforce 2026 also introduced the Slackforce language.
Again, this doesn’t mean Slack has disappeared and been replaced by a completely different product.
It’s part of Salesforce’s broader vision of Slack becoming an interface where people and AI agents work together, rather than simply somewhere teams send messages to each other.
The important thing here isn’t really the name.
It’s the direction.
So what should Salesforce customers actually call everything?
The simplest rule is: don’t worry too much about using yesterday’s name.
If you say Pardot instead of MCAE, people will understand you.
If you say Data Cloud instead of Data 360, you’re not talking about an obsolete platform.
And if you’ve only just trained everybody to say Agentforce Sales and Salesforce starts calling it Sales Cloud again, you’re allowed a small sigh.
What’s much more important is understanding whether a name change represents:
A rename
The product is essentially the same, but Salesforce has changed its name.
An evolution
The familiar product is developing into a broader or differently architected offering.
A genuinely new capability
There’s new technology underneath the new terminology.
Those distinctions matter far more than memorising Salesforce’s latest vocabulary.
The bigger Dreamforce 2026 story isn’t actually the names
Look past all the branding changes and Salesforce’s direction becomes much clearer.
Data 360 provides the trusted data.
The Salesforce Platform provides the workflows, permissions and business logic.
Agentforce provides AI agents capable of reasoning and taking action.
AIforce increasingly allows all of that to appear wherever people actually work.
And integrations with platforms such as Claude, Slack, Google and AWS mean Salesforce is becoming less dependent on users spending their day inside a traditional Salesforce interface.
That’s the bit businesses should be paying attention to.
Because the question isn’t really whether your team can remember what Salesforce has renamed something.
It’s whether your existing Salesforce environment, data and processes are ready to take advantage of what those new capabilities can actually do.
And that starts with getting the foundations right.
If you’re trying to understand what Salesforce’s latest changes mean for your existing setup, roadmap or investment, talk to the Xenogenix team. We’ll help you separate the genuinely useful developments from the new terminology and work out what actually matters for your organisation.
Samantha Mathie is a Senior Digital Marketing Executive at Xenogenix and has been part of the business for four years. Before joining Xenogenix, she spent more than eight years working independently as a marketing consultant.
With a background in IT, telecommunications and video conferencing, Samantha specialises in B2B technology marketing, digital campaigns, content and connected customer journeys. She is particularly skilled at turning complex subjects into clear, engaging communications.
As an author for Xenogenix, Samantha shares practical guidance on digital marketing, campaign planning, content and communicating technology effectively.