February 26, 2026
In Salesforce Revenue Cloud, you map fields from a Quote to an Order through a Context Definition, not a direct object-to-object link. You add an attribute to the Sales Transaction Context, map your Quote field into it, then map that same attribute back out to the Order. Map the node first, then its attribute, and turn on both Input and Output. That one pattern drives the whole handoff.
Legacy Salesforce CPQ did this with matching 'twin fields' on both objects. Revenue Cloud drops that rule. The new model is a relief once it clicks, and a little confusing the first time you go looking for it.
This guide covers both halves. First, what Salesforce Revenue Cloud is and where it sits in quote-to-cash. Then the exact steps to map Quote-to-Order fields, with the attribute-tag detail, the map-the-node-first rule, the pricing-procedure step most walkthroughs skip, plus comparison tables, a Transaction Line Editor check, troubleshooting, and FAQs you can act on today.
Salesforce Revenue Cloud is Salesforce's platform for running the entire revenue lifecycle on one data model, from the first quote to cash in the bank. You'll also see it written as revenue cloud salesforce, Salesforce Revenue Lifecycle Management, or just Revenue Lifecycle Management (RLM). Same platform, different labels.
It pulls the moving parts of Salesforce Revenue Management into one flow: configure, price, quote; contracts; orders; billing; and subscriptions. Old orgs stitch those steps together with custom code and nightly syncs. Revenue Cloud links them on shared objects instead.
The newest tier is Salesforce Revenue Cloud Advanced. It's rebuilt on core platform objects like Sales Transaction. Those are the same objects you'll map against below, so the 'what is it' and the 'how do I do it' sit close together. If your team is weighing a move onto this model, our Revenue Cloud implementation team plans the data model before a single field gets touched.
If your team grew up on Salesforce CPQ, this shift matters. Classic CPQ was a managed package bolted onto the platform. Revenue Cloud Advanced is native to it. That one change reshapes how data moves. It also changes how much upkeep you sign up for.
Here's how the two stack up across the factors that matter most:
For a wider view of how the two products compare, Salesforce Ben's coverage of Revenue Cloud and CPQ is a useful read.
Moving an existing CPQ org onto this model is its own project, which is where legacy CPQ migration support earns its keep.
Salesforce quote-to-cash is the path a deal takes from a priced quote to recognized revenue. Revenue Cloud runs each stage on the same platform, so data isn't re-keyed at every handoff. That's the payoff of the shared-object model.
Here's how the stages line up, and where the Quote-to-Order step you're mapping actually lives:
Mapping fields from Quote to Order is the second handoff in that chain. Get it right and every stage after it inherits clean data.
Three capabilities carry the back half of quote-to-cash, and each one leans on the same clean handoff you're setting up.
Advanced Salesforce Revenue Cloud Billing turns active orders and subscriptions into invoices without manual re-entry. If an Order field arrives blank because a mapping was missed, that gap follows the record straight onto the invoice.
Salesforce subscription management tracks each sold asset across its life - renewals, upgrades, downgrades, and cancellations - so recurring revenue stays accurate as customers change plans.
Salesforce billing automation ties it together. Usage and schedule data flow from the order to billing on a set cadence, so finance isn't rebuilding invoices by hand every cycle. Wiring Revenue Cloud to billing and fulfillment cleanly is an integration architecture job. Clean field mapping upstream is what keeps that automation honest.
Worth knowing up front: Salesforce is renaming Revenue Cloud to Agentforce Revenue Management, folding AI agents into quoting, contracts, and order workflows.
The name is changing. The mechanics in this guide are not. Context Definitions, Sales Transactions, and entity mapping all work exactly as described here, whichever label shows up in your org's Setup menu.
Field values don't travel straight from a Quote to an Order. They pass through a context layer:
Quote (Source) → Sales Transaction Context → Order (Target)
Two mapping actions happen. First, the Quote field goes into a shared attribute. Then that attribute goes out to the Order field. Learn it once and every future mapping follows the same shape. Salesforce's own developer documentation on Context Definitions covers the Sales Transaction data model if you want to go deeper.
The naming rule is the biggest change to unlearn. Here's the side-by-side:
One rule trips up almost every first-time setup: map the node before you map its attributes. In both Quote Entities Mapping and Order Entities Mapping, the node (Sales Transaction or Sales Transaction Item) has to be mapped first. Only then will its attributes accept a source or target.
Skip the node and the attribute row looks selectable but never saves a value. If your mapping seems to 'not stick,' check that the node above it is mapped first.
There are two mapping levels, and each one uses a different context node:
DetailHeader-LevelLine-LevelContext nodeSales TransactionSales Transaction ItemSource objectQuoteQuote LineTarget objectOrderOrder ProductExample fieldRequested Delivery DateLine Configuration NotesCommon mistakeMapping a line field on the header nodeMapping a header field on the item node
Pick the wrong node and nothing throws an error - the field just stays empty. That silent miss is the single most common cause of a 'mapping didn't work' ticket.
Each attribute has an Input setting and an Output setting. Input pulls a value in from the source. Output pushes it back out to the target. Turn on both, or data flows one way and stops.
This example maps a Requested Delivery Date field from Quote to Order.
Line-item detail - like Line Configuration Notes on a configured product — rides through the Sales Transaction Item node instead of Sales Transaction. The shape is the same; only the node changes.
Before you convert anything, check the Transaction Line Editor (TLE). This is the pricing surface Revenue Cloud uses on the Quote, and a mapped attribute has to persist there before it can flow onward.
Open a Quote, launch the Transaction Line Editor, and confirm your custom value holds after a reprice. If it clears when the TLE recalculates, the attribute isn't wired into the pricing procedure yet - which is the exact step below. A value that survives the TLE will survive the conversion.
Here's the one that fills support forums. You extend the Sales Transaction Context, map both sides, activate, convert — and the field still shows up blank. The mapping is fine. The problem is elsewhere.
Revenue Cloud runs your Context Definition through the pricing procedure during conversion. If that pricing procedure still references the standard Sales Transaction Context instead of your extended one, your new attribute never gets read. Setting the extended definition in Revenue Settings is only half the wiring.
Open your default pricing procedure and confirm it points at the same extended Context Definition you mapped against. Community threads on this exact symptom keep landing on the same fix — the Trailblazer Community threads on quote-to-order mapping repeat it in thread after thread. Check this before you re-map anything.
The same idea applies when you reprice an order. If a custom tag isn't mapped in Order Entities Mapping for every procedure that touches the order, repricing can throw an error. Map the tag everywhere the pricing procedure expects it, not just on the first pass. Keeping hundreds of these mappings stable across releases is where our release governance and Managed Services team does its steady work.
Mapping and conversion are two different actions, and it helps to see them together.
To convert, open an accepted Quote that has at least one Quote Line and click Create Order. Revenue Cloud spins up the Order and its Order Products, running your Context Definition as it goes. Open the new Order and confirm each mapped field — header and line — carries the value from the Quote.
If a value is missing, don't re-map yet. Check the node mapping, the Input/Output toggle, the active definition in Revenue Settings, and the pricing procedure reference first. That short list clears most conversion misses.
Plenty of teams need a value to travel past the Order — from Quote Line to Order Product to Asset, and on to Asset State. The pattern holds, but the mapping objects change.
Propagating a field all the way to the asset lifecycle uses dedicated maps like AssetStatePrdToSalesTxnItmMap and AssetToSalesTransactionMapping. Set up the Quote-to-Order hop first and confirm it works, then extend the same attribute downstream one object at a time. Testing each hop on its own tells you exactly where a value stops flowing.
Most 'mapping didn't work' tickets trace back to one of these causes:
Salesforce Revenue Cloud is Salesforce's platform for running the full revenue lifecycle — quote, order, billing, and subscriptions — on one shared data model. It's also called Salesforce Revenue Lifecycle Management, and its native tier is Revenue Cloud Advanced.
Create an attribute on the Sales Transaction Context Definition, tag it, and enable Input and Output. Map the node first, set your Quote field as the source, then map that attribute to your Order field as the target. Activate the definition to go live.
Open an accepted Quote with at least one Quote Line and click Create Order. Revenue Cloud creates the Order and Order Products and runs your active Context Definition, carrying mapped values across as it builds the record.
Open your active Context Definition and review Quote Entities Mapping and Order Entities Mapping for the attribute. Confirm the value holds in the Transaction Line Editor, then convert a test Quote and confirm it lands on the Order. If it doesn't, check the node, Input/Output, Revenue Settings, and the pricing procedure reference.
A quote is the priced proposal you send a customer; an order is the accepted, fulfillable commitment created once they say yes. In Revenue Cloud, converting the quote creates the order and copies mapped field values across.
Revenue Cloud Advanced is the native successor to the classic Salesforce CPQ managed package. Existing CPQ orgs still run, but new field mapping moves from twin fields to Context Definitions.
Yes. Salesforce Revenue Cloud Billing and subscription management sit downstream of the order, turning mapped order data into invoices and tracking each asset through renewals and changes.
Yes, through the Sales Transaction Item node - used for Quote Line to Order Product mapping, separate from the header-level Sales Transaction node.
No. The rebrand changes the product name only. Context Definitions and entity mapping work exactly as described here either way.
A single field mapping is a five-minute task. Keeping hundreds of them stable is a different job. They have to survive every release, product change, and org migration — and that's the one we do. At Minuscule Technologies, we act as your Salesforce engineering partner across the full quote-to-cash lifecycle. That runs from Context Definition design to pricing-procedure wiring and release governance.
Ready to stop chasing manual re-entry between Quote and Order? Talk to our Revenue Cloud team about a governed, release-proof field-mapping setup.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
