Salesforce Core, Advanced & Max: 2026 Renewal & Migration Guide
Salesforce's new Core ($195), Advanced ($395), and Max ($550) editions reshape the renewal decision. Pricing, bundles, negotiation tactics, and migration paths.
Planning a migration?
Get a free 30-min call with our engineers. We'll review your setup and map out a custom migration plan — no obligation.
Schedule a free call- 1,500+ migrations completed
- Zero downtime guaranteed
- Transparent, fixed pricing
- Project success responsibility
- Post-migration support included
Salesforce Core, Advanced & Max: 2026 Renewal & Migration Guide
On September 3, 2026, Salesforce introduced three new edition tiers — Core ($195), Advanced ($395), and Max ($550) per user per month — for Agentforce Sales, Agentforce Service, and Agentforce Industries (salesforce.com). If your renewal is approaching, you now face a decision that didn't exist six months ago: stay on your legacy Enterprise or Unlimited contract, convert to the new lineup, or leave Salesforce entirely.
This guide breaks down the pricing, what's bundled, what breaks if you change editions, and what each path actually costs — including the engineering realities of moving enterprise data off the platform.
Note on sourcing: Pricing figures in this guide are list prices as of November 2026, taken from Salesforce's pricing pages and announcements. Prices change, so check Salesforce's pricing page before you budget. Salesforce has not announced an end-of-sale date for Enterprise or Unlimited editions.
What are Salesforce Core, Advanced, and Max editions?
Salesforce Core, Advanced, and Max are the edition tiers Salesforce launched on September 3, 2026, for Agentforce Sales, Agentforce Service, and Agentforce Industries. Each tier bundles Agentforce AI, Slack, Tableau Next, a Premier Success Plan, enterprise-grade security, and a yearly pool of Flex Credits into a single subscription (salesforce.com).
The list prices as of November 2026, billed annually (salesforce.com):
| Edition | List price (per user/month) | Flex Credits (per org/year) | Legacy edition Salesforce compares it with | Price delta vs. legacy edition |
|---|---|---|---|---|
| Core | $195 | 500,000 | Enterprise ($175) | +$20/user/mo (+11.4%) |
| Advanced | $395 | 1,000,000 | Unlimited ($350) | +$45/user/mo (+12.9%) |
| Max | $550 | 2,750,000 | Agentforce 1 ($550) | No change |
Salesforce's pricing FAQ is explicit about the mapping: "Core replaces Enterprise Edition, Advanced replaces Unlimited Edition, and Max replaces Agentforce 1 Edition" (salesforce.com). The legacy Enterprise and Unlimited prices are from Salesforce's pricing page before the change (web.archive.org). Salesforce positions Core as offering "70% more value than legacy Enterprise Edition," Advanced as "more than 50% more value than legacy Unlimited Edition," and Max as "nearly 60% more value than Agentforce 1 Edition" (salesforce.com). Those value claims rest entirely on whether your org already purchases the bundled components separately — a point addressed directly below.
On the Sales Cloud pricing page (salesforce.com):
Core ($195/user/month) includes everything in Professional Edition plus Premier Success, Slack Business+, and Tableau Next.
Advanced ($395/user/month) adds enhanced security, more AI, and expanded data capacity, including Sales Programs and Backup & Recover, Archive, Data Detect, and Security Center.
Max ($550/user/month) adds Advanced Momentum, Agentforce for Sales and Agentforce Coworker, Spiff, Sales Planning, Salesforce Maps, and Slack Enterprise+.
Agentforce 1 Edition became generally available in June 2025, starting at $550/user/month with 1 million Flex Credits per org per year (salesforce.com). Max keeps the same price with 2.75 million Flex Credits, and existing Agentforce 1 customers can move to Max at no extra cost (salesforce.com).
Starter Suite ($25/user/month) and Pro Suite ($100/user/month) remain on the pricing page for smaller teams.
How much more do the new editions cost?
The list-price gap is straightforward. Core at $195 per user per month lists $20 above Enterprise at $175, an 11.4% difference. Advanced at $395 lists $45 above Unlimited at $350, a 12.9% difference. Max holds steady at $550.
At scale, the per-seat delta compounds fast:
| Team size | Legacy edition | Annual legacy cost | New edition | Annual new cost | Annual delta |
|---|---|---|---|---|---|
| 50 users | Enterprise ($175) | $105,000 | Core ($195) | $117,000 | +$12,000 |
| 200 users | Enterprise ($175) | $420,000 | Core ($195) | $468,000 | +$48,000 |
| 200 users | Unlimited ($350) | $840,000 | Advanced ($395) | $948,000 | +$108,000 |
| 500 users | Unlimited ($350) | $2,100,000 | Advanced ($395) | $2,370,000 | +$270,000 |
These are list-price comparisons. Your actual dollar delta depends on your contracted discount structure. The percentage increase, however, applies equally regardless of negotiated rate if Salesforce holds the discount tier constant.
Whether the nominal increase represents a real cost or a net saving depends entirely on what you already pay separately for the bundled components.
Context on prior price increases: Salesforce raised Enterprise and Unlimited list prices by an average of 6% on August 1, 2025 (salesforce.com). The 2026 edition transition represents a larger structural shift — not just a list-price adjustment, but a rebundling that changes what you're buying. Those are distinct negotiating situations.
What's actually bundled in every tier?
Every Core, Advanced, and Max edition bundles the following:
- Slack (Slack Business+ in Core and Advanced, Slack Enterprise+ in Max on the Sales pricing page)
- Tableau Next (Salesforce's agentic analytics product)
- Premier Success Plan (personalized, expert guidance for adoption)
- Data security (protecting sensitive data and managing permission changes)
- Agentforce AI (AI capabilities built for every role across Sales and Service workflows)
- Flex Credits (annual pool for consumption-based Agentforce agent actions)
The value proposition is straightforward: if you were already paying for Slack Business+, Tableau, and the Premier Success Plan as separate line items, the new bundled price may wash or save money. If you weren't using those products, the new editions are a price increase dressed as a bundle.
Price each component from your own order form or Salesforce's current price list. If your org licenses all three separately, those costs may exceed the $20/user/month premium for Core over Enterprise. If none of them are on your current order form, the premium is a straight cost increase.
Audit before you compare. Pull your current order form and list every add-on SKU. If Slack, Tableau, and Premier Support aren't on it, the "70% more value" math doesn't apply to your org.
What are the platform limits by edition?
The most common question from enterprise buyers evaluating edition tiers is what they actually gain or lose in platform capabilities. Salesforce's launch announcement does not publish API allocations or custom object limits for the new editions. The Sales Cloud pricing page does list included sandboxes, and they match the legacy editions Salesforce compares each tier with (salesforce.com, web.archive.org):
| Included sandboxes | Core (legacy: Enterprise) | Advanced (legacy: Unlimited) | Max (legacy: Agentforce 1) |
|---|---|---|---|
| Partial Copy | 1 | 1 | 1 |
| Full | Available for purchase | 1 | 1 |
Request a written specification of API allocations, storage, and custom object limits from your account executive before committing.
Critical gap for downgrade scenarios: If your current org is near the custom object limit of the edition you are evaluating, you must consolidate or delete objects before the change. This is not a data migration problem — it is an org architecture problem.
What are Flex Credits and what does one action cost?
Flex Credits are Salesforce's consumption-based pricing unit for Agentforce. As of November 2026, they cost $500 per 100,000 credits, which works out to $0.005 (half a cent) per credit. Each standard agent action costs 20 Flex Credits ($0.10), and Agentforce Voice actions cost 30 Flex Credits ($0.15) per action (salesforce.com).
The bundled allocations translate to the following action budgets:
| Edition | Included credits | Standard actions (÷20) | Voice actions (÷30) | Equivalent overage cost if purchased |
|---|---|---|---|---|
| Core | 500,000 | 25,000 | 16,667 | $2,500 |
| Advanced | 1,000,000 | 50,000 | 33,333 | $5,000 |
| Max | 2,750,000 | 137,500 | 91,667 | $13,750 |
To put consumption in perspective: a simple case management workflow (identify customer, retrieve cases, add comment) consumes 3 actions and 60 credits, costing $0.30 per workflow execution. A Core org receives enough credits for approximately 8,333 such workflows per year — roughly 694 per month across the entire org, whatever its user count, because the credits are allocated per org.
If your Agentforce usage is light, those credits are overhead baked into your seat price. If you're running AI agents at volume — for example, a service org routing and triaging 500 cases per day — a Core org running that three-action workflow would exhaust its annual credit allocation in about 17 days at that rate, triggering overage purchases at $500/100,000 credits.
Unused credits do not roll over into later subscription terms (salesforce.com).
Does anything change for existing customers before renewal?
Not before renewal. The new editions replace Enterprise, Unlimited and Agentforce 1 in Salesforce's lineup, but its announcement states: "Existing customer pricing on legacy editions remains unchanged" (salesforce.com). Your current contract holds until your renewal date. You are not facing an immediate forced migration or an end-of-life event for your current deployment.
What is confirmed:
- Current contract pricing is protected through the existing term
- The announcement gives no end-of-sale date for Enterprise or Unlimited editions
- The announcement gives no end-of-life date for Enterprise or Unlimited editions
What is not confirmed as of publication date:
- Whether new customers can still purchase Enterprise or Unlimited editions (the Sales Cloud pricing page now lists Starter, Pro Suite, Core, Advanced, and Max)
- Whether existing customers can renew on legacy editions after the current term expires
- Whether customers can add seats to a legacy edition mid-contract at legacy pricing
- Whether legacy edition pricing will be available at renewal or only until a future announced cutoff date
This ambiguity is not a minor detail — it is the central risk for customers planning multi-year budget scenarios. Salesforce's official position protects your current pricing. But there is no published guarantee you'll be able to renew on your legacy edition indefinitely. Get the renewal terms in writing from your account executive, specifically including the right to add seats on your current edition at current pricing for the full term.
Should you convert to Core/Advanced or stay on your legacy edition?
This is primarily a cost-of-bundle question, not a feature question. The underlying Salesforce platform hasn't changed — your Apex, flows, custom objects, and integrations all work the same way regardless of edition label. Edition differences manifest in platform limits (covered above) and bundled products, not in core CRM functionality.
Run this analysis before your next renewal conversation:
Step 1: Calculate your true current per-user cost. Add your negotiated seat rate + Slack subscription cost + Tableau licenses + Premier Success Plan cost + any Agentforce credits already purchased. Divide by your user count. This is your actual blended per-user cost.
Step 2: Compare to the new all-in rate. If your blended total already exceeds $195/user/month (Core) or $395/user/month (Advanced), converting may be cost-neutral or cheaper. If it's below, you're looking at a real increase.
Step 3: Estimate your Flex Credit consumption. Map your current or planned Agentforce use cases to the action model. If you're not deploying Agentforce agents, the included credits have no present value. The legacy-edition protection is your strongest card.
Step 4: Audit your edition utilization. Before converting to Advanced, confirm whether your users actually need features above Core. Check each Unlimited seat for a documented requirement for capabilities above Enterprise.
Step 5: Confirm your platform limits headroom. If your org uses many custom objects, makes heavy daily API calls, or runs complex automation at high volume, get Core's limits in writing and verify they support your current workload before agreeing to any tier conversion.
The negotiation order matters. Get the legacy-edition renewal quote first, in writing. Then evaluate the new-edition quote against it. Never accept the premise that you must convert — Salesforce has stated legacy pricing is unchanged for existing customers.
How to negotiate your Salesforce renewal in 2026
Start the internal audit at least 120 days before your renewal date — not on the renewal date. Here's what to prepare:
Right-size seats first. Export login history and feature-usage reports. Identify users who haven't logged in within 90 days and users on Unlimited who don't use a single feature above Enterprise. The seat count and edition mix are the biggest cost levers — typically larger in absolute dollar terms than any percentage discount negotiation.
Get legacy-edition renewal terms in writing. Specifically request: (1) the right to renew on your current edition, (2) the right to add seats on your current edition at current pricing, and (3) confirmation of how long legacy pricing is available. Salesforce has not published answers to (2) and (3) publicly.
Request both quotes simultaneously. Send your right-sized proposal in writing and request both a legacy-edition quote and a new-edition quote at least 90 days before renewal. Negotiate absolute dollars per user against your last term — not a percentage off the new list price, which resets the anchor to Core/Advanced pricing.
Negotiate a renewal price cap. Push for a fixed ceiling on the percentage increase for every product line across the full contract term. Salesforce raised Enterprise and Unlimited list prices by an average of 6% on August 1, 2025 (salesforce.com). Without a cap, any subsequent list-price increases flow through at renewal.
Understand the new anchor. Core and Advanced are now the editions on Salesforce's public Sales Cloud price list. If you're negotiating against an Enterprise or Unlimited price point, you may be arguing about a number that is no longer on that list. Know whether your AE is quoting against legacy list or new list before you evaluate any discount percentage.
What happens to multi-cloud contracts? Salesforce has not published guidance on how Core/Advanced/Max adoption affects existing Marketing Cloud, Commerce Cloud, or MuleSoft contracts. If you have cross-cloud agreements, escalate to your account team before agreeing to any Sales Cloud or Service Cloud edition change. A Sales Cloud move to Core could affect pricing structures tied to other clouds in ways that aren't yet publicly documented.
Mid-term seat additions: If you need to add seats mid-contract on a legacy edition, the terms governing whether you can do so at your legacy rate — or only at the new edition rate — depend on your specific contract language. This is a live negotiating point; get written clarification before you need to add seats.
What breaks when you downgrade a Salesforce edition?
If you attempt to reduce costs by downgrading from Unlimited to Enterprise, or from a legacy tier to a lower new edition, you cannot flip a switch yourself. Edition changes go through your Salesforce account team, and your org has to fit within the lower edition's limits and features first.
API limits and integration failures
API request allocations depend on your edition and user license count, so a lower edition can mean a lower 24-hour allocation. Organizations heavily integrated with external ERPs, marketing automation platforms, or data warehouses via the REST or Bulk API commonly find a lower tier cannot support their daily sync volume.
When the allocation is exhausted, Salesforce rejects further calls until usage in the rolling 24-hour window falls back below it, causing data synchronization lag across dependent systems. For orgs running real-time inventory, billing, or support ticket synchronization, this is an immediate operational failure.
Custom objects and managed packages
Lower tiers allow fewer custom objects. If your current org uses more than the lower tier supports, you must delete or consolidate objects and their data first, so export anything you need to keep before you do.
Managed packages from the AppExchange specify minimum edition requirements. A package that installs and functions on Unlimited may refuse to install on a lower-tier org. Before committing to a downgrade, audit every installed package against its minimum edition requirement in the AppExchange listing.
Sandbox availability
Enterprise and Core include one Partial Copy sandbox, with a Full sandbox available for purchase. Unlimited and Advanced each include one Full sandbox (salesforce.com). If your release management process depends on a Full sandbox for staging or QA, a downgrade to Core means buying one or consolidating environments. This affects deployment velocity and regression testing coverage.
When does leaving Salesforce make sense?
For some teams, this edition restructuring is the trigger for a broader platform decision. The renewal math is a good forcing function to ask: does the complexity and cost of Salesforce still match how we actually sell?
Leaving typically makes sense when:
- Admin overhead exceeds the value. A dedicated Salesforce admin is a salaried role. For small teams, platform administration cost can exceed the value delivered by features that simpler CRMs handle natively.
- You use less than 20% of the feature surface. If your team only uses Accounts, Contacts, Opportunities, and basic reporting, you're paying enterprise prices for a subset of functionality available in cheaper platforms.
- The TCO floor is too high for your scale. At $195/user/month (Core) for 20 users, annual seat cost alone is $46,800 — before admin, integrations, or AppExchange add-ons. Comparable alternatives at list price as of November 2026, billed annually: HubSpot Sales Hub Professional at $90/seat/month ($21,600/year for 20 users) (hubspot.com); Pipedrive Premium at $49/seat/month ($11,760/year for 20 users) (pipedrive.com). These are not feature-equivalent products, but for lightweight sales workflows they may be functionally sufficient.
Leaving is harder when:
- You rely on multi-cloud integration. Sales Cloud + Service Cloud + Marketing Cloud sharing a single customer record with unified identity is not replicated natively by any direct competitor. Replicating it requires custom integration work on the destination platform.
- Your Apex codebase and custom objects are deep. Thousands of lines of Apex, complex trigger frameworks, and custom objects with rich lookup and master-detail relationships don't port to another CRM — they are rebuilt from scratch, which is a development project in its own right.
- Regulatory or compliance workflows are embedded. Financial services, healthcare, and public-sector orgs often have compliance logic (audit trails, field-level security, record retention policies) wired into Salesforce configuration that would require re-validation on any new platform, adding regulatory risk to the migration timeline.
- You are mid-term on a multi-year contract. Early termination penalties and committed spend obligations make mid-contract exits expensive. Run this analysis before your renewal window, not after.
Migration cost: Fixed-price migration services (see below) cover the data transfer. They do not cover rebuilding your platform, which you budget separately.
For detailed alternatives comparisons, see our Salesforce Service Cloud alternatives guide and Salesforce FSC alternatives analysis.
How does a CRM data migration work if you decide to leave?
If the renewal math pushes you off Salesforce, the next question is how you move your data — and how long it takes. Two timelines matter and they're independent: the data migration (moving records from Salesforce to the target CRM) and the platform implementation (rebuilding workflows, automations, and integrations on the new system). The data migration is typically the shorter of the two; platform reimplementation is your own project and usually takes considerably longer.
Getting data out of Salesforce
For most CRM datasets — Accounts, Contacts, Opportunities, Activities, Notes, and Attachments — Bulk API 2.0 via custom scripts is the fastest extraction path.
The transfer preference hierarchy is: API > JSON > CSV. CSV is the least preferred option because flat files strip away metadata, picklist values, and relational context that must be manually reconstructed in the destination system. Bulk API 2.0 does not support file and blob export natively, so attachments and files require a separate extraction pass through the REST API, adding time and API quota consumption to the project.
Handling polymorphic fields and activity history
Salesforce uses polymorphic fields — fields that can reference multiple object types from a single field. The most operationally significant examples are WhoId and WhatId on the Task and Event objects.
WhoIdcan reference either aLeador aContactWhatIdcan reference anAccount,Opportunity,Case,Contract, or other objects depending on org configuration
During extraction, the migration script must resolve each polymorphic ID, identify the target object type, and map the relationship correctly in the destination CRM schema. Failure to handle polymorphic fields results in orphaned emails, missing meeting notes, and broken activity timelines — a common data quality failure in Salesforce-to-CRM migrations.
Extracting attachments and files (ContentVersion)
Salesforce manages file storage through three linked objects: ContentDocument (the file record), ContentVersion (a specific version of the file, containing the binary data), and ContentDocumentLink (the junction object linking a file to a Salesforce record such as an Account or Opportunity).
Extracting a file requires:
- Querying
ContentVersionto identify the latest version and retrieve the binary payload - Querying
ContentDocumentLinkto determine which parent record (Account, Opportunity, Case, etc.) the file belongs to - Re-associating the file with the correct record in the destination system
Because files are large and each requires individual API calls for the binary payload, file extraction is the most API-bandwidth-intensive phase of a Salesforce migration. Orgs with tens of thousands of documents should plan for dedicated extraction windows to avoid hitting daily API limits on other integration dependencies.
Salesforce also maintains a legacy Attachments object from before the Files architecture was introduced. Older orgs may have records in both the legacy Attachments object and the modern ContentVersion system, requiring two separate extraction pipelines.
Migration timelines
Most CRM data migrations complete within 1–5 business days, depending on data volume, complexity, and API rate limits:
| Scenario | Volume | Timeline |
|---|---|---|
| Small dataset | Under 10,000 records | Under 24 hours |
| Most migrations | Depends on data volume, complexity, and API rate limits | 1–5 business days |
Large, file-heavy orgs use an initial bulk migration plus delta syncs. The bulk historical load runs on the working days before go-live while your team keeps working in Salesforce. Go-live is a Monday morning: Salesforce is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and users log in to the new CRM that day.
We recommend beginning the scoping conversation at least 3–4 months before an internal deadline — not because the data migration itself takes that long, but because the decision-making, field mapping, data quality remediation, and stakeholder alignment around a CRM change consistently extend beyond what organizations initially plan for.
Validation and cutover
Validation includes:
- Checksums on file exports to detect corruption
- Record-count parity checks on every migrated object
- Field-level verification on a sampled subset of records
- Referential integrity checks — every Opportunity verified against the correct Account, every Contact linked to its historical communication log
- Relationship integrity — lookup and master-detail relationships verified across the full object graph
Background sync with a fast cutover keeps source systems operational until validation passes. No cutover happens until all checks pass.
What does a CRM data migration cost?
Predictability matters most in an infrastructure project. Open-ended hourly billing creates misaligned incentives, penalizing the client for unexpected API limits or complex data mapping decisions that arise mid-project.
ClonePartner operates on one fixed price per project, starting at $500. No hourly billing, no hidden fees, no change orders, no per-record metering. The quote is driven by data volume, schema complexity, and the specific source and target platforms.
The process includes unlimited sample migrations until the data mapping is exactly right, with re-migration at no additional cost during the testing phase. You are assigned a dedicated migration engineer who owns the project end to end.
Security is embedded at the architectural level: ClonePartner is independently audited for SOC 2 Type II and ISO 27001, with GDPR, CCPA, and HIPAA safeguards. Data is encrypted with AES-256 at rest and TLS 1.2+ in transit. Staging databases auto-purge within 30 days of project close.
A decision framework for your 2026 renewal
The Salesforce edition change is a decision point, not a forced move. Your current contract pricing holds. Use the runway before renewal to answer three questions:
Question 1: Is the bundled value real for my org?
- Pull your current order form and sum the cost of Slack, Tableau, and Premier Support as separate line items
- If those costs exceed the per-user premium of Core over Enterprise (or Advanced over Unlimited), the bundle may save money
- If those products aren't on your order form, the premium is a straight cost increase — no "value" math applies
Question 2: Do I need Agentforce now?
- Map your current support and sales workflows to the Flex Credit consumption model
- If you're not deploying AI agents in the next 12 months, the included credits are sunk cost
- Protect your legacy edition pricing and revisit when Agentforce is part of your actual workflow planning
Question 3: Is Salesforce itself the right platform?
- Run the full TCO comparison: seats + admin + integrations + AppExchange add-ons vs. the alternative platform's equivalent
- Compare what you'd gain (simpler administration, lower seat cost) against what you'd rebuild (Apex, complex automations, multi-cloud integrations)
- The data migration is the tractable part; platform reimplementation is where migration projects fail to scope accurately
Decision matrix:
| Scenario | Recommended action |
|---|---|
| Already paying for Slack + Tableau + Premier Support | Evaluate Core/Advanced conversion; run the bundle math |
| Not using bundled products | Protect legacy edition; get renewal terms in writing |
| Deploying Agentforce in next 12 months | Evaluate Advanced or Max for Flex Credit headroom |
| Not deploying Agentforce | Legacy edition protection is highest value; defer conversion |
| Using <20% of Salesforce feature surface, <30 users | Run full TCO comparison against alternatives |
| Deep Apex codebase, multi-cloud dependencies | Stay on Salesforce; negotiate aggressively on price |
For more on evaluating CRM platforms, see our Salesforce vs HubSpot architecture guide or Salesforce vs Pipedrive comparison.
Frequently Asked Questions
- What are Salesforce Core, Advanced, and Max editions?
- Core ($195/user/month), Advanced ($395), and Max ($550) are the Salesforce editions launched September 3, 2026, for Agentforce Sales, Agentforce Service, and Agentforce Industries. Each bundles Agentforce AI, Slack, Tableau Next, a Premier Success Plan, and Flex Credits. Salesforce compares them with the legacy Enterprise, Unlimited, and Agentforce 1 editions.
- Does Salesforce Core replace Enterprise Edition?
- Yes. Salesforce's pricing FAQ says Core replaces Enterprise Edition, Advanced replaces Unlimited Edition, and Max replaces Agentforce 1 Edition. Its announcement also says existing customer pricing on legacy editions remains unchanged, and it gives no end-of-sale date for current contracts. Ask your account executive to confirm your renewal options in writing.
- Can I downgrade my Salesforce edition to save money?
- Edition changes are negotiated with your Salesforce account team, usually at renewal. Before you move to a lower edition, check what it includes, such as sandboxes, API allocations, and custom object limits, because a lower edition can break integrations that depend on them.
- How long does it take to migrate data off Salesforce to another CRM?
- The data migration itself — moving records, relationships, and attachments — typically completes within 1–5 business days, depending on data volume, complexity, and API rate limits. Small datasets under 10,000 records can finish in under 24 hours. This is separate from the platform implementation (rebuilding workflows and automations), which is a longer effort.
- Are Salesforce Flex Credits worth it?
- It depends on your Agentforce usage. Core includes 500,000 credits/year (about 25,000 standard actions). If you're actively deploying AI agents, the bundled credits offset a la carte pricing at $500 per 100,000. If you're not using Agentforce, those credits are unused value baked into a higher seat price — and they don't roll over.