Skip to main content

Maintain Your CPQ Administrator Certification for Spring ’26

Learning Objectives

After completing this unit, you’ll be able to:

  • Explain how implementation sequencing, feature scoping, and cross-functional discovery influence data migration readiness in Revenue Cloud.
  • Identify key limitations of the Debug Preview feature and apply best practices to ensure approval flows run successfully during preview execution.
  • Recognize the Revenue Cloud capabilities supported in a coexistence model.
  • Describe the requirements for supporting coexistence between Salesforce CPQ and Billing.
  • Identify key Revenue Cloud capabilities that are not available in Salesforce CPQ.
  • Compare how asset management works in Salesforce CPQ versus Revenue Cloud Advanced.
  • Describe how agents integrate with Revenue Cloud Advanced and explain how AI-driven interactions enhance revenue processes.

Stay Current with Your Certification

Salesforce certifications hold the most value when you keep them relevant. To keep your CPQ Administrator certification current, complete this badge by the due date.

Interested in learning more about getting certified? Check out the CPQ Administrator certification.

Note

While anyone can earn this badge, it is designed for those who hold the CPQ Administrator certification.

As part of the Salesforce Certification Program, you agree to the terms of the Salesforce Certification Program Agreement. Review the exam policies in the agreement and the Salesforce Certification Program Agreement and Code of Conduct article before you continue.

CPQ Administrator Certification Overview

Certified CPQ administrators know how to:

  • Design scalable product and pricing models that support complex sales scenarios.
  • Configure accurate quoting and approval processes that reduce errors and sales friction.
  • Optimize quote-to-cash workflows to improve deal velocity and revenue accuracy.
  • Collaborate with sales, finance, and operations to align CPQ solutions with business goals.

The badge highlights key updates you need to know for Spring ’26 to keep your certification current and your skills sharp.

Prepare for Data Migration in Revenue Cloud

Before migrating data into Revenue Cloud (RCA), you must establish a strong implementation foundation that reduces rework, minimizes data quality issues, and ensures processes work as intended. An effective discovery process can help you uncover your current state (existing systems, data models, and processes), future state, and business drivers behind each requirement.

This discovery phase should involve key stakeholders across sales, finance, operations, IT, and billing to identify pain points, inefficiencies, and opportunities for automation. Migration planning isn’t just technical—it’s a cross-functional effort that directly impacts quoting accuracy, billing integrity, and downstream automation.

Assess Which Revenue Cloud Features You’ll Use

Not every organization uses every Revenue Cloud capability. As part of migration planning, determine which features you’re implementing now versus later.

Many organizations adopt a phased approach, migrating only the data required to support the first release and expanding over time. This reduces risk and accelerates time to value.

Evaluate Your Quote-to-Cash Data Landscape

As you prepare for migration, review how you currently manage data across the quote-to-cash lifecycle.

Sales, Pricing, and Quotes

  • How products are structured (bundles, options, attributes)
  • How pricing and discounts are applied and approved
  • Where quoting delays or errors commonly occur
  • Which opportunities are managed from lead to close

Contracts and Orders

  • How contracts are generated and managed
  • How renewals, cancellations, amendments and order handoffs are handled

Billing and Invoicing

  • The current billing models, cycles, and frequencies
  • How invoices are generated, delivered, and reconciled
  • Your tax calculation and compliance processes
  • How payments are processed and applied

Data and Systems

  • Current systems involved in the quote-to-cash process (CRM, ERP, billing systems, and so forth)
  • Which systems store revenue and product data
  • The key integration points required for a seamless Revenue Cloud solution
  • Required integrations and legacy data dependencies

Plan Migration Scope and Timing

Data migration effort can significantly influence your overall project timeline. Migration complexity increases with:

  • High data volumes.
  • Custom pricing or product structures.
  • Multiple legacy systems.
  • Extensive integrations.
  • Limited subject-matter expert availability.

Avoid scheduling migrations during major business events like product launches or peak sales cycles.

Follow a Phased Build Sequence

Most Revenue Cloud implementations—and migrations—follow a logical order.

  • Product catalog setup: Define products, bundles, and attributes first. Most Revenue Cloud features depend on this foundation.
  • Pricing and pricing models: Configure price rules, tiers, subscriptions, and volume pricing before migrating transactional data.
  • Sales and contract processes: Enable quoting, ordering, contract, and asset workflows.

From there, migrate data to support additional capabilities such as billing automation, consumption models, fulfillment orchestration, portals, or ERP integrations.

Choose the Right Data Migration Tools

Selecting the appropriate data import method depends on data volume and complexity.

  • Salesforce Data Loader for smaller or simpler datasets
  • Bulk API for large-scale data imports
  • Third-party tools for complex transformations or multi-system migrations

Because every migration is unique, Salesforce recommends evaluating your data thoroughly and, when appropriate, working with a certified Salesforce partner.

For CPQ administrators, data migration readiness isn’t about memorizing tools—it’s about understanding how to structure product, pricing, and revenue data before migration begins. Strong planning upfront ensures Revenue Cloud delivers accurate quotes, clean contracts, and reliable billing from day one.

Before migrating data into Revenue Cloud Advanced, organizations must complete foundational implementation planning. Migration readiness depends on having a clearly defined product catalog, pricing models, and sales processes already configured in Revenue Cloud.

Key preparation steps include:

  • Gather cross-functional business requirements (sales, finance, operations, IT).
  • Identify which Revenue Cloud features will be implemented initially versus later.
  • Assess existing data quality and structure across CRM, CPQ, billing, and ERP systems.
  • Map legacy CPQ and billing data to the Revenue Cloud data model.
  • Select appropriate data migration tools based on data volume and complexity.

In Revenue Cloud, data migration is tightly coupled to implementation sequencing. Product and pricing configuration must be completed before transactional data is migrated.

Debug Preview Feature Limitations

This section outlines known limitations of the Debug Preview feature and how administrators can avoid common issues.

Supported Editions

Debug Preview is available in Lightning Experience for Enterprise, Unlimited, and Developer Editions of Revenue Cloud when Advanced Approvals is enabled.

Flow Activation and Qualification

Debug Preview only runs on active flows that use the Autolaunched Flow Approval Process (No Trigger) type. If the flow isn’t active or doesn’t meet this requirement, the preview fails. Always verify that the associated workflow is active and configured with the correct flow type.

Stage and Step Exit Criteria

If a stage’s exit criteria depend on steps that were skipped due to entry conditions, the stage or step may fail during preview and enter an error state. Review all stage and step conditions to ensure they can exit successfully, even when some steps don’t run.

Asynchronous Step Simulation

Asynchronous steps—such as background updates, subflows, or callouts—don’t run automatically in Debug Preview. To test them, configure simulated steps and provide mock output values in the debug configuration.

Input Variable Support

Debug Preview doesn’t support passing additional input variables at runtime. To prevent failures, define default values for required input variables directly in Flow Builder so they’re available during preview execution.

Approval Chain Name Display

Approval chain names appear in all uppercase in the Preview component due to a known cosmetic limitation. This behavior doesn’t affect functionality, and no workaround is currently available.

Revenue Cloud Coexistence with Salesforce CPQ and Billing

Revenue Cloud can coexist with the Salesforce CPQ and Salesforce Billing managed packages in the same org when all required licenses and features are enabled.

Coexistence Requirements

To support coexistence, the Salesforce org must:

  • Have Revenue Cloud, Salesforce CPQ, and Salesforce Billing managed packages provisioned and enabled.
  • Include both the Revenue Cloud Advanced and Revenue Cloud Billing licenses.
  • Have Billing in Revenue Cloud enabled.

Supported Revenue Cloud Capabilities

When coexistence is configured, Revenue Cloud users can:

  • Create quotes, orders, and contracts.
  • Activate orders to generate corresponding assets.
  • Amend, renew, or cancel orders and manage related assets.
  • Generate billing schedules and invoices.
  • Create, apply, and unapply credit memos.
  • Create dual transaction journals.

Configuration Overview for Billing

To transition to Revenue Cloud while preserving existing Salesforce Billing processes, configure Salesforce Billing to bypass standard billing logic for Revenue Cloud–created orders. This approach ensures Revenue Cloud orders don’t trigger duplicate billing, tax, or revenue recognition workflows.

Supported Editions

Available in all Salesforce Billing editions.

Required Permissions

System Administrator profile.

Prerequisite

Upgrade Salesforce Billing to Summer ’25 before completing the next steps.

Step 1: Create a Custom Order Field

Create a custom picklist field on the Order object to control Salesforce Billing processing.

  1. From Object Manager, select Order | Fields & Relationships.
  2. Click New and select Picklist.
  3. Enter Salesforce Billing Order Processing as the field label.
  4. Select Enter values, and add Skip.
  5. Set the API name to SalesforceBillingOrderProc__c.
  6. Configure field-level security for the appropriate profiles.
  7. Add the field to the relevant page layouts and save.

This field flags Revenue Cloud orders so Salesforce Billing can bypass standard processing.

Step 2: Create Billing, Tax, and Revenue Recognition Rules

Create rules in Salesforce Billing that explicitly prevent invoicing, taxation, and revenue recognition.

Billing Rule

  • Name: Do Not Invoice
  • Generate Invoice: No

Tax Rule

  • Name: Do Not Tax
  • Taxable: No

Revenue Recognition Rule

  • Name: Do Not Recognize
  • Create Revenue Schedule: No

These rules ensure Revenue Cloud orders don’t trigger Salesforce Billing automation.

Step 3: Create Orders in Revenue Cloud

Create Order records in Revenue Cloud using the Place Order API, passing values that instruct Salesforce Billing to skip processing.

Required Field Values

  • Order.SalesforceBillingOrderProc__c = Skip
  • OrderItem.blng__BillingRule__c = Do Not Invoice rule ID
  • OrderItem.blng__TaxRule__c = Do Not Tax rule ID
  • OrderItem.blng__RevenueRecognitionRule__c = Do Not Recognize rule ID

These values are included in the API payload across the Order, Order Action, and Order Item records. For an example of what this payload looks like, check out our help documentation.

Optional Automation

To reduce manual effort, create a Revenue Cloud–specific Order record type and set the default value of SalesforceBillingOrderProc__c to Skip. This automatically applies the correct behavior when orders are created in Revenue Cloud.

New Revenue Cloud Features

Revenue Cloud introduces several capabilities that extend beyond traditional Salesforce CPQ functionality. These include Salesforce Contracts for centralized and scalable contract lifecycle management, Dynamic Revenue Orchestrator for coordinating complex fulfillment and billing workflows, and native support for advanced consumption and usage-based revenue models. Revenue Cloud also provides tighter integration across sales, fulfillment, billing, and finance, enabling a more connected revenue lifecycle. For CPQ administrators, the key takeaway is that Revenue Cloud is not simply “CPQ plus billing” but an end-to-end revenue platform with orchestration and lifecycle management capabilities that CPQ alone does not offer.

For a full features list, check out the help article, Functional Area and Feature Availability in Revenue Cloud Licenses.

Asset Management

Use the Assets tab on Account and Contract records to view and manage customer assets in Revenue Cloud. From this view, admins can update asset details such as renewal terms and auto-renewal settings.

This feature is available in Lightning Experience for Enterprise, Unlimited, and Developer Editions of Revenue Cloud when Transaction Management is enabled.

Required Permissions

  • View on Account to access account records
  • View on Contract to access contract records
  • Read, Create, Edit, and Delete on Assets to manage assets and use the Managed Asset Viewer component

Access and Manage Assets

  • From the App Launcher, open Accounts or Contracts.
  • Select a record.
  • Open the Assets tab.
  • Click an asset name to open the side panel and view asset details.

Edit an Asset

  • Select Show Actions next to the asset.
  • Click Edit.
  • Update the required fields and save your changes.

Asset Behavior Across Transactions

When Transaction Management is enabled, Revenue Cloud carries forward asset attributes—such as auto-renewal status—to downstream transactions. For example, when you create a quote from a contract, the asset’s auto-renewal setting is copied to the corresponding quote line items.

View Asset State and Actions

To view the asset state period and related asset actions:

  • Select Show Actions next to the asset.
  • Click View.

When you select the checkbox in the Managed Assets header, only the assets currently loaded on the page are selected.

Agentforce for Revenue Cloud

Agentforce for Revenue Cloud is a suite of AI-powered agents that streamline product-to-cash operations across the revenue lifecycle available in Lightning Experience for Enterprise, Unlimited, and Developer Editions of Revenue Cloud with the Agentforce Employee Agent add-on. These agents assist with tasks such as quote creation and management, overage consumption analysis, and billing inquiries with clear invoice line-item explanations. By using generative AI for reasoning and orchestration, Agentforce reduces manual effort and helps teams move faster with greater accuracy.

Agent Templates in Revenue Cloud

Revenue Cloud includes prebuilt Agentforce Employee Agent (AEA) templates designed for common revenue workflows. These templates allow administrators to quickly deploy AI-powered agents for product-to-cash operations. Access to Revenue Cloud solutions is required to use these templates.

Set Up Agentforce for Revenue Cloud

To use Revenue agent templates, admins must:

  • Configure the required Revenue Cloud and Agentforce features.
  • Enable agent management capabilities.
  • Assign the appropriate permissions to users.

Community and Partner Access

You can expose Agentforce for Revenue agents to customers or partners by configuring Experience Cloud sites and enabling Embedded Messaging.

Examples include:

  • Creating a community site for the Billing Service Assistance agent
  • Creating a partner site for the Revenue Quote Management agent

Considerations and Limitations

Before enabling Agentforce for Revenue Cloud, review supported functionality, usage guidelines, system limits, and known limitations to ensure the agents align with your business requirements.

Agentforce for Revenue Quote Management

The Revenue Quote Management agent template helps sales reps streamline quoting workflows and accelerate the sales cycle. Using simple prompts, reps can create and manage initial, renewal, and amendment quotes. Built-in Agentforce actions automate tasks such as product selection, quote creation, and line item updates—allowing quotes to be built in minutes instead of manually.

Agentforce for Billing Employee Assistance

Billing Employee Assistance provides internal finance and billing teams with a conversational way to understand billing data. Employees can ask questions about invoice charges, payment plans, outstanding balances, and upcoming due dates, and receive clear, AI-generated explanations without navigating multiple billing records.

Agentforce for Billing Service Assistance

The Billing Service Assistance agent enables customers to get fast, conversational explanations of invoice charges directly within an Experience Cloud billing portal.

Revenue Agent Topic Reference

Revenue Cloud also provides standard agent topics that support common revenue use cases. These topics aren’t included by default in Revenue agent templates, but admins can add them to any Agentforce Employee Agent template to extend agent functionality.

Sum It Up

In this badge, you explored how evolving Revenue Cloud capabilities impact the way CPQ administrators design, implement, and maintain quote-to-cash solutions. From preparing for Revenue Cloud data migration and understanding implementation sequencing, to navigating approval differences, coexistence models, and new platform capabilities, these Spring ’26 updates reinforce the importance of strong foundations, clear system ownership, and intentional design. You also learned how Revenue Cloud extends beyond traditional CPQ with unified asset management, advanced revenue orchestration, billing alignment, and AI-powered agents—equipping you to deliver accurate quotes, scalable revenue operations, and connected customer experiences as the platform continues to evolve.

Resources

在 Salesforce 帮助中分享 Trailhead 反馈

我们很想听听您使用 Trailhead 的经验——您现在可以随时从 Salesforce 帮助网站访问新的反馈表单。

了解更多 继续分享反馈