PeopleSoft customers on a stable release have a real choice. Stay on Oracle Premier or Extended Support, or move to a third party support provider at roughly half the annual cost. This article maps the framework, the math, the audit risk, and the exit path.
PeopleSoft is one of the easiest Oracle estates to move to third party support. The product is mature. The release cadence is slow. The audit defense is well understood. The buyer side decision is almost always a cost decision, not a feature decision.
Customers on PeopleSoft 9.2 with Application Maintenance Pack 27 or later have access to a stable release that runs without major change through 2034 under Oracle Premier Support. The same release runs on any of the three named third party support providers at roughly half the annual fee, with the same break/fix scope and the same regulatory updates.
This article frames the decision, the math, the risk, and the exit path. Read it alongside the Oracle knowledge hub, the PeopleSoft compliance article, and the Oracle services page.
The motive is rarely dissatisfaction with Oracle support tickets. The motive is cost, and a recognition that the support fee buys very little incremental value on a mature estate.
A typical mid sized PeopleSoft estate carries 1.4M to 3.8M USD per year in Oracle support fees on a Financials, HCM, and ELS bundle. The same estate on third party support lands at 700K to 1.9M USD per year.
The five year saving across a Vendor Shield client base sits at 30 to 60 percent of total Oracle support spend on the PeopleSoft footprint, before factoring database and middleware decisions.
The cost decision is not free. Third party support narrows the relationship with Oracle and removes specific entitlements that some customers rely on.
The five year compare is the right horizon. Year one savings often understate the gap because Oracle support uplift compounds across the period.
| Scenario | Year 1 | Year 3 | Year 5 | 5 year total |
|---|---|---|---|---|
| Oracle Premier at 8 percent annual uplift | 2,650,000 | 3,089,856 | 3,602,816 | 15,548,000 |
| Oracle Premier at 4 percent capped uplift (negotiated) | 2,650,000 | 2,866,144 | 3,099,930 | 14,344,000 |
| Third party support at 3 percent uplift | 1,180,000 | 1,251,855 | 1,327,899 | 6,259,000 |
| Saving vs Oracle Premier 8 percent | 1,470,000 | 1,838,001 | 2,274,917 | 9,289,000 |
Oracle LMS audits a small but non zero percentage of customers in the year following a third party support move. The defense is structural, not reactive.
The 2014 to 2018 Rimini Street and Oracle litigation defined the boundaries. Customers can lawfully use third party support for software they license. Third party providers cannot store Oracle update files in shared multi tenant repositories, and cannot use one customer's downloaded materials to support another customer.
The current major providers operate under court mandated controls that segregate customer environments. The buyer side risk on a 9.2 estate is well understood and manageable.
The right answer turns on five questions. Walk through each before signing or rejecting the third party proposal.
| Question | Stay on Oracle | Move to third party |
|---|---|---|
| Will the customer adopt new PeopleSoft features in the next 5 years? | Yes, plans active | No, frozen on current release |
| Is a Fusion HCM or Fusion Cloud ERP migration planned in 24 months? | Yes, migration credits matter | No, or migration is 36+ months out |
| Does the customer rely on Oracle for global tax and payroll updates? | Comfort with Oracle delivery | Comfortable with third party delivery |
| Does Oracle Premier Support deliver real ticket value? | High SR volume on PeopleSoft | Low SR volume, low complexity |
| Is the database moving to OCI or staying on premises? | OCI migration credit eligible | On premises, no Oracle Cloud roadmap |
A clean third party support move runs across 12 months. Skip the sequence and the customer either misses the notice window or arrives at the cut over date without an audit defense pack.
Whether the customer ends up on Oracle or third party, the negotiation table moves when procurement names the alternative. Even staying on Oracle, the conversation about third party support reshapes the renewal.
The checklist takes a PeopleSoft customer from the current renewal cycle to a decision and a clean execution.
Yes. Customers have a contractual right to use the PeopleSoft software they license, and to engage third parties to support that software. The Rimini Street and Oracle litigation defined the boundaries on how providers handle Oracle update materials, but the customer's right to use third party support is well established.
The current major providers operate under court mandated controls that segregate customer environments. The buyer side risk on a stable 9.2 estate is manageable with the right audit defense pack in place.
The annual support fee under third party support typically lands at 50 percent of Oracle Premier or Extended Support. Across five years, with Oracle uplift compounding, the saving runs 40 to 60 percent of total support spend on the PeopleSoft footprint before factoring transition cost.
A 4,800 user mid market PeopleSoft estate at 2.65M USD per year Oracle support typically lands around 1.18M USD per year on third party, with five year cumulative savings around 9M USD.
Yes. The major third party providers maintain global tax, US payroll, and country specific regulatory updates for PeopleSoft 9.2 through 2030 and beyond. The delivery mechanism is the provider's own update bundle, not the Oracle PeopleSoft Update Manager image.
Validate the specific countries, tax types, and payroll types covered in the provider's update commitment before signing.
The Oracle Database license under PeopleSoft is separate from the PeopleSoft license. The database can stay on Oracle Premier Support, move with the application to third party support, or run on the major third party provider's database support practice.
The decision turns on whether the customer has a database upgrade roadmap (stay on Oracle), whether the database needs ongoing CPU patches (assess third party patching solutions), and whether the cost saving justifies the operational shift.
Oracle's Matching Service Levels (MSL) policy requires that, where a customer holds support on a license group, all licenses in that group carry the same level of support. The policy constrains hybrid moves where the customer wants part of a license bundle on Oracle and part on third party.
The practical workaround is to split licenses into separate Oracle license groups before the move, where the underlying licenses and ordering documents permit. Document the split carefully and validate against the order documents before terminating support on one side of the boundary.
Yes. Oracle offers a reinstatement path. The customer pays the back support fees for the period under third party support, plus a reinstatement penalty (typically 50 percent of the lapsed support). The reinstatement is usually possible within 24 to 36 months of the termination.
Beyond that window, reinstatement may require renegotiation of the entire license position. Document the reinstatement formula in writing during the support termination correspondence.
Redress runs the third party support decision inside the Vendor Shield subscription, the Oracle services practice, and the Renewal Program. The output is a five year cost compare, a decision matrix, a provider shortlist, an audit defense pack, and the negotiation execution with Oracle support sales.
The work is led by Oracle commercial professionals on the buyer side. We have run PeopleSoft third party support decisions across pharma, banking, manufacturing, distribution, and public sector customers running PeopleSoft estates from 800K to 8M USD per year in Oracle support.
Redress runs PeopleSoft third party support advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program.
Read the related PeopleSoft compliance article, the database licensing guide, the database pricing 2026, the ULA decision framework, the contract renewal strategy, the contract negotiation service, the telecoms licensing guide, the benchmarking page, the about us page, and the contact page.
Buyer side reference on Oracle contracts. Scope, certification math, exit modeling, OMA term protection, and the seven levers procurement carries to every Oracle renewal.
Independent. Buyer side. Written for CIOs, CFOs, procurement leaders, and Oracle contract owners running active PeopleSoft, EBS, and database renewals. No Oracle kickback. No conflict on the table.
Open the white paper in your browser. Corporate email only.
Open the Paper →The third party support conversation is the strongest commercial lever an Oracle Applications customer carries into the renewal. Even when the customer stays on Oracle, the named alternative typically takes 12 to 22 percent off the uplift demand.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
PeopleSoft, EBS, Fusion, and JD Edwards lessons from every Oracle Applications engagement we run. Audit defense patterns, third party support case data, migration credit benchmarks, and renewal lessons.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
