Short answer: Siebel end of life is commercial, not technical. Oracle still ships Siebel CRM updates under Applications Unlimited, so the product is not discontinued — but older releases move into Sustaining Support, the lowest tier of the Lifetime Support Policy, where you keep existing patches and pay the full 22% fee while losing new fixes, security patches, and certifications. The cost-cutting moves are third-party support or a planned migration.
Key Takeaways
- Siebel is not discontinued — Oracle continues to release Siebel CRM updates under its Applications Unlimited commitment, so the end-of-life pressure is commercial steering toward Fusion CX, not a technical kill date.
- Sustaining Support is the lowest of Oracle's three Lifetime Support tiers: you keep existing patches but get no new fixes, no new security patches, and no new certifications.
- Sustaining Support costs the same as Premier Support — roughly 22% of net licence value per year — for far less service, which is the core reason Siebel customers leave it (Oracle Licensing Experts, 2026).
- Third-party support typically cuts the annual Siebel support fee by around 50% while still covering break-fix, tax and regulatory updates, and security advisories.
- A stable, mature Siebel deployment can run safely for years off Oracle support — the decision is a risk-and-cost calculation, not a forced migration.
What This Guide Covers
Is Siebel CRM end of life in 2026?
Short answer: No — Siebel CRM is not end of life in 2026. Oracle continues to ship Siebel CRM 25.x releases under its Applications Unlimited commitment, which pledges continued development for legacy applications. The end-of-life pressure is commercial: Oracle steers Siebel customers toward Fusion CX, and that sales agenda, not a technical deadline, is what drives most "Siebel is dying" conversations.
The phrase "Siebel end of life" is used loosely, and the confusion is profitable for Oracle. Siebel CRM is an actively maintained product: under Oracle's Applications Unlimited commitment — Oracle's pledge to keep developing its acquired application lines including Siebel, PeopleSoft, JD Edwards, and E-Business Suite — Siebel continues to receive feature updates and innovation packs. So no version with current updates is "dead" in any technical sense.
What is real is the commercial pressure. Oracle's strategic priority is Fusion Cloud CX, and its account teams consistently frame Siebel as legacy to accelerate migration deals. The "end of life" narrative is part of Oracle's playbook: create urgency, then sell the cloud transition. Your job as a buyer is to separate the genuine support-lifecycle facts from the sales pressure — which means understanding exactly where each of your Siebel releases sits in the Lifetime Support Policy. This page sits within our broader Oracle Siebel Licensing Guide, which covers modules, metrics, and migration alongside support.
How does Oracle's Lifetime Support Policy apply to Siebel?
Short answer: Oracle's Lifetime Support Policy has three phases — Premier Support, Extended Support, and Sustaining Support. Siebel releases pass through them by version. Premier Support gives full service for a defined window; Extended Support adds limited time at a premium; Sustaining Support is indefinite but stripped down. Where your version sits dictates your real cost and risk.
The Oracle Lifetime Support Policy is the framework that actually governs Siebel's lifecycle, and it has three tiers. Premier Support is the full-service phase: new fixes, security updates, certifications, and tax and regulatory updates, normally for a defined number of years from a release's general availability. Extended Support is an optional, time-limited extension — often carrying a fee uplift — that continues most Premier services for a few additional years. Sustaining Support is the open-ended final phase: you retain access to what already exists but receive nothing new.
For Siebel, the practical point is that these phases attach to versions, not to the product as a whole. An older Siebel release may already be in Sustaining Support while a current release sits in Premier Support. So the first diagnostic question is always "which Siebel version are we running, and what phase is it in?" — because that single fact determines whether you are paying full price for full service or full price for a fraction of it. We map this for clients in our Compliance Review.
| Support tier | New fixes & security patches | New certifications | Tax/regulatory updates | Typical annual fee |
|---|---|---|---|---|
| Premier Support | Yes | Yes | Yes | ~22% of net licence value |
| Extended Support | Yes (limited) | Limited | Yes | ~22% + uplift |
| Sustaining Support | No new fixes | No | No | ~22% of net licence value |
| Third-party support | Break-fix + security advisories | Provider-dependent | Yes (provider-delivered) | ~50% less than Oracle |
What is Sustaining Support — and what does it cost?
Short answer: Sustaining Support is the lowest tier of Oracle's Lifetime Support Policy. You keep access to existing patches, fixes, and documentation, but get no new updates, no new security fixes, and no new certifications — and you still pay the full support fee, roughly 22% of net licence value, the same as Premier Support. It is full price for materially reduced service.
Sustaining Support is the tier Oracle would prefer you not examine closely, because its economics are indefensible from a buyer's seat. Definitionally: Sustaining Support is indefinite Oracle support that preserves your access to pre-existing patches, updates, fixes, and documentation, but excludes any new patches, new security alerts, new certifications with newer platforms or browsers, and new tax, legal, or regulatory updates. Severity-1 service degrades, too — you lose the 24/7 guaranteed response of Premier Support.
The decisive fact is the price. Sustaining Support is not a discount tier — it costs the same as Premier Support, roughly 22% of net licence value annually, while delivering far less. You pay the identical fee for a frozen product. This is why, across our Siebel engagements, the customers most ready to act are those who discover they have been on Sustaining Support for years without realising the service had been hollowed out (Oracle Licensing Experts, 2026). Once a Siebel release is in Sustaining Support and your deployment is stable, continuing to pay Oracle the full fee delivers little that a third-party provider cannot deliver for around half the cost.
Insider note: Oracle counts on inertia. Sustaining Support auto-renews at the same fee, and most customers never re-examine what they are actually receiving. The moment a Siebel version drops into Sustaining Support is the moment to challenge the renewal — not a year later.
Our Support Reduction service confirms which support tier each Siebel release sits in and models the savings from third-party support before your next renewal.
What are your options at Siebel end of premier support?
Short answer: Three realistic paths exist. Stay on Oracle Sustaining Support and accept reduced service at full price; move to third-party support and cut the annual fee by roughly 50% while keeping Siebel running; or migrate to a modern CRM such as Fusion CX or Salesforce. The right path depends on your deployment's stability and your regulatory and integration demands.
When a Siebel release leaves Premier Support, you face a genuine fork with three defensible options, and the choice is a buyer-side calculation rather than a foregone conclusion. Stay on Oracle Sustaining Support if you value Oracle as the single point of contact and accept paying full price for a frozen product — the least economical option, but the simplest. Move to third-party support if your Siebel deployment is stable and you want to cut the support bill by roughly half while retaining break-fix, security, and regulatory coverage — the option most aligned with a settled estate. Migrate if Siebel no longer fits your business — to Oracle Fusion CX or to a competitor such as Salesforce.
Each path has a different risk profile. Third-party support carries minimal technical risk for a mature deployment but means leaving Oracle's update stream. Migration is the highest-cost, highest-disruption path but resolves the legacy question permanently. Staying on Sustaining Support is the lowest-effort, highest-waste path. We model all three with hard numbers in any engagement, because the worst outcome is drifting on Sustaining Support by default. For the migration route specifically, see Siebel to Salesforce migration, and for the third-party route, our support cost reduction guide.
Can you run Siebel safely without Oracle support?
Short answer: Yes. A stable, mature Siebel deployment can run for years on third-party support or self-support, because Siebel is a settled product with few mandatory updates. The real risks are unpatched security exposure, platform certification gaps, and regulatory change — all of which reputable third-party providers cover through break-fix, tax and regulatory updates, and security advisories at roughly half Oracle's fee.
The fear Oracle relies on is that leaving Oracle support means running unsupported, exposed software. For a mature Siebel estate, that fear is overstated. Siebel is a stable, decades-old application; once your customisations are settled and your integrations are working, the volume of genuinely necessary Oracle-only updates is small. The practical question is not "can it run without Oracle" — it demonstrably can — but "which risks must a replacement support model cover?"
Three risks matter. Security: unpatched vulnerabilities in Siebel or its stack — covered by third-party providers' security advisories and virtual-patching guidance. Certification: running Siebel on newer database, browser, or OS versions Oracle no longer certifies — manageable with provider testing and a controlled platform strategy. Regulatory: tax, legal, and statutory updates — delivered directly by reputable third-party providers. Reputable providers such as the established third-party support firms cover all three, which is why leaving Oracle support is a measured risk decision, not a leap. Our independent, buyer-side view weighs these risks against your specific deployment; see our Third-Party Support service.
How to plan your Siebel end-of-life strategy
Short answer: Confirm which support tier each Siebel release sits in, assess deployment stability and regulatory exposure, model the three paths with hard numbers, and time any support change to your renewal date. Decide deliberately — the costliest Siebel outcome is paying full Oracle Sustaining Support by default while the product sits frozen.
A defensible Siebel end-of-life strategy follows a clear sequence. Start by establishing the facts: which Siebel version are you on, and what Lifetime Support phase is it in? Then assess your deployment — how stable are the customisations, how active is development, what regulatory and integration demands sit ahead? With those facts, model the three paths side by side: Oracle Sustaining Support, third-party support, and migration, each with a five-year cost and risk profile. Only then choose, and time the move to your support renewal so you do not pay for an overlapping period.
The discipline that protects you is treating the renewal as a decision point rather than an auto-renew. Oracle's economics depend on Siebel customers drifting on Sustaining Support without re-examining the value. A documented decision — even a decision to stay — beats inertia, and for most stable Siebel estates the numbers favour third-party support decisively. This planning is the core of our Support Reduction and negotiation work. For results, see how we cut support cost in our insurance third-party support case study.
Siebel End of Life FAQ
Is Siebel CRM end of life in 2026?
Siebel CRM is not dead, but it is mature: Oracle continues to ship Siebel CRM 25.x updates under its Applications Unlimited commitment, so the product is still developed. The practical end-of-life pressure is commercial, not technical — Oracle steers Siebel customers toward Fusion CX, and many releases have moved from Premier Support into limited support phases, raising the cost and risk of staying put.
What is Oracle Sustaining Support for Siebel?
Sustaining Support is the lowest tier of Oracle's Lifetime Support Policy. Under Sustaining Support you keep access to existing patches, fixes, and documentation, but Oracle provides no new updates, no new security fixes, no new certifications, and no guaranteed support for new regulatory changes. You still pay the full support fee — roughly 22% of net licence value — for materially reduced service.
Does Sustaining Support cost less than Premier Support?
No. This is the most misunderstood point in Oracle's Lifetime Support Policy: Sustaining Support costs the same as Premier Support — roughly 22% of net licence value per year — but delivers far less. You lose new fixes, security patches, and certifications while paying the same fee, which is precisely why many Siebel customers on Sustaining Support move to third-party support to cut the bill by around 50%.
What are my options when Siebel reaches end of premier support?
Three realistic paths exist. Stay on Oracle Sustaining Support and accept reduced service at full price; move to third-party support and cut the annual fee by roughly 50% while keeping the system running; or migrate to a modern CRM such as Oracle Fusion CX or Salesforce. The right choice depends on how stable your Siebel deployment is and whether you face new regulatory or integration demands.
Can I run Siebel safely without Oracle support?
Yes. A stable, mature Siebel deployment can run for years on third-party support or self-support, because Siebel is a settled product with few mandatory updates. The real risks are security exposure on unpatched components, database and platform certification gaps, and regulatory change. Third-party providers cover break-fix, tax and regulatory updates, and security advisories, which closes most of the gap at roughly half Oracle's fee.
Does moving Siebel to third-party support void my licences?
No. You own your Siebel perpetual licences regardless of who provides support — leaving Oracle support does not affect your right to run the software you have licensed. What you lose is access to new Oracle patches and the right to download new versions. For a stable deployment that is not upgrading, that trade-off is exactly why third-party support cuts cost without operational disruption.
If I leave Oracle support, can I go back later?
You can return to Oracle support, but Oracle typically charges reinstatement fees — back-support for the lapsed period plus a penalty — which can erase the savings. This is why the decision should be deliberate and the deployment genuinely stable before you leave. Plan the move as a multi-year commitment, not an experiment, and document the cost case before your renewal date.
Stop paying full price for frozen Siebel support
We confirm which support tier each Siebel release sits in, model Oracle vs third-party vs migration with hard numbers, and time the move to your renewal. Independent, buyer-side, 600+ engagements.