Every Salesforce Product Name Change in 2026: The Complete Rename Map

You got a renewal email that says "Agentforce Sales." Your license agreement says "Sales Cloud." Your Salesforce rep is using a third name entirely. Your admin is forwarding you articles that contradict each other.

Here's what happened: Salesforce has been systematically folding its entire cloud portfolio under the Agentforce brand — not just Sales Cloud and Service Cloud, but Marketing Cloud, Commerce Cloud, Field Service, Revenue Cloud, and most of its vertical industry products. The rename wave is real, the list is longer than most guides cover, and none of it changes your contract. This post is the definitive map.

Every Salesforce Product Name Change: Quick-Reference Table

The full cheat sheet. Core products first, then industry verticals, then what did not change.

Core Product Renames

Industry Cloud Renames

Products That Were NOT Renamed

New product (not a rename): AgentExchange — a separate marketplace for AI agents — launched alongside Agentforce 2dx. Not a rename of AppExchange.

Contract impact for all renames: None. Existing licenses, pricing, and renewal dates carry over automatically. Details below.

Why Salesforce Is Renaming Everything

The short answer: every product name now needs to signal "AI-first."

When Agentforce launched at Dreamforce 2024, Salesforce positioned it as the platform itself, not a feature bolted on top. If Agentforce is the core, then "Sales Cloud" starts to sound like a legacy silo. Renaming it Agentforce Sales makes the architecture legible: everything is Agentforce, the secondary word tells you which business function it serves.

The pattern mirrors what Microsoft did with Copilot: centralise the AI brand, attach the function, roll it across the portfolio. The customer benefit is a clearer signal about roadmap direction. The cost is exactly the confusion you're experiencing during the transition.

The renames coincide with the Spring '26 release, which shipped Agentforce 2dx — the version that added proactive, event-driven agents. Bundling the renames with a major release gave Salesforce a single announcement moment to reframe the entire product line.

Sales Cloud Renamed to Agentforce Sales

The name changed. The product underneath it did not.

Agentforce Sales is the same CRM you've been running — Opportunities, Accounts, Contacts, Activities, all the same objects and field names. Your Flows still run, your Apex triggers still fire, your reports still work.

What the rename signals is where new investment is going: AI agents that handle pipeline management, call prep, forecast updates, and opportunity scoring as first-class capabilities, not optional add-ons. If you're licensed for Agentforce, you can deploy those agents now. If you're not, the rename alone doesn't add them.

The Agentforce 2dx explainer covers what the AI layer actually does. If you want to build your first agent without code, this no-code setup guide is the starting point.

Service Cloud Renamed to Agentforce Service

Same story as Sales Cloud. The rename to Agentforce Service happened with Spring '26. Case management, omni-channel routing, entitlements, SLA rules — all intact. The direction of new feature investment shifts toward autonomous service agents: ones that resolve routine cases, route complex ones to the right human, and draft responses from your knowledge base without requiring a rep to manually search.

Existing configuration survives unchanged. Pricing survives unchanged.

Marketing Cloud Renamed to Agentforce Marketing

Marketing Cloud's rename has been messier than Sales and Service — you've probably seen references to both "Agentforce Marketing" and plain "Marketing Cloud" in official Salesforce materials. That ambiguity is real, not a mistake on your part.

The official direction is Agentforce Marketing. Salesforce has moved its marketing products under the Agentforce umbrella, with AI-driven journey orchestration and campaign intelligence framed as core rather than add-on. In practice, Salesforce documentation and partner communications are still catching up to the new name. If your contract or your rep still says "Marketing Cloud," that's correct — the product and your agreement haven't changed.

Commerce Cloud, Field Service, and Revenue Cloud

These three made less noise during the rebrand but are confirmed renamed:

• Commerce Cloud is now Agentforce Commerce — the same e-commerce and order management platform, repositioned around AI agents handling catalog recommendations, order tracking responses, and return processing.
• Field Service Lightning is now Agentforce Field Service — the same workforce scheduling and mobile platform, with AI agents increasingly handling dispatch decisions and technician prep.
• Revenue Cloud (the CPQ and billing platform) is now Agentforce Revenue Management — same quoting, contracting, and billing capabilities, with AI agents designed to accelerate deal configuration and catch billing anomalies.

For all three: existing configuration, integrations, and contracts are unaffected.

The Industry Verticals: All Renamed

If you're on a Salesforce vertical product, it has almost certainly been renamed. Health Cloud, Financial Services Cloud, Education Cloud, Automotive Cloud, and the rest of the industry lineup have all moved to the Agentforce naming pattern.

The functional difference — and the honest answer — is that the renames are primarily branding. The vertical products retain their industry-specific data models, regulatory compliance features, and specialty workflows. What changes is the umbrella they sit under and the roadmap emphasis on AI agents tuned for each industry's use cases.

If you're on Financial Services Cloud, you're now on Agentforce for Financial Services. Everything your compliance team knows about the product still applies.

A Note on "Data 360"

You may have seen Salesforce refer to "Data 360" in recent presentations and marketing materials. This is Salesforce's vision name for its unified data strategy — the idea that Data Cloud, CRM data, and third-party data form a complete 360-degree view that powers Agentforce agents.

The official product name is still Data Cloud. No formal rename has been announced as of Spring '26. When Salesforce says "Data 360," treat it as positioning language describing what Data Cloud enables, not a new product name. If your contract says Data Cloud, that's still correct.

The Products That Were NOT Renamed

AppExchange is still AppExchange. Salesforce's main marketplace for apps, components, and consulting partners — unchanged since 2005. Third-party apps, Lightning components, pre-built solutions: still live here.

Experience Cloud is still Experience Cloud. The digital experience and portal platform received Spring '26 updates but was not rebranded under Agentforce.

Slack is still Slack. Deeper Agentforce integration shipped in Spring '26 (agents can now surface in Slack channels and respond to users in threads), but the product name is unchanged.

Tableau is still Tableau. The analytics platform has not been folded into the Agentforce naming.

CRM Analytics is still CRM Analytics.

Salesforce Platform is still Salesforce Platform.

AgentExchange vs. AppExchange: Not the Same Thing

This is the most common confusion point.

AppExchange has been around since 2005. Thousands of apps, components, and consulting listings across every business function. CPQ tools, document generation, custom components — AppExchange.

AgentExchange launched with Agentforce 2dx. It's a separate marketplace specifically for AI agents and agent actions: pre-built agents, agent skills, integrations built to run inside the Agentforce framework. Think of it as the catalog of what your AI agents can do, not what humans install on the platform.

They coexist. AppExchange is where you buy apps. AgentExchange is where you find agent capabilities. If you're building out an Agentforce deployment, browsing AgentExchange early is worth the time — some of the most commonly needed agent skills are already pre-built there.

What This Means for Your Contract and Pricing

Nothing changes.

Salesforce has been consistent: the product renames do not alter existing customer agreements. If your contract says "Sales Cloud Enterprise Edition," you're now effectively on "Agentforce Sales Enterprise Edition" — same seats, same price, same renewal date. Renewal documents going forward will use the new names, so the first time you'll actually see it is when paperwork arrives with "Agentforce Sales" where "Sales Cloud" used to be. That's expected.

What is separately licensed is the Agentforce AI agent functionality itself. The rename doesn't expand what you're licensed for. If your Sales Cloud contract didn't include Agentforce agents, you don't get them automatically. Agentforce capabilities are sold as an add-on or included in certain editions — check your order form or ask your account executive what you're currently entitled to.

Will More Products Be Renamed?

At this point the question is really which products are left. The major ones are done. Experience Cloud and Tableau are the notable holdouts among Salesforce-owned products. Whether those follow in Summer '26 or later hasn't been announced.

The safe assumption: the Agentforce brand will keep expanding. Salesforce's entire investor narrative is built around Agentforce as the AI platform of record. Any product that hasn't been renamed yet is more likely to be renamed eventually than to stay as-is.

For now: if you see a Salesforce product name with "Agentforce" in it that you don't recognise, find the old name in the tables above.

---

Keep reading:

• Agentforce 2dx: What the Spring '26 Upgrade Actually Changes
• AgentExchange: The Best Pre-Built AI Agents for Salesforce in 2026
• Salesforce Spring '26 Admin Guide: What You Need to Know