Moving off Siebel to Oracle Fusion CX is not an upgrade, it is a wholesale replacement of your licensing model and your negotiating position. This page quantifies what you leave behind, what you take on, and where the dual-run and conversion traps sit.
Moving off Siebel to Oracle Fusion CX is not an upgrade, it is a wholesale replacement of your licensing model and your negotiating position. This page quantifies what you leave behind, what you take on, and where the dual-run and conversion traps sit.
Read the Siebel-to-Fusion CX move as a change of licensing regime, because that is what it is. Siebel is a perpetual license: you paid once per named user (plus modules), and you pay 22 percent of net license fees every year for support. Oracle Fusion CX is a SaaS subscription: you pay per user or per transaction every month, forever, and support is bundled into that subscription. There is no residual asset when you switch. The perpetual licenses you own do not convert into cloud subscriptions, and Oracle has no contractual obligation to give you credit for them.
The user-counting logic also changes underneath you. Siebel is licensed on an Application User basis, one license per named user with access, and certain modules (Analytics, Marketing, Call Center) are licensed on a Component basis. If you have not modeled how your current count maps, start with our breakdown of the Siebel Application User versus Employee metric before you let Oracle build the target-state subscription for you. Fusion CX bundles roles into broader subscriptions and prices some CX modules on transaction volume, so a straight seat-for-seat translation almost always overshoots.
Your Siebel licenses will not automatically convert into Fusion CX subscriptions. There is no residual asset when you switch, and Oracle owes you no credit for what you already paid.
Oracle has committed to Premier Support for Siebel CRM through at least 2037 under the Continuous Innovation model, and states it will annually review whether to extend that a further year. Note the language: the date rolls forward one year at a time, so it is real but contractually soft rather than a fixed horizon you can build a plan around indefinitely. Either way, the practical point stands. A Siebel customer can keep running with full Premier Support for roughly another decade.
That single fact reshapes the entire negotiation. When Oracle's account team frames Fusion CX as the answer to an end-of-life problem, they are manufacturing urgency you do not have. In 25 years negotiating this vendor, the customers who lose most are the ones who accept the vendor's timeline. If you are not being pushed off Siebel by a technical cliff, you are migrating on your schedule, on your business case, and with the credible option of staying put. Do not surrender that. If support cost is the real driver, the alternative is not always Fusion CX; weigh whether Siebel on third-party support gets you the same annual savings without a re-platform.
Before you can judge whether Fusion CX is cheaper, you have to price the status quo accurately, because Oracle will build the migration business case around whichever number flatters the cloud. Use the late-2024 Siebel list figures as your reference points: a Siebel Base license lists at $3,750 per user, carrying roughly $825 per user in annual support at the standard 22 percent rate.
| Item | List basis | 150-user example (list) | At 50% negotiated discount |
|---|---|---|---|
| Siebel Base license | $3,750 per user | $562,500 | $281,250 |
| Communications Industry license | $400 per user | $63,000 | $31,500 |
| Total license | $625,500 | $312,750 | |
| Annual support (22% of net) | 22% of net license | ~$137,610/yr | ~$68,800/yr |
Two things matter here. First, your negotiated Siebel license is a sunk cost; the number that competes with a Fusion CX subscription is the annual support line, roughly $68,800 per year in the discounted example above. That is the recurring cost you actually eliminate by leaving. Second, that support figure drifts upward. In 2026 the 22 percent is typically repriced annually with a 4 to 8 percent uplift depending on term, unless your contract capped it. So every year the migration slips, the cost of staying rises, but so does the cost of the Fusion subscription you are being sold. Model both trajectories, not just the one Oracle shows you.
One caution on the leaving-side number: make sure the support line you are comparing reflects your true entitlement, not what has crept in. Siebel module sprawl means many customers carry add-on modules they no longer use but still pay support on. Clean those up first. Cancelling unused module support before migration modeling shrinks the baseline and, if you do stay on Siebel, is a legitimate saving in its own right.
Fusion CX Sales is priced per user per month, and the tier ladder is steep. Public tier data puts Professional at $65, Standard at $100, Enterprise at $200 (this is where the AI Sales Predictor and incentive compensation live), and Premium at $300 per user per month. Independent advisory pricing brackets Fusion CX Sales at roughly $125 to $200 per user per month at list. The gap between those sources is the tiering: Oracle steers you toward Enterprise and Premium because that is where the AI functionality and the higher margin sit.
| Fusion CX Sales tier | List per user/mo | Annual per user | What it adds |
|---|---|---|---|
| Professional | $65 | $780 | Core CX, mobile, sales analytics, forecasting |
| Standard | $100 | $1,200 | Outlook integration, territory management |
| Enterprise | $200 | $2,400 | AI Sales Predictor, incentive comp, quote mgmt |
| Premium | $300 | $3,600 | Whitespace analysis, Oracle Voice, enterprise contracts |
Run the comparison honestly. At the Enterprise tier, 150 users cost $360,000 per year at list, more than five times the $68,800 annual Siebel support you were paying in the discounted example. Even at Professional, 150 users at $780 per year each is $117,000 annually, still above your Siebel support baseline. The subscription model trades a one-time capital cost and a modest support line for a permanent, escalating operating cost. That is the core economic truth of this migration, and it is why the negotiated discount matters more than any feature demo.
At the Enterprise tier, 150 Fusion CX users cost $360,000 per year at list. That is more than five times the annual Siebel support you were paying. The subscription model is not automatically cheaper.
The exposure that catches buyers is not the per-user pricing, it is the modules Oracle prices on transaction volume. Fusion CX is not a single metric product. The same Fusion brand covers per-user, per-employee, and per-transaction pricing, and certain CX modules fall into the transaction bucket alongside B2B Order Management, Tax, and Subscription Management. These carry hard caps and ladder pricing, meaning the price per transaction steps up once you breach a tier.
Here is why that is worse than Siebel exposure. In Siebel, Oracle audits your named users, and you control the deployment. In Fusion, Oracle owns the production tenancy and reserves the right to read the transaction count directly from it. The metric definitions are tighter and, critically, more enforceable. Digital Customer Service, for example, is metered by Session (a unique individual accessing through a specific channel), and CX4C subscriber counting is per unique subscriber regardless of how many services they use. You must model these definitions against your real volumes before you sign, because once you are live, Oracle reads the meter and you argue after the fact. This is a different discipline from Siebel audit defense, where you build the evidence pack that caps exposure from data you control.
No large Siebel estate migrates to Fusion CX in a single cutover. You run both in parallel through phased rollout, data conversion, and integration rework. That means you pay Siebel Premier Support (22 percent, escalating) and the Fusion CX subscription simultaneously, often for 12 to 24 months on a realistic enterprise timeline. In our experience across Oracle re-platforming projects (this is market experience, not a published Oracle figure), dual-run cost is the single most underestimated line in the business case, and Oracle's own migration models routinely omit or understate it.
The remedy is contractual, not technical. A subscription that ramps in step with your rollout, plus a Siebel support term that ends when the last workload moves, is the difference between a controlled transition and paying full freight for two platforms at once.
The Fusion CX list prices above are opening positions, not landing prices. Enterprise customers who bring a defensible deployment forecast and a credible competitive alternative to the table land realized pricing 35 to 55 percent below list, with price-protection clauses extending through year five. The negotiated landing is the number your business case should use, and the year-five protection matters as much as the year-one discount, because Oracle's default renewal posture is to reset toward list once you are committed and switching costs are high.
Watch the bundle. Oracle will offer to consolidate CX into a multi-pillar Fusion deal alongside ERP or HCM, dangling a larger aggregate discount. Model it carefully, because the bundle discount is frequently worth less than the negotiating power you surrender by putting everything into one deal with one renewal date and one vendor lock. Keep CX negotiable on its own terms wherever you can. The competitive alternative you name (Salesforce, Microsoft, or staying on Siebel) is the lever that actually moves Oracle, and a bundle dilutes that leverage across pillars where your alternatives are weaker.
A 35 to 55 percent discount below list is achievable, but only with a defensible forecast and a named competitive alternative. Without both, you pay list dressed up as a discount.
Sequence the decision so you never negotiate from weakness. First, establish that you have a decade of Siebel support and that migration is your choice, not a deadline. Second, clean up the Siebel baseline (retire unused modules, confirm your true user count, cap support increases if the contract allows) so the number you compare against is honest. For the counting mechanics, start from our Siebel CRM licensing buyer guide and the treatment of contractors and external users, which are the two areas that most often inflate a target-state Fusion count.
Third, model the Fusion CX target state on your real user profile and transaction volumes, at the tier you actually need rather than the tier Oracle steers you to, and add a fully costed dual-run period. Fourth, name a competitive alternative and keep CX separable from any broader Fusion bundle. Fifth, hold out for year-five price protection and a subscription ramp tied to rollout. If the migration business case only works at list-versus-list or ignores dual-run, it does not work, and the right answer may be to stay on Siebel or move it to third-party support. The re-platforming pattern here rhymes with the SAP world; if you want the parallel framework, our note on negotiating SAP S/4HANA conversions shows how migration credits and ramp terms get structured buyer-side.
No. Siebel licenses do not automatically convert, and Oracle has no contractual obligation to credit your perpetual investment against a Fusion CX subscription. The perpetual license and its 22 percent support line are, economically, a sunk asset. Any credit you receive is a negotiated concession you have to fight for, not an entitlement.
No. Oracle has committed to Premier Support for Siebel CRM through at least 2037 under the Continuous Innovation model, and reviews annually whether to extend a further year. You can run Siebel with full support for roughly another decade, so any migration is your commercial choice rather than a technical necessity. That absence of a deadline is your strongest negotiating lever.
Not automatically. The fair comparison is your annual Siebel support cost (often well under $100,000 for a mid-sized estate) against the Fusion CX subscription, which at the Enterprise tier runs $2,400 per user per year at list. In many cases the subscription is more expensive on an ongoing basis. Whether it is cheaper depends entirely on the tier you buy and the discount you negotiate.
Dual-run. Most enterprises pay Siebel Premier Support and the Fusion CX subscription simultaneously for 12 to 24 months during phased cutover, and Oracle's business case routinely understates this. Mitigate it by negotiating a subscription ramp tied to actual user migration and co-terming your Siebel support end date to the final cutover.
In Siebel you control the deployment and Oracle audits named users. In Fusion, Oracle owns the production tenancy and reads the transaction count directly, so metrics like DCS Sessions and CX4C subscribers are far more enforceable. Model these definitions against real volumes before signing, because after go-live Oracle reads the meter and you argue after the fact.
Enterprise buyers with a defensible deployment forecast and a named competitive alternative land 35 to 55 percent below list, with price protection extending through year five. Without both a forecast and a credible alternative, you will pay close to list dressed up as a discount. The year-five protection is as important as the year-one price.
Oracle prices Fusion ERP Cloud per employee, not per user, which inflates true cost. The buyer side guide to module economics and the modernization discount.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
