How to Migrate Off Salesforce CPQ: The Complete Playbook

How to Migrate Off Salesforce CPQ: The Complete Playbook

Migrating off Salesforce CPQ means re-implementing your quoting logic on a new platform — there is no lift-and-shift. Whether you're moving to Salesforce's successor (Agentforce Revenue Management) or a third-party CPQ, your price rules, product rules, approval chains, and quote templates get rebuilt, not copied. The good news: done right, the rebuild is smaller than you fear, because most teams use far less of CPQ than they configured.

With Salesforce CPQ in maintenance mode — end-of-sale since March 2025, most documentation removed in July 2026 — more teams are planning this move deliberately rather than waiting for a forcing event. This playbook covers when to move, how to scope it, how to pick a destination, the six steps of the migration itself, and the mistakes that stretch a six-week project into six months. It also covers where Kugamon fits as a Salesforce-native destination.

When to Move (and When to Wait)

Move sooner if: your CPQ admin is a single point of failure, quoting workarounds are multiplying, you're paying for modules you don't use, or a renewal is coming and you want negotiating room. Wait if: quoting is stable, your team is mid-fiscal-year crunch, or you haven't inventoried what you actually use yet. Renewal-minus-6-months is the ideal evaluation window — you keep the option to renew on your terms. (Context: Can You Still Renew Salesforce CPQ?)

Step Zero: Inventory What You Actually Use

Practitioners regularly discover they use only a fraction of the CPQ features they originally configured. Before evaluating anything, list: active price rules, product rules, discount schedules, approval chains, quote templates, and integrations — then mark which ones fired in the last 90 days. That 90-day list is your real requirements document, and it's usually dramatically shorter than your configuration.

Choosing a Destination

The one question that sorts the field fastest: "Where does my quote data physically live, and can I run a native Salesforce report on it without exporting?" Our CPQ evaluation guide covers the full criteria list.

The Six-Step Migration

1. Freeze and document (Week 0)

Export your CPQ configuration and quote history. Archive the consolidated documentation PDF. Screenshot working templates. This is your rollback insurance and your build reference.

2. Map the 90-day feature list to the new platform (Week 1)

For each active rule and workflow, identify the equivalent in the destination. Anything without an equivalent goes into a decision log: rebuild differently, simplify, or drop.

3. Rebuild the catalog and pricing (Weeks 1–3)

On a native platform this is the light step — your Products and Price Books already live in Salesforce and carry over. On ARM or an external tool, this is where the project cost concentrates.

4. Rebuild quoting flows and templates (Weeks 2–5)

Quote layouts, approval chains, discount guardrails, e-signature. Rebuild from the 90-day list, not from the old configuration — this is your chance to drop accumulated complexity.

5. Parallel-run on live deals (Weeks 4–6)

Run 10–20 real quotes through both systems. Compare outputs line by line. Fix gaps while the old system is still your system of record.

6. Cut over and retire (Weeks 6–8)

Switch the default quoting path, keep CPQ read-only for history through your renewal date, and retrain the team on the five workflows they touch daily.

Common Mistakes

• Migrating the configuration instead of the requirement. Rebuilding every legacy rule recreates your technical debt on a new platform.
• Skipping the parallel run. The first month of side-by-side quotes catches pricing edge cases no test plan finds.
• Underestimating template work. Quote documents are where "quick" projects stall; scope them explicitly.
• Letting quote history block the move. You rarely need old quotes in the new tool — you need them queryable. Read-only access or an export usually suffices.
• Signing a long renewal mid-evaluation. Keep terms short while you decide.

What It Costs

Destination license plus implementation. As a benchmark: Kugamon publishes pricing from $65 per user per month for Mid-Market CPQ, with implementation typically ¼–⅓ of annual licensing and admin-led delivery. ARM runs $200 per user per month with re-implementation projects commonly estimated at $100K–$500K. The calculator at transition.kugamon.com models your seat count across the options — including tailored migration paths from Salesforce CPQ, Conga, and DealHub.

Frequently Asked Questions

Q: How long does a Salesforce CPQ migration take?

To a Salesforce-native platform like Kugamon, 4–8 weeks is typical because the product catalog stays in native Salesforce objects. To ARM or an external CPQ, plan for months — the catalog and pricing model are rebuilt.

Q: Can I export my quote history from Salesforce CPQ?

Yes — quotes and lines are Salesforce records and export normally. Most teams keep CPQ read-only for history instead of importing old quotes into the new tool.

Q: Do my Products and Price Books carry over?

To a native platform, yes — Kugamon uses Salesforce's own Product and Price Book objects, so your catalog stays put. External tools and ARM use their own models, which means catalog rebuild work.

Q: Should we migrate to ARM since it's Salesforce's successor?

Only if the enterprise suite justifies the price and project. ARM is $200 per user per month with no automated migration from CPQ; it's a rebuild either way, so evaluate it against alternatives on equal terms.

Q: What's the biggest risk in a CPQ migration?

Rebuilding legacy complexity nobody uses. Inventory the rules that actually fired in the last 90 days and rebuild only those. The second biggest: skipping the parallel run.

Q: Do we need a consulting partner?

For ARM or external platforms, usually yes. For admin-first native packages, most teams self-implement — Kugamon deployments are typically led by the customer's own Salesforce admin with vendor support.

Q: When is the best time to start?

About six months before your CPQ renewal. You'll finish the evaluation with time to either migrate calmly or renew on stronger terms.

Next Steps

Start with the 90-day feature inventory this week — it's two hours of work and it reframes the whole project. Then compare destinations on transition.kugamon.com, explore Kugamon CPQ, or schedule a demo to see what a native migration looks like on your own data. No pitch — just honest guidance.