Service · Three to six weeks · Fixed scope
A Salesforce CPQ migration plan you can hand to a builder
Salesforce CPQ reached end of sale in March 2025. The CPQ Exit Plan tells you what your current setup really does, what should replace it, and how to get there without a quarter of broken quotes.
You know this one
Your CPQ works. It took two years, one consultancy and a great deal of patience to get there. It has 60 price rules, a handful of custom scripts and one product bundle that only Dana in sales ops understands.
Now there’s a line in a release announcement saying it’s no longer being sold, and a renewal conversation on the calendar. Nobody’s forcing you to move this month. But nobody’s adding features to it either, and the question “what’s the plan?” is starting to arrive from above.
What a Salesforce CPQ migration needs before anyone builds anything
Most migrations go wrong for the same reason: nobody wrote down what the old system did. Rules built years ago for a pricing model that’s since changed twice get rebuilt faithfully, bugs and all. Or they get dropped, and you find out which ones mattered when a quote goes out wrong.
The Exit Plan is the step before the build. It answers three questions:
- What do we have? Every product, bundle, rule, script, template and approval, and which ones are still used.
- What do we need? The target design, in Revenue Cloud or an alternative, covering what you sell today.
- How do we get there? Phases, cut-over, what runs in parallel, and how you’ll know it worked.
What you get
- An inventory: products, bundles, price and product rules, custom scripts, quote templates, approvals and integrations, each marked keep, simplify or retire, with usage behind the call.
- A target design: how each kept item maps to the new setup, and where it doesn’t map cleanly.
- An options note: Revenue Cloud, a lighter alternative, or staying put for now, with the trade-offs in plain words. We don’t resell any of them.
- A migration and cut-over plan: phases, data to move, what to test, and a rollback.
- A document template review: what your quote and contract documents need in the new world.
- A read-out for the people who’ll approve and the people who’ll build.
How it runs
- Week 1: inventory. We read the configuration and pull usage: which rules fire, which products get quoted.
- Week 2: the people. Sessions with sales ops, finance and two or three reps. What they rely on. What they work around.
- Weeks 3 to 4: design and options.
- Weeks 5 to 6: plan and read-out. Simpler setups finish in three weeks.
What we need from you
- Read access to the CPQ configuration and a recent sandbox.
- Your sales ops lead for about four hours a week.
- An hour each with finance and a couple of reps.
- Somebody who can decide between options.
What it isn’t
- It isn’t the migration. It’s the plan. The build is separate, and you can take the plan to any partner or your own team.
- It isn’t licensing advice. Commercial terms are between you and your account team.
- It isn’t a recommendation to move now. Sometimes the right answer is “stay, tidy up, and revisit in a year.” If so, the report says that and tells you what to tidy.
Where our apps fit
Two parts of quoting often don’t need a full CPQ: the document and the renewal copy. Purser generates quote and contract documents from a record, with a real preview. Sistership clones a deal for renewal with rules, so last year’s dates don’t come along. Both are optional.
Questions people ask
Is Salesforce CPQ being discontinued?
Salesforce CPQ reached end of sale in March 2025, which means it is no longer sold to new customers. Existing customers continue to be supported. Salesforce’s investment has moved to Revenue Cloud. Check Salesforce’s own announcements and your contract for the dates that apply to you.
Do we have to migrate off Salesforce CPQ right away?
No. End of sale isn’t end of support. But new features are going elsewhere, so it’s worth having a plan and a rough timeline, even if the timeline is “next year.” A plan made calmly is better than one made at renewal.
How long does a CPQ migration take?
It depends almost entirely on how much custom logic you carry over. The planning takes three to six weeks. The build can take anywhere from a couple of months to most of a year. The inventory is what makes the estimate honest, and retiring unused rules is the fastest way to shorten it.
Should we move to Revenue Cloud or something else?
It depends on what you sell and how complicated your pricing is. Revenue Cloud suits teams with complex products and a long Salesforce roadmap. Simpler catalogs sometimes do better with less. The options note lays out both for your case.
What can we do right now, before any migration?
Take stock. List your price rules and find out which have fired in the last year. Count your quote templates. Ask reps what they work around. That costs nothing and makes every later step shorter.
Get the plan before the pressure
Thirty minutes to talk through your setup and whether the Exit Plan fits.