Salesforce Clouds Compared: Which Ones Do You Actually Need?

Key Takeaways:

• Salesforce cloud counts vary because “cloud” is not a clearly defined category, with guides counting core products, industry clouds, or acquired products differently.
• The six core clouds are Sales, Service, Marketing, Commerce, Experience, and Analytics.
• In 2026, Sales, Service, Marketing, and Commerce Cloud adopted Agentforce naming, while Experience Cloud and Analytics Cloud remained unchanged.
• Data 360, Agentforce, and the Salesforce Platform are foundation layers rather than additional Salesforce clouds.
• Industry clouds provide pre-built data models for sectors such as healthcare, financial services, manufacturing, education, and nonprofit.
• Businesses often create unnecessary overlap by purchasing multiple products that perform similar functions, particularly Marketing Cloud vs. Account Engagement and Analytics Cloud vs. Tableau.
• Most businesses should start with one or two clouds, rather than attempting a multi-cloud rollout from the beginning.
• Salesforce licences are purchased separately by cloud and user, making role-based licensing important for controlling costs.
• Data 360 and Agentforce are generally better added after an organization has clean data and well-established processes.
• The right Salesforce cloud mix depends on business processes, customer journeys, existing systems, and actual operational needs, not simply the size of Salesforce’s product catalogue.

Quick Answer: Most businesses do not need all Salesforce clouds. Sales Cloud is typically the starting point for sales-led organizations, while Service Cloud fits businesses focused on customer support. Marketing, Commerce, Experience, Analytics, industry clouds, Data 360, and Agentforce should be added based on specific business needs. Starting with one or two clouds and expanding after adoption is usually more practical than implementing the entire Salesforce ecosystem at once.

Ask how many Salesforce clouds there are, and you’ll get confident, contradictory answers. Six. Fifteen. More than twenty.

All three are right, and the reason nobody explains it is the most useful thing on this page: “cloud” isn’t a defined term. Some guides count only the core products. Some add industry clouds. Some include acquired products like Tableau and Slack that Salesforce sells but runs separately.

There’s a second reason the guides disagree, and it’s newer: Salesforce renamed some of the clouds in 2026 and not others. Sales, Service, Marketing, and Commerce Cloud now carry the Agentforce name. Experience Cloud and Analytics Cloud don’t. So depending on when an article was written, the same product has two names.

This guide sorts the portfolio properly, then answers the question you’re actually asking – which ones do you need.

The Portfolio, Grouped Properly

Count only the core clouds, and you get six. Add the industry clouds, and you’re near fifteen. Count acquisitions, and you pass twenty. That’s the whole explanation for the discrepancy, and once you see the grouping, the catalogue stops being confusing.

The foundation column matters more than it looks. Data 360, Agentforce and the Platform aren’t clouds – they sit beneath all of them. A guide that lists Data Cloud as “the seventh cloud” has miscategorised it, which then makes the rest of the advice harder to follow.

The Six Core Clouds

Sales Cloud and Service Cloud remain the most deployed by a wide margin. Most Salesforce projects still start with one or both, and that hasn’t changed despite everything else that has.

The fastest-growing area isn’t a cloud at all; it’s Data 360, because unified data is what makes the AI layer worth having.

Deeper: Sales Cloud guide · Service Cloud guide · Marketing Cloud guide

The Foundation: Not Clouds, but Underneath Them

Data 360 (formerly Data Cloud) unifies customer records from every system you run – Salesforce and otherwise – into one profile. It’s what makes “one customer view” real rather than aspirational, and it’s what agents are grounded in. See Data 360 explained.

Agentforce is the AI agent layer spanning every cloud. Not a separate product you use in isolation – it acts inside Sales, Service, Marketing, and the rest. See what Agentforce is.

The Salesforce Platform is what all of it is built on, and what you build your own applications on. It also has its own licence type at roughly a sixth the cost of a full CRM seat, which matters if you have users who never touch a Lead or Case. See the Salesforce Platform explained.

Industry Clouds

These are pre-built data models for specific sectors – not add-ons or templates, but genuine object models Salesforce builds and maintains.

The argument for buying rather than building is simple arithmetic. Rebuilding an industry data model costs six figures, and you maintain it forever; the industry cloud costs more per seat and Salesforce maintains it. For anything genuinely clinical, financial or regulated, the industry cloud wins on total cost by year three.

Deeper: Salesforce for healthcare · Salesforce for financial services · Salesforce for manufacturing

Where Clouds Overlap, and You Pay Twice

The Two Worth Understanding Before You Buy Anything:

• Agentforce Marketing Cloud versus Account Engagement: Account Engagement is what used to be Pardot, and it’s a genuinely separate product from Marketing Cloud despite both doing marketing automation. The rough split is B2C scale versus B2B nurture. Plenty of organisations end up owning both because different teams bought them at different times, and one usually goes unused.
• Analytics Cloud versus Tableau: Both do reporting. Analytics Cloud lives inside the CRM and is good at CRM data. Tableau is stronger across systems and better for analysts. The overlap is real, and organisations frequently pay for both while using one.
• Before adding any cloud, ask what you already own that does 70% of the job: Usually, something does, and 70% with no additional licence often beats 100% with one.

Related: How to reduce Salesforce licence costs

What to Start With

• Almost Nobody Should Start With More Than Two: The most common implementation failure isn’t picking the wrong cloud – it’s buying four and rolling out none of them properly.
• The Sequencing That Works: Get one cloud genuinely adopted, with clean data and people actually using it, then add the second. A working Sales Cloud beats a half-implemented Sales, Service and Marketing suite in every measurable way.

Data 360 and Agentforce come later, not first. They’re what you add once you have data worth unifying and processes worth automating. Buying the AI layer before the data is clean is how organisations end up with agents that give confident wrong answers.

Common Combinations

The one to think hardest about is Sales plus Marketing. The question that prevents most problems is deciding early which system owns the lead record and which one owns consent. “Both” is how data diverges.

Licensing: What Multi-Cloud Actually Costs

Each cloud is licensed separately, per user. That’s the fact most buyers underestimate. Two clouds for fifty users is not one licence; it’s two, and the cost roughly doubles for anyone who needs both.

Three things that reduce the bill:

• Not Everyone Needs Every Cloud: A support agent doesn’t need Sales Cloud. Licence by role, not by headcount.
• Platform Licences: Cost roughly a sixth of a full CRM seat for users who need custom apps but never touch Leads, Opportunities, or Cases. In most organisations, that’s more people than expected.
• Editions Matter As Much As Clouds: Enterprise versus Unlimited is a bigger cost difference than adding a second cloud for a small team.

Deeper: Salesforce pricing in full · Editions compared · Reducing licence costs

The Naming Problem

Worth a short section, because it causes real confusion when comparing guides.

Salesforce has renamed the same products repeatedly. Pardot became Marketing Cloud Account Engagement became Account Engagement. Force.com became the Lightning Platform became the Salesforce Platform. Data Cloud became Data 360. Four of the six core clouds picked up the Agentforce name in 2026; two didn’t.

What this means practically:

• An article using only old names was written before 2026
• An article using only new names may be missing that Experience and Analytics Cloud kept theirs
• A partner listing “Sales Cloud Consultant” hasn’t updated their credentials – the certification was renamed in July 2026

Some stale content is worse than that; one widely-shared guide with a 2026 update stamp still lists “Vaccine Cloud” among the current products, a COVID-era offering. If a guide’s product list includes something that no longer exists, treat the rest of its advice accordingly.

Related: Salesforce certifications and the 2026 renames

Where to Go Next

For the individual clouds in depth – Sales Cloud · Service Cloud · Marketing Cloud · Experience Cloud

For the foundation layer – Data 360 · what is Agentforce · the Salesforce Platform

For industry clouds – Salesforce for healthcare · Salesforce for financial services · manufacturing · nonprofit

For cost – Salesforce pricing · editions compared · reducing licence costs · Salesforce ROI

For deciding whether Salesforce fits at all – Salesforce alternatives · vs HubSpot · for startups and SMBs

For implementing – choosing an implementation partner · every Salesforce product

The complete guide to Salesforce is the hub.

Buying More Clouds Than You Need Is the Default Outcome

Salesforce sells by cloud, so the conversation naturally trends toward more of them. Nobody in that meeting is incentivised to say “you don’t need Marketing Cloud yet.”

We are, because an implementation that covers two clouds properly succeeds, and one that covers four badly becomes a rescue project.