What's happening to Salesforce CPQ?
Salesforce moved CPQ to End-of-Sale in March 2025. Since then, European mid-market CROs and CTOs ask us the same questions. When does Salesforce CPQ reach end of life? What happens if I wait until 2029? Salesforce CPQ versus Revenue Cloud: what is the difference? Find all your answers below. No vendor spin.
When does Salesforce CPQ reach end of life?
No official End-of-Life date exists yet. A formal announcement is widely expected in 2027-2028, with support ending around 2029-2030. Treat those as projections, not Salesforce commitments.
End-of-Sale happened in March 2025. No new licenses are sold. Existing customers renew and receive support. Engineering moved to Revenue Cloud, so support response slows over time.
Do I need to migrate now?
Not immediately but start your evaluation now.
A Revenue Cloud migration runs 18-24 months, per Salesforce's documentation. Evaluation runs 6-12 months. Start in 2026 and you finish before the expected End-of-Life window, with vendor leverage intact. Start in 2028 and you move under deadline pressure.
What happens if I wait until 2029?
You migrate under a forced deadline. Implementation partners run scarce because every CPQ customer moves at once. Your negotiating position weakens. Costs rise. Compressed timelines raise the risk of a failed project.
Your CPQ keeps running past 2030 until something breaks. After support ends, no security patches and no bug fixes.
Salesforce CPQ versus Revenue Cloud: what is the difference?
Revenue Cloud is a complete platform rebuild, not an upgrade.
New capabilities: AI-assisted quoting, native billing, a unified revenue lifecycle, subscription management.
The trade-off: higher licensing and a full platform rebuild. Salesforce documents an 18-24 month timeline. Whether the new capabilities earn that cost depends on how much of the Salesforce platform you use.
What should I do this quarter?
Weeks 1-2: Document your CPQ customisations, integrations, and which teams depend on CPQ data beyond sales.
Weeks 3-8: Request proposals from Salesforce, HubSpot-based alternatives, and third-party CPQ vendors. Require a proof of concept with your real data.
Weeks 9-12: Present the comparison to executive leadership. Begin contract negotiations.
What is a realistic Salesforce CPQ migration cost?
Salesforce publishes baseline figures of $300K-750K implementation plus a 30-100% licensing increase. Treat these numbers as a floor, not a forecast.
The published number leaves out the costs that drive overruns: integration rebuilds across ERP, billing, and contracts, internal team time, productivity loss during transition, and parallel operation. Build your budget from your own integration map, not the headline figure. The real total runs well above the published services range.
Can I negotiate better Revenue Cloud pricing?
Yes, if you commit early. Salesforce wants reference customers in 2026-2027, so early commitments carry more leverage. That leverage weakens as the deadline approaches.
Are there cheaper alternatives to Revenue Cloud?
Yes:
Whether an alternative fits depends on your integration architecture.
Want a cost comparison for your situation? [Schedule assessment].
What Salesforce CPQ alternatives exist?
Is Revenue Cloud migration an upgrade or a rebuild?
A complete rebuild. Nothing transfers automatically. Per Salesforce's documentation, basic data moves automatically, pricing rules and configurations move semi-automatically, and custom logic needs manual redesign. The effort matches migrating to any alternative platform.
How long does a Revenue Cloud migration take?
Salesforce publishes an 18-24 month timeline. With integration rebuilds, testing, and user adoption, real projects run longer. Plan in phases: assessment, configuration, migration, deployment, then full adoption over two to three months.
Should I stay with Salesforce or switch platforms?
Stay with Revenue Cloud if you use Service Cloud and Marketing Cloud heavily, need unified billing, and your budget supports the licensing increase.
Switch platforms if you use mainly Sales Cloud, run complex SAP or ERP integrations, want platform independence, or your team struggles with Salesforce complexity.
What is the risk of leaving Salesforce entirely?
Execution complexity. Changing CRM and CPQ at once is harder than changing CPQ alone. If you run heavy Service Cloud or custom apps, switching costs rise.
The trade-off: you exit the forced-migration cycle. CPQ today. Which product next?
Want an honest read on your best path? [Schedule a 60-minute evaluation]
What breaks when I migrate CPQ?
Every integration point: ERP product and order data, billing, contract management, document generation, and CRM connections. Revenue Cloud uses different APIs, so each integration needs rebuilding.
How complex is a Salesforce CPQ to SAP integration?
Significant. Revenue Cloud's APIs differ from CPQ's managed-package APIs. You rebuild product master data sync, pricing procedure connections, order handoff workflows, and configuration data flows. Map this complexity before you commit to any path.
What happens to my AppExchange integrations?
Many CPQ-specific apps do not support Revenue Cloud. Document every app and verify compatibility before committing. This hidden cost gets missed during evaluation.
Can I migrate in phases?
Yes, by product line, region, or user group. Phasing lowers risk and extends the timeline, and you run two systems in parallel during cutover.
When should I hire an implementation partner?
CPQ migrations fail most often when companies underestimate integration complexity, rush the timeline, or skip change management.
Hire a partner if you have complex SAP or ERP integrations, heavy CPQ customisation, no internal bandwidth for a multi-year project, or you need specialised integration expertise.
Run it internally if your configuration is standard, you have experienced architects on staff, your integrations are simple, and you have dedicated resources for the full timeline.
How do I choose between Salesforce consultants and alternatives?
Salesforce consultants carry quota pressure for Revenue Cloud, so their proposals favour Revenue Cloud. Platform-agnostic consultants implement the alternative when it fits better. The question to ask: who benefits financially from which recommendation?
Why work with Elixir on CPQ migrations?
We sit at the intersection of HubSpot expertise and SAP integration depth. We are one of the few HubSpot Elite Partners in Europe with certified SAP integration architects. Most HubSpot partners understand CRM. Few understand ERP integration complexity.
We implement HubSpot with specialised CPQ when it fits your architecture. We tell you directly when Revenue Cloud is the stronger choice despite the higher cost. We optimise the recommendation to prevent expensive mistakes, not to win the deal.
What does your assessment include?
It covers integration architecture mapping across CRM, CPQ, ERP, billing, and contracts. A clear evaluation of all three options for your situation, a five-year cost framework, and a written recommendation for executive leadership.
You get a decision framework specific to your needs.