Six months. A frozen deal desk. Lost pricing logic. Or not.
That's the usual cost of moving off legacy Salesforce CPQ. CrossXLane turns the migration into lanes you click through in days — pricing, approvals, bundles, and revenue recognition, mapped without freezing your deal desk or writing a line of Apex.
Your mapping structure, laid out as lanes
Every category of your legacy Salesforce CPQ becomes its own lane, running from where it lives today to where it lands in Agentforce Revenue Cloud. Each lane crosses on its own — point, click, done.
Pricing Lane
Every tiered discount schedule, price rule, and adjustment condition is read from your CPQ instance and rebuilt as a Revenue Cloud price rule — including nested conditions a flat data export would lose.
One lane, one migration action
CrossXLane breaks your CPQ instance into lanes — each one a self-contained migration action with its own source, target, and validation. Nothing moves until its lane is ready.
Pricing Lane
Price rules, discount schedules, and adjustment logic — rebuilt as Revenue Cloud price rules.
Approval Lane
Approval matrices and sign-off thresholds, rebuilt as declarative approval rules.
Bundle Lane
Product bundles, options, and configuration constraints, mapped without losing dependencies.
Quote Template Lane
Quote templates, terms, and output layouts, rebuilt to render natively in Revenue Cloud.
Catalog Lane
Product catalog structure and price books, mapped into the new catalog hierarchy.
Revenue Lane (ARM)
Billing schedules and recognition timing, mapped into Agentforce Revenue Management.
The problems every CPQ migration runs into
None of these are hypothetical — they're the reasons most legacy Salesforce CPQ migrations run long, run over budget, or get quietly shelved.
Pricing logic no one wrote down
Discount tiers and price conditions exist only as live configuration. Nobody remembers every edge case well enough to describe it, let alone rebuild it.
Years of custom Apex
One-off customizations built up over years rarely have a clean equivalent on the new platform — someone has to decide what's still needed.
Approval chains that break silently
A mis-mapped threshold doesn't throw an error — it just approves a deal it shouldn't have, and nobody notices until later.
No room to freeze the deal desk
Sales can't stop quoting for a quarter while the migration finishes, so teams delay starting at all rather than risk the disruption.
No visibility before go-live
Most migration approaches don't show what actually changed until it's already live in production — and by then, it's a support ticket.
Revenue recognition drift
Billing schedules moved by hand often shift recognition timing slightly — enough to matter at audit, not enough to notice at migration.
The workarounds most teams are already running
Without a way to migrate logic directly, teams patch together one of these — each buys time, none of them solves it.
Two ways to run your lanes
Watch every lane cross, or let CrossXLane run the full set — both are point-and-click, neither needs a developer.
Click through each lane yourself
CrossXLane opens every lane with a full diff — legacy object on one side, mapped Revenue Cloud object on the other. Click approve, and the lane crosses. Nothing needs a line of Apex.
- Works with any CPQ configuration, standard or heavily customized
- Side-by-side diff for every price rule, bundle, and template
- Flags edge cases instead of guessing at them
Let every lane run itself
Set your cutover window and CrossXLane runs every lane end to end — no manual intervention, no one clicking through each object by hand.
- Runs on your schedule — nights, weekends, or a full change freeze
- Shadow mode compares legacy and Revenue Cloud quotes automatically
- Every lane logged and reversible until you confirm cutover
How a lane crosses
Three clicks between a legacy object and its Revenue Cloud equivalent.
Open the lane
CrossXLane reads your CPQ instance and opens one lane per category — pricing, approvals, bundles, revenue.
Review the mapping
See the legacy object and its Revenue Cloud target side by side, with nothing converted yet.
Click to cross
Approve the lane and it crosses — point and click, with zero manual configuration on your side.
Choose how each lane gets checked
Some teams want a human eye on every lane. Others just want the numbers to match. CrossXLane supports both, per lane.
Shadow Lane
Legacy and Revenue Cloud run in parallel. CrossXLane compares quote totals automatically and flags drift.
Guided Lane
Every lane is queued for a click-through sign-off, with the original object shown alongside the mapping.
Auto Lane
For standard catalogs, lanes cross automatically, with a full audit trail kept for later review.
"Every lane just crossed on its own. We reviewed the pricing lane by hand and let the rest run — cut over on a Friday afternoon."
Every lane you need to cross, mapped before you click a thing.
A lane check takes about 20 minutes and only reads your configuration — nothing is converted or changed.