Salesforce Data 360 (formerly Data Cloud) is worth it when customer data is spread across several systems and you have a clear use that needs it joined up. If most of your customer data already lives in Salesforce, or your CRM records are still messy, fix the basics first. Data 360 adds a usage-based bill on top of your CRM licenses, so know what you will do with it before you turn it on.
This guide explains what Data 360 does in plain terms, how the pricing works, the signs you are ready, and the questions we ask before a client commits.
What is Salesforce Data 360?
Data 360 is Salesforce's data platform. It pulls in data from Salesforce clouds and from outside sources such as a website, an ecommerce store, a billing system or a data warehouse. It maps that data to a common data model, then matches records that belong to the same person or company into a unified profile.
Salesforce renamed the product from Data Cloud to Data 360, and its pricing pages now use the new name. Many partners, admins and older documents still say Data Cloud. They mean the same product.
Once profiles are unified, you can build segments, send them to marketing or ad platforms, show the joined data inside Salesforce, and give AI features such as Agentforce more context to work with.
How does Data 360 decide two records are the same customer?
This step is called identity resolution. As Salesforce's Trailhead module on mapping and unifying data explains, you set two kinds of rules:
- Match rules decide which records belong together. Each rule compares a field such as email or phone using exact, fuzzy or normalized matching.
- Reconciliation rules decide which value to show when matched records disagree, for example the most recent value, the most frequent value, or the value from the source you trust most.
These rules only work as well as the data you feed them. If one customer has three spellings of a company name and no shared email, no rule will join those records reliably. That is why we treat data cleanup as step one, not an afterthought.
How is Data 360 priced?
Data 360 is priced on usage. On its Data 360 pricing page, Salesforce lists three models (list prices as of October 2026):
- Flex Credits: $500 per 100,000 credits, used up as you perform actions.
- Profiles: $240 per 1,000 profiles per year, with set allowances for items such as segments and transforms.
- Enterprise Profiles: $420 per 1,000 profiles per year, with larger allowances.
Batch data ingestion is listed as free. Processing unstructured data, querying, sharing and streaming are tied to usage under every model. Salesforce offers a pricing calculator for estimates and a Digital Wallet view to monitor consumption.
The practical point is that your bill depends on what you do with the data, how often, and how much of it. A team that refreshes segments in near real time will spend very differently from one that updates a weekly report. Ask for an estimate built on your real use cases, and name someone to review usage every month.
What are the signs you are ready for Data 360?
The strongest cases usually share a few traits:
- Customer data sits in several systems that matter, not just Salesforce. Think ecommerce orders, product usage, support tickets or billing.
- You have a named use case with an owner, such as sending churn-risk accounts to the success team each morning, or removing current customers from paid ad audiences.
- Your Salesforce org is already in decent shape: clear account and contact ownership, few duplicates, and agreed field definitions.
- You plan to use AI features in Salesforce and want them working from more than the CRM record.
- Someone can own the rules and the monthly usage review after launch.
When should you wait or choose something simpler?
Data 360 is not the answer to every data problem. Consider waiting if:
- Most of your customer data is already in Salesforce. Reports, flows and good field design may be enough.
- Your main pain is duplicate or stale CRM records. Fix those with cleanup, validation rules and duplicate rules first. Our guide to reconciling records during a CRM migration covers the checks we use.
- You only need to move data between two systems. A direct integration is cheaper and easier to support. See our API and system integration services.
- You cannot yet say who will use the unified profile and for what.
Sometimes the real fix is a workflow, not a data platform. A solar solutions provider we work with builds task reminders into its Arches workflow automation for every bid, so no bid sits without a next step. That solved a follow-up problem without adding a new data layer.
What should you ask before you sign?
- Which two or three use cases will we launch first, and who owns each one?
- Which sources will we connect, and how often must each one refresh?
- What match and reconciliation rules will we start with, and how will we test them on a sample?
- What is the estimated monthly credit use for those use cases, and what alert fires if it runs high?
- Who reviews data quality, rule changes and usage after go-live?
- How will we measure whether unified profiles changed a business result?
How do you roll out Data 360 without surprises?
Start small. Pick one use case, connect only the sources it needs, and test identity resolution on a sample where you already know the right answer. Count how many records merged correctly, how many should have merged and did not, and how many merged by mistake. Then watch credit use for a full month before you add the next use case.
If you are still deciding which customers matter most, start with an ideal customer profile your CRM can use. It tells you which data is worth unifying first.
Frequently asked questions
Yes. Salesforce renamed Data Cloud to Data 360. The product and its core features carry over, and many documents still use the older name.
Most do not at first. If your customer data lives mainly in one CRM, cleaning that data and improving reports and workflows usually pays off faster. Data 360 makes more sense once several systems hold customer data you need to act on together.
It is usage-based. As of October 2026, Salesforce lists Flex Credits at $500 per 100,000 credits and profile-based plans at $240 or $420 per 1,000 profiles per year. Your real cost depends on how often you process, query and stream data, so get an estimate based on your own use cases.
It can match records into unified profiles, but it does not replace CRM data hygiene. Duplicate rules, required fields and clear ownership in Salesforce still matter, and clean source data makes identity resolution more accurate.
Sources
Not sure if Data 360 fits your CRM?
We review your Salesforce setup, data sources and goals, then tell you whether Data 360, an integration or a CRM cleanup will pay off first.

