Salesforce Data 360 Pricing: What Does It Cost?
Salesforce Data 360 pricing is different from traditional Salesforce products that are primarily priced per user.
Data 360 currently offers credit-based and profile-based pricing models, allowing organizations to choose between consumption-based flexibility and more predictable profile-based pricing. Salesforce lists:
- Flex Credits: $500 per 100,000 Flex Credits
- Profiles: $240 per 1,000 profiles per year
- Enterprise Profiles: $420 per 1,000 profiles per year
Salesforce states that pricing is subject to change and that final pricing depends on the organization's requirements and contract.
But the license or SKU is only one part of the total investment.
A realistic Data 360 budget can include:
- Data 360 licensing
- Flex Credits or profile pricing
- Implementation
- Data modeling
- Data preparation
- Identity resolution
- Integrations
- Data migration
- Security and governance
- Marketing activation
- Agentforce use cases
- Testing
- Training
- Managed services
- Ongoing consumption
That makes it important to evaluate Total Cost of Ownership, rather than looking at one Salesforce price point.
Quick Salesforce Data 360 Pricing Overview
| Pricing Component | Current Salesforce List Price |
|---|---|
| Flex Credits | $500 per 100K Flex Credits |
| Profiles | $240 per 1K profiles/year |
| Enterprise Profiles | $420 per 1K profiles/year |
| Data Ingestion | Free |
| Data 360 Starter | $60,000/year |
| Data 360 Provisioning | $0 SKU with different included entitlements |
| Additional Flex Credits | $500 per 100K |
| Implementation | Depends on project scope |
| Integrations | Depends on complexity |
| Managed Services | Depends on support scope |
Salesforce describes these prices as list pricing and notes that pricing and availability can change.
What Is Salesforce Data 360?
Salesforce Data 360 is Salesforce's data platform for bringing enterprise data together, creating unified customer context and making that data available for analytics, automation, personalization and AI.
Salesforce describes Data 360 as a platform that can transform fragmented enterprise data into a unified view that supports workflows, decisions and AI agents.
The product was previously known as Salesforce Data Cloud.
Salesforce officially rebranded Data Cloud to Data 360 on October 14, 2025. Salesforce says the name changed while the underlying functionality and content remained unchanged.
This means you may still find older search results, documentation and implementation material referring to:
Salesforce Data Cloud
and newer material referring to:
Salesforce Data 360
For pricing and implementation decisions, use the current Data 360 documentation and commercial materials.
How Salesforce Data 360 Pricing Works
Salesforce's current model is based around the actions an organization performs with its data.
The basic concept is:
Bring data in → Prepare and harmonize → Unify → Build segments → Activate → Query and share → Use streaming and real-time capabilities
Some of these actions consume credits or are included within profile-based plans.
Salesforce currently states that batch data ingestion and zero-copy integrations are free, while organizations pay for actions such as data preparation, unification, segmentation, activation, querying, sharing and real-time processing.
This is an important distinction.
You should not estimate Data 360 cost simply by asking:
"How much data do we have?"
Instead, ask:
"What will we do with that data?"
Salesforce Data 360 Flex Credits
Flex Credits provide consumption-based pricing.
Salesforce currently lists:
$500 per 100,000 Flex Credits
The credits can be used across eligible Data 360 actions, allowing organizations to align spending with actual consumption. Salesforce also states that Flex Credits can be purchased through pre-purchase, pay-as-you-go and pre-commit options.
This model can be useful for organizations where Data 360 usage varies significantly.
For example, a company might have:
- Moderate ingestion
- High segmentation activity
- Heavy real-time processing
- Limited query usage
A consumption model allows the organization to pay according to those activities rather than using a single flat pricing structure.
What Uses Data 360 Credits?
Salesforce's current pricing model identifies several billable or consumption-based activities.
These include:
Data Preparation
Cleaning and preparing data before it is used.
Harmonization
Aligning information from different sources.
Unification
Matching and merging customer records.
Segmentation
Creating customer audiences.
Activation
Sending data, audiences or insights to downstream destinations.
Queries
Retrieving customer information and insights.
Data Sharing
Sharing data with external environments.
Streaming
Processing continuous data flows.
Real-Time Processing
Processing data for live customer experiences.
Unstructured Data Processing
Extracting intelligence from documents, text, audio and other unstructured sources.
Salesforce's pricing page currently separates free ingestion from these downstream actions.
Salesforce Data 360 Profile Pricing
Salesforce also offers profile-based pricing.
The current listed price is:
$240 per 1,000 profiles per year
Salesforce describes this model as a more predictable pricing option where essential profile-building Data 360 actions are included.
This model can be attractive for organizations primarily focused on Customer 360 and unified profile use cases.
Salesforce Data 360 Enterprise Profiles
The Enterprise Profiles option is currently listed at:
$420 per 1,000 profiles per year
Salesforce describes Enterprise Profiles as including everything in Profiles plus additional included Flex Credits and capabilities such as Data Masking and Ad Audience add-ons.
The current comparison lists:
| Feature | Profiles | Enterprise Profiles |
|---|---|---|
| Price | $240 / 1K profiles/year | $420 / 1K profiles/year |
| Ingestion | Free | Free |
| Included preparation/unification | 25 CIs, 25 transforms | 100 CIs, 100 transforms |
| Included segments | 100 | 500 |
| Flex Credits per profile | 1 | 2 |
| Data Masking | Not included in base | Available as add-on |
| Ad Audience | Not included in base | Available as add-on |
Salesforce's pricing page should be treated as the source of truth because these entitlements can change.
What Is a Data 360 Profile?
For pricing purposes, a profile represents the unified customer or entity record that Data 360 is building and managing.
A company may have customer information across:
- CRM
- ERP
- Marketing
- Website
- Commerce
- Customer service
- Mobile applications
Data 360 can bring those records together to create a more unified customer representation.
For example:
CRM
Customer A → ERP
Customer 7821 → Website
Visitor 98321 → Marketing
Contact 12993 → Unified Profile
Customer A
The number and nature of profiles therefore become an important part of a profile-based pricing calculation.
Salesforce Data 360 Starter Pricing
Salesforce's current pricing calculator documentation lists a Data 360 Starter SKU at $60,000 per year.
Salesforce states that the Starter SKU includes:
- 10 million Flex Credits
- 5 TB Data Storage
- 1 Customer Data 360 instance
- 1 Admin Data 360 user
- 100 Internal Identity Customer Data 360 users
- 200,000 Permission Set Licenses
- Data 360 One
- 10 free Companion Org Connections
Salesforce notes that the Starter SKU is intended for customers with Data 360 use cases.
This is important when comparing Data 360 pricing because a large enterprise implementation may not be best represented by the simple $500 per 100,000 Flex Credits figure alone.
What Is the Data 360 Provisioning SKU?
Salesforce also documents a Data 360 Provisioning SKU, sometimes referred to as the Data 360 Everywhere SKU.
Salesforce currently lists this as a $0 SKU.
However, it has different included entitlements from the paid Starter SKU.
The current documentation lists:
- 250,000 Flex Credits
- 1 TB Data Storage
- 1 Customer Data 360 instance
- 1 Admin Data 360 user
- 100 Internal Identity Customer Data 360 users
- 200,000 Permission Set Licenses
- Data 360 One
- 10 free Companion Org Connections
Salesforce describes this provisioning SKU as being intended for customers who do not have standalone Data 360 use cases but use other Salesforce products that rely on Data 360 functionality.
Salesforce Data 360 Pricing Calculator
Salesforce provides a Data 360 pricing calculator to estimate expected consumption.
The calculator is useful because actual consumption depends on factors such as:
- Data volume
- Features being used
- Processing frequency
- Number of profiles
- Segmentation
- Activation
- Queries
- Streaming
- Real-time workloads
Salesforce explicitly recommends its pricing calculator for estimating the number of credits and overall pricing based on specific use cases.
How Much Does Salesforce Data 360 Cost?
There is no single implementation cost that applies to every organization.
A practical budget should separate four major categories:
1. Salesforce Data 360 Licensing
This includes the applicable:
- Starter SKU
- Flex Credits
- Profiles
- Enterprise Profiles
- Storage
- Add-ons
2. Implementation
This can include:
- Discovery
- Architecture
- Data modeling
- Data ingestion
- Identity resolution
- Integrations
- Security
- Testing
- Deployment
3. Business Enablement
This can include:
- Training
- Documentation
- Change management
- Governance
- Adoption
4. Ongoing Operations
This can include:
- Support
- Optimization
- Data quality
- New integrations
- Release management
- Consumption monitoring
Salesforce Data 360 Implementation Cost Factors
The biggest implementation cost driver is usually not the Data 360 license itself.
It is the complexity of the environment.
Number of Data Sources
Connecting three clean systems is significantly different from connecting twenty fragmented systems.
Data Quality
Poor data can increase:
- Mapping effort
- Transformation work
- Identity resolution complexity
- Testing
- Remediation
Data Model Complexity
A simple customer profile is easier to implement than a model involving:
- Accounts
- Contacts
- Households
- Products
- Contracts
- Transactions
- Service relationships
- Digital behavior
Identity Resolution
Complex matching requirements can increase architecture and configuration effort.
Integration Complexity
Integrating Salesforce with one SaaS application is different from integrating:
- SAP
- NetSuite
- Dynamics 365
- Snowflake
- Databricks
- Custom applications
- Legacy databases
Real-Time Requirements
Real-time architecture can require more sophisticated:
- APIs
- Event pipelines
- Streaming
- Monitoring
- Error handling
Activation
A project that only creates unified profiles may be simpler than one that activates those profiles across:
- Marketing Cloud
- Advertising
- Sales
- Service
- Commerce
- Agentforce
Salesforce Data 360 Pricing Example
Consider an organization with:
- 500,000 customer profiles
- CRM data
- ERP data
- Marketing data
- Website activity
- Several segments
- Marketing activation
- Some real-time use cases
Under the current listed Profile pricing:
500 × $240
would equal:
$120,000 per year
before considering additional usage-based requirements or other applicable commercial terms.
Under Enterprise Profiles:
500 × $420
would equal:
$210,000 per year
before applicable additional consumption and add-ons.
These are simple list-price calculations based on Salesforce's currently published rates, not a quote or prediction of a customer's actual contract. Salesforce notes that final pricing depends on the customer's requirements and agreement.
Flex Credit vs Profile Pricing
The right pricing model depends on the use case.
| Factor | Flex Credits | Profiles | Enterprise Profiles |
|---|---|---|---|
| Pricing style | Consumption | Profile-based | Profile-based |
| Predictability | Medium | High | High |
| Best for | Variable workloads | Customer 360 | Larger enterprise profile use cases |
| Scaling model | Usage | Profiles | Profiles |
| Included actions | Consumption-based | Included entitlements | Larger included entitlements |
| Additional credits | Yes | Yes | Yes |
| Best suited for | Diverse workloads | Profile-centric deployments | More advanced profile deployments |
When Should You Choose Flex Credits?
Flex Credits can make sense when:
- Usage varies considerably
- Multiple Data 360 capabilities are required
- Real-time processing is important
- Segmentation is extensive
- Query activity is significant
- Consumption needs to scale dynamically
For example, a company building an advanced data platform for AI, real-time activation and multiple downstream systems may prefer consumption-based flexibility.
When Should You Choose Profile Pricing?
Profile pricing can make sense when:
- Customer profiles are the primary use case
- The organization wants predictable pricing
- Profile volumes are relatively stable
- Core Customer 360 capabilities are the priority
It can simplify budgeting because the main pricing variable becomes the number of profiles.
When Should You Choose Enterprise Profiles?
Enterprise Profiles may be more appropriate when an organization needs the broader included capabilities associated with the Enterprise tier.
The current Salesforce pricing page includes higher included transformation and calculated insight allowances, more included segments and additional Flex Credits compared with the Profiles option.
Salesforce Data 360 Hidden Costs
The biggest budgeting mistake is looking only at the product price.
Several additional costs can affect the overall project.
Data Engineering
Source data may require substantial preparation.
Integration Development
Custom APIs, middleware and legacy integrations can increase project scope.
Data Migration
Historical customer data can require:
- Extraction
- Cleansing
- Transformation
- Mapping
- Validation
Identity Resolution
Complex matching rules can require significant design and testing.
Governance
Enterprise environments often need:
- Access controls
- Data classification
- Privacy controls
- Audit processes
- Ownership models
Training
Teams need to understand how to use unified data.
Managed Services
Ongoing support can be required after launch.
Salesforce Data 360 Total Cost of Ownership
A useful TCO model is:
Data 360 TCO = Licensing + Implementation + Integration + Data Engineering + Governance + Training + Operations
This is more useful than comparing license prices alone.
For a three-year business case, evaluate:
Year 1
- License
- Implementation
- Integration
- Migration
- Training
Year 2
- License
- Consumption
- Support
- Optimization
- New use cases
Year 3
- License
- Consumption
- Expansion
- Additional integrations
- Platform optimization
Data 360 Cost Optimization Strategies
1. Do Not Ingest Everything
Not every enterprise dataset needs to live inside Data 360.
Evaluate whether a source should be:
- Ingested
- Federated
- Queried
- Activated
2. Evaluate Zero Copy
Where supported, zero-copy can reduce unnecessary duplication.
Salesforce currently describes zero-copy integrations as part of its free ingestion model.
3. Prioritize High-Value Use Cases
Start with business outcomes such as:
- Customer retention
- Lead conversion
- Personalization
- Service optimization
- AI agent context
Avoid building an enormous data platform without a measurable use case.
4. Monitor Consumption
Salesforce provides Digital Wallet for monitoring consumption-based Salesforce products, including Data 360.
Monitor:
- Credits consumed
- Processing volume
- Real-time usage
- Segmentation
- Activation
- Queries
5. Avoid Unnecessary Real-Time Processing
If daily updates are sufficient, a real-time pipeline may add unnecessary complexity and cost.
6. Improve Data Quality Upstream
Poor data can increase processing and operational effort.
7. Design the Data Model Carefully
A strong model reduces unnecessary transformations and rework.
Salesforce Data 360 Pricing and AI
Data 360 pricing becomes even more important when AI and Agentforce are part of the roadmap.
An organization may use Data 360 to provide context to:
- Agentforce
- Sales AI
- Service AI
- Marketing personalization
- Customer intelligence
- Automated workflows
Salesforce's current Data 360 pricing model allows Flex Credits to be transferred between Data 360 and Agentforce, according to its pricing documentation.
This creates an important planning question:
How much of your Data 360 investment will support AI use cases?
AI should not be treated as an isolated layer.
The quality, freshness and accessibility of the underlying data can directly affect the usefulness of AI applications.
Data 360 Pricing for Agentforce Use Cases
A typical architecture might look like:
CRM → ERP → Marketing → Service → Data 360 → Unified Customer Context → Agentforce → AI-assisted Action
The Data 360 budget should therefore consider:
- Profile creation
- Data preparation
- Unification
- Querying
- Real-time data
- Agentforce consumption
- Activation
This is especially relevant as Salesforce continues expanding its data and AI architecture. Salesforce's 2026 announcements describe Data 360 as part of its broader agentic platform strategy.
Salesforce Data 360 Pricing for Marketing Use Cases
Marketing use cases can require:
- Customer profiles
- Segmentation
- Data activation
- Journey orchestration
- Personalization
- Real-time signals
For example:
Data 360 → High-value customers → Customers with declining engagement → Segment → Marketing Cloud → Retention Journey
The cost model therefore needs to consider not just profiles but also segmentation and activation activity.
Salesforce Data 360 Pricing for Service Use Cases
A service organization may use Data 360 to combine:
- Customer profile
- Service cases
- Purchases
- Contracts
- Product usage
- Customer interactions
This can support:
- Agentforce Service
- Service personalization
- Next-best action
- Customer health scoring
The more frequently the data is processed and activated, the more important consumption planning becomes.
Salesforce Data 360 Pricing for Enterprise Integration
Large enterprises should model pricing around their integration architecture.
For example:
SAP
Batch transaction data
Salesforce CRM
Customer and account data
Snowflake
Analytical datasets
Website
Behavioral events
Marketing Cloud
Engagement
Data 360
Unified profile
This architecture creates different data flows with different consumption characteristics.
A pricing model should therefore evaluate each integration independently.
Salesforce Data 360 Cost Planning Framework
Before requesting a quote, create a worksheet with these categories.
Customer Data
- Number of profiles
- Number of customer entities
- Number of accounts
- Number of contacts
Sources
- CRM
- ERP
- Marketing
- Website
- Commerce
- Service
- Data warehouse
- Legacy applications
Data Volume
- Records
- Daily changes
- Historical data
- Unstructured data
Processing
- Transformations
- Calculated insights
- Identity resolution
- Segmentation
Activation
- Destinations
- Audience sizes
- Frequency
- Channels
Real-Time
- Streaming events
- Real-time pipelines
- Response requirements
AI
- Agentforce
- Intelligent context
- AI-powered processing
This gives the Salesforce account team and implementation partner enough context to build a more realistic commercial model.
Salesforce Data 360 Pricing Mistakes to Avoid
Mistake 1: Comparing Only the License Price
The implementation can represent a significant part of the overall investment.
Mistake 2: Ignoring Data Quality
Poor source data increases implementation effort.
Mistake 3: Assuming All Data Should Be Ingested
Zero-copy and other integration options can change the architecture.
Mistake 4: Making Everything Real-Time
Real-time should be justified by business requirements.
Mistake 5: Ignoring Consumption
Consumption-based actions can become significant as usage scales.
Mistake 6: Building Without a Use Case
A large data platform without clear activation can create cost without sufficient business value.
Mistake 7: Ignoring AI Requirements
If Agentforce is part of the roadmap, the data architecture should account for AI context from the beginning.
How to Build a Salesforce Data 360 Budget
A practical budget can use five layers.
Layer 1: Platform
- Data 360 SKU
- Profiles
- Flex Credits
- Storage
- Add-ons
Layer 2: Implementation
- Architecture
- Configuration
- Data modeling
- Identity
- Security
- Testing
Layer 3: Integration
- Salesforce
- ERP
- Data warehouse
- Marketing
- Custom applications
Layer 4: Adoption
- Training
- Documentation
- Governance
- Change management
Layer 5: Operations
- Support
- Optimization
- Monitoring
- Consumption management
- Enhancements
MoreYeahs for Salesforce Data 360
MoreYeahs approaches Salesforce work as a combination of implementation, integration, data migration, automation and ongoing optimization.
Its current Salesforce practice highlights a five-stage delivery model:
Discovery → Configuration → Integration → Training → Optimisation.
The company also states that it has built Salesforce integrations with SAP, NetSuite, Dynamics 365 and custom systems, using real-time APIs, near-real-time middleware and batch integration patterns.
For a Data 360 project, this type of integration experience is relevant because Data 360 pricing cannot be separated completely from the complexity of the surrounding enterprise architecture.
MoreYeahs can support areas such as:
- Salesforce implementation
- Data migration
- Enterprise integration
- API integration
- Data mapping
- Salesforce optimization
- Automation
- Managed services
- AI and Agentforce initiatives
The company's Salesforce services page currently reports 200+ projects and 94% client satisfaction, alongside its five-stage delivery model. These are MoreYeahs-reported figures and should not be interpreted as a guarantee of project outcomes.
Salesforce Data 360 Pricing Checklist
Before finalizing a Data 360 budget, answer:
Licensing
- Which Data 360 SKU is required?
- Flex Credits or Profile pricing?
- Enterprise Profiles required?
- Storage requirements?
- Additional add-ons?
Data
- How many profiles?
- How many source systems?
- How much historical data?
- How frequently does data change?
Integration
- Which systems need integration?
- Which have native connectors?
- Which require APIs?
- Which require MuleSoft?
- Can zero-copy be used?
Processing
- How much transformation?
- How much identity resolution?
- How many calculated insights?
- How many segments?
Activation
- How many destinations?
- How frequently will data be activated?
- How large are the audiences?
Real-Time
- Which use cases need streaming?
- Which require real-time processing?
- What latency is actually required?
AI
- Is Agentforce part of the roadmap?
- What customer context will agents need?
- How much real-time information is required?
Operations
- Who monitors consumption?
- Who manages data quality?
- Who supports integrations?
- Who handles Salesforce releases?
Final Takeaway
Salesforce Data 360 pricing should not be evaluated as a single number.
The current pricing structure gives enterprises multiple options:
Flex Credits
for consumption-based flexibility.
Profiles
for predictable profile-based pricing.
Enterprise Profiles
for broader included capabilities.
Data 360 Starter
for organizations purchasing a larger packaged Data 360 deployment.
Salesforce currently lists:
$500 per 100K Flex Credits
$240 per 1K Profiles/year
$420 per 1K Enterprise Profiles/year
and a $60,000/year Data 360 Starter SKU.
But the real cost of Data 360 depends on what the organization does after the data enters the platform.
The most important budgeting questions are:
How many profiles do we need?
How much data needs to be processed?
How often will it be processed?
How much needs to be unified?
How many segments will we activate?
Which systems need integration?
Which workloads require real-time processing?
Can zero-copy reduce unnecessary data movement?
How will Data 360 support AI and Agentforce?
Who will manage the platform after implementation?
A strong Data 360 business case therefore combines licensing + implementation + integration + data engineering + governance + operations + expected business value.
That approach gives enterprise teams a much more realistic view of Salesforce Data 360 Total Cost of Ownership.
