When should we migrate from Salesforce CPQ to Revenue Cloud?

It depends on timing pressure (renewal date, new pricing models, AI plans) and on how complex your setup is. If both are high, start planning now. If neither is, you have time, but use it to clean up rather than add more to CPQ.

Is it risky to wait to migrate from CPQ?

Waiting is fine if your setup is simple and nothing in your business is changing. The risk grows if your setup is complex, because the closer you get to end of life, the less control you have over timing, cost and who's available to do the work.

Should we wait for Salesforce's CPQ migration assistant?

Only if you've already decided on Revenue Cloud and your timing allows it. The assistant is a roadmap item targeted for December 2026, so check what it actually covers once it ships. It can help move data and configuration, but it won't decide how to redesign your pricing, rules and renewals, and it won't clean up your org for you. The prep work in this checklist is worth doing either way.

What should we do first to prepare for a CPQ migration?

Find out who actually builds quotes, retire unused products and rules, document how your pricing works, and list every integration and piece of code that touches CPQ objects.

CPQ Migration Readiness Checklist: Should You Move to Revenue Cloud Now?

This CPQ migration readiness checklist takes two minutes. Tick what applies to your org and get an instant recommendation: start now, plan for your renewal, clean up first, or wait.

How to use this: the checklist has three parts. Timing tells you how soon you should move. Complexity tells you how big the move is. Readiness tells you what to sort out before you start. Your answers stay in your browser. Nothing is sent anywhere.

The most common question we get from CPQ owners isn't "how do we migrate?" It's "do we need to do this now?" And with Salesforce's CPQ migration assistant on the roadmap for December 2026, many are also asking whether to wait for it. The honest answer depends on two things: how much pressure you're under, and how big your migration is. This checklist puts both on one page.

1. Timing

How much pressure is there to move soon?

Our Salesforce renewal is within the next 12 monthsYour renewal is the best moment to decide on licenses. We're planning new pricing models (usage-based, new bundles, new markets)Building these on CPQ means building them twice. We want AI in our quoting or renewals (Agentforce)New capabilities are going into Revenue Cloud, not CPQ. We're growing the sales team fastYou can still add CPQ users, but every new seat is one more to move later. Our CPQ admin or main CPQ developer has left, or mightCPQ skills are getting harder to hire for. CPQ performance or quote calculation speed is a regular complaint

2. Complexity

How big is the job? Not sure? The queries in our CPQ end of sale guide will tell you in 10 minutes.

We have more than 50 active price rules and product rules combined We use a Quote Calculator Plugin (custom script)Usually the hardest part to rebuild. We have custom Apex triggers, flows or LWCs on CPQ objects CPQ is integrated with an ERP, billing or other external system We handle lots of amendments, co-terming or mid-term upgrades We sell in multiple currencies or regions with different pricing We use Advanced Approvals with several approval chains We have more than a few quote templates

3. Readiness

Tick what's already true. Anything left unticked becomes your to-do list.

We know who actually builds quotes, not just who has a license We've cleaned up unused products, bundles and rules Our pricing logic is documented somewhere other than in CPQ itself We have a list of all code and integrations that touch CPQ There's a clear business owner for the migration We have a rough budget in mind

Your result

Tick the boxes above to see your recommendation

Your result updates as you go.

Timing pressure: Low

Migration size: Small

What each result means

Start planning now

High timing pressure and a large migration is the combination that turns into a rushed, expensive project if you wait. Get an assessment done this quarter, so you go into your renewal knowing the scope, the licenses you need and a realistic timeline.

Plan around your renewal

You have a reason to move soon, but the job itself is manageable. A focused project timed around your renewal works well here. Use the assessment to confirm the scope and right-size your licenses before you sign.

Clean up first, then plan

There's no rush, but your setup is complex. That's the best possible position: you have time to simplify before anything is rebuilt. Retire unused rules and products, document your pricing, and plan a proper assessment in the next 6 to 12 months.

You have time

A simple setup with no pressure to move. Don't start a migration just because everyone is talking about it. Do a light cleanup, avoid adding new complexity to CPQ, and check again at your next planning cycle.

Got your result? Bring it to a 30-minute CPQ review, and we'll tell you whether it holds up once we look at your actual org.

Book a CPQ review

Keep reading

Common questions

Want a second opinion on your result?

Book a 30-minute CPQ review with our architect. We'll look at your setup and give you an honest view of the timing, size and cost of your move.

Book your CPQ review