How Redress Compliance helped Roche transition Oracle Siebel CRM support to a third-party provider — saving $500K annually ($1.5M over 3 years) while maintaining full compliance in a highly regulated pharmaceutical environment.
Roche, a global pharmaceutical and diagnostics leader headquartered in Switzerland, employs over 100,000 people across more than 100 countries. Known for pioneering work in cancer treatments, biotechnology, and data-driven diagnostics, Roche operates a complex and highly regulated IT landscape supporting R&D, commercial operations, supply chain, and customer engagement.
One legacy application embedded in Roche's commercial operations was Oracle Siebel CRM. While still operational in some business units, Siebel had become a low-change, stable system with no major upgrades or customisation planned. Despite the platform's diminished strategic importance, Roche was still paying Oracle's full annual support — nearly $500,000 per year.
Roche engaged Redress Compliance to explore options for optimising Siebel-related spend without risking compliance or operational continuity.
Roche's challenge was clear: maintain Siebel for the short to mid-term, but stop paying premium Oracle support for a legacy platform at steady state.
| Challenge | Detail | Impact |
|---|---|---|
| High Support Cost, Declining Value | Annual Siebel support exceeded $475K; no critical support requests or major patches in 2+ years | Paying premium fees for a service that was rarely used |
| Oracle's "All or Nothing" Stance | Oracle refused to decouple Siebel support or reduce price — full entitlement coverage declared non-negotiable | No vendor flexibility without committing to new cloud deals |
| Audit & Compliance Concerns | Any transition had to be fully defensible, risk-managed, and compliant with licensing terms | Pharmaceutical regulatory requirements (GxP, audit trail) added complexity |
| Complex Alternatives Landscape | Oracle negotiations, licensing review, legal scrutiny, unfamiliarity with third-party models | Internal teams needed specialist guidance to untangle options |
| Stakeholder Hesitance | Business units demanded assurance that service quality and system reliability would not suffer | Risk-averse culture required rigorous proof before any change |
Redress Compliance launched a focused engagement covering licensing assessment, Oracle negotiation, third-party evaluation, and transition planning:
Phase 1 — Licence and Deployment Optimisation: Redress conducted a full licensing assessment across Roche's Siebel deployment, mapping modules and usage by region and business unit, verifying entitlement coverage against active deployments, and identifying inactive components still under support billing. This analysis revealed several modules no longer in active use yet still contributing to the support cost base.
Phase 2 — Oracle Negotiation Support: Redress reviewed Oracle contracts and advised on levers to request price reductions or carve-outs. They prepared commercial positioning to challenge Oracle's "all or nothing" support stance and benchmarked fair pricing against industry norms. Despite several negotiation rounds, Oracle declined to reduce Siebel support fees unless Roche committed to new cloud deals — an approach Redress flagged as vendor lock-in.
Phase 3 — Third-Party Support Evaluation: Redress introduced third-party support as a viable, low-risk option for Siebel. They facilitated detailed technical and commercial due diligence comparing cost savings potential, security patching and compliance capabilities, SLAs and responsiveness, and pharmaceutical industry experience and regulatory readiness. Working with Roche's legal, IT, and procurement teams, Redress ensured the chosen provider met GxP, audit trail, and security requirements.
Phase 4 — Transition Planning and Compliance Safeguards: Redress supported the entire transition including documentation of licence entitlements and deployment history, risk mitigation planning for future Oracle scrutiny, internal communication and change management, and operational alignment with validation and QA processes.
The engagement delivered immediate and long-term benefits for Roche:
| Metric | Result |
|---|---|
| Annual Savings | $500,000 per year |
| 3-Year Total Savings | $1,500,000 |
| Compliance Status | Zero audit or compliance issues — strong entitlement records and controlled transition |
| Support Quality | Seamless continuity — equal or better responsiveness from new provider |
| Oracle Lock-In Avoided | Preserved Roche's ability to negotiate future Oracle services independently |
| Licence Ownership | Full ownership of Siebel licences retained — migration/decommissioning on Roche's timeline |
| Reusable Playbook | Created a framework applicable to other legacy systems facing similar cost/value imbalance |
Importantly, the engagement created a repeatable playbook that Roche can apply to other legacy Oracle systems — any stable, low-change platform where Oracle support costs outweigh the value received.
"Redress Compliance helped us see beyond Oracle's one-size-fits-all support model. They provided us with the data, options, and confidence to make a more informed decision for our legacy platform. The transition to third-party support was smooth, fully compliant, and resulted in a $1.5 million savings without compromising service. It was a clear win."
— Director of IT Procurement, Roche Pharmaceuticals
This engagement highlights strategies applicable to any regulated enterprise paying Oracle support on stable legacy systems:
Legacy systems on steady state are prime candidates. If a system hasn't required critical patches, major upgrades, or significant support requests in 1–2+ years, you're paying for Oracle support capacity you don't consume. Siebel, E-Business Suite, PeopleSoft, and stable database environments are common targets.
Oracle's "all or nothing" stance is a negotiation tactic, not a rule. Oracle will refuse to reduce or decouple support and attempt to tie concessions to new cloud purchases. Independent advisory helps you see through this positioning and evaluate alternatives without vendor pressure.
Third-party support is viable in regulated industries. Roche operates in one of the most heavily regulated industries globally (pharmaceutical/GxP). If third-party support can meet pharma-grade compliance, audit trail, and security requirements, it can work for virtually any sector.
Licence ownership is preserved. Moving to third-party support does not forfeit your Oracle licence rights. You retain full ownership of perpetual licences and can decide on migration, decommissioning, or even returning to Oracle support on your own timeline.
Build a repeatable playbook. The framework developed for Roche's Siebel transition can be applied systematically across other legacy Oracle products. Most large enterprises have multiple candidates where the same cost/value analysis would yield significant savings.
Start with a support portfolio review. Before making any transition decision, audit your entire Oracle support portfolio. Identify which products are stable, which are actively changing, and where the cost/value ratio is most favourable for optimisation.
By transitioning Siebel CRM support from Oracle to a vetted third-party provider, saving approximately $500,000 per year ($1.5M over three years). The Siebel system was stable with no major patches or critical support requests in over two years, making it an ideal candidate for third-party support.
Siebel had become a low-change, stable system with no major upgrades or customisation planned. Roche hadn't logged a critical support request or applied major patches in over two years — yet was paying nearly $500K annually. When a system is at steady state, third-party support delivers equivalent coverage at roughly half the cost.
Oracle refused to decouple Siebel support or reduce pricing, declaring full entitlement coverage non-negotiable. Their only concession offer was tied to new cloud purchases — which Redress flagged as vendor lock-in rather than genuine flexibility.
Redress ensured the chosen third-party provider met Roche's GxP, audit trail, and security requirements. Detailed technical and commercial due diligence was conducted, and the transition included comprehensive documentation of licence entitlements, deployment history, and risk mitigation planning.
No. Roche retained full ownership of its Siebel perpetual licences. Third-party support replaces Oracle's support services only — licence rights remain intact. Roche can decide on future migration, decommissioning, or even returning to Oracle support on its own timeline.
No. The transition was seamless, with equal or better responsiveness from the new provider. Redress managed the entire process including technical onboarding, internal communications, change management, and operational alignment with Roche's validation and QA processes.
Absolutely. The engagement created a repeatable playbook applicable to any stable, low-change Oracle system — E-Business Suite, PeopleSoft, WebLogic, Oracle Database, and other middleware. Most large enterprises have multiple candidates where the same cost/value analysis would yield significant savings.
Redress ensured comprehensive documentation of licence entitlements and deployment boundaries as part of the transition. These records provide a fully defensible position in case of future Oracle scrutiny. Proper preparation — not avoidance — is the key to audit readiness.
This article is part of our Oracle Third-Party Support pillar. Explore related guides:
Redress Compliance has helped hundreds of Fortune 500 enterprises — typically saving 15–35% on Oracle renewals, ULA negotiations, and audit defense.
100% vendor-independent · No commercial relationships with any software vendor