Third party PeopleSoft support in 2026. What it saves, and what PeopleTools limits.

Third party support replaces Oracle maintenance on PeopleSoft at roughly half the fee, and you keep the license you own. Oracle support is not ending, so the decision rests on your PeopleTools release and the platform underneath it.

What is third party support for Oracle PeopleSoft?

It is a maintenance contract with an independent provider that replaces the annual support you buy from Oracle for PeopleSoft. Your license does not change. What changes is who takes your service requests, who writes the fixes, and who ships tax and regulatory updates.

Oracle keeps publishing the official roadmap and the Lifetime Support Policy chart for Applications. Moving to a provider is a commercial choice about maintenance, and it does not alter what you own.

Who provides PeopleSoft third party support in 2026?

• Spinnaker Support. An established provider across Oracle applications, and one of the broad providers still signing new PeopleSoft contracts.
• Rimini Street. The largest independent provider across Oracle applications, and publicly listed, so its financials and litigation record are open to read. Under its July 2025 settlement with Oracle it must finish winding down PeopleSoft support by July 31, 2028, which rules it out for a new PeopleSoft contract.
• PeopleSoft specialists. Smaller firms, often staffed by former Oracle or implementation partner people, strong on specific modules or regions. Test their payroll depth before anything else.

Score them as you would any provider. Our provider selection page sets out the scoring, the legality page covers the court record, and the Rimini Street guide explains what the wind down means for current Rimini PeopleSoft customers.

What stays the same when you switch?

Your PeopleSoft entitlement is unaffected. Perpetual licenses do not lapse when maintenance lapses, and the metric you are licensed on stays the same. The PeopleSoft licensing white paper offered on this page covers those metrics in detail.

What ends is the service: new Oracle fixes, new PeopleSoft Update Images, new PeopleTools releases, and access to My Oracle Support. Oracle can still audit your use, so reconcile your license position before you give notice. The PeopleSoft compliance and audit guide shows how.

How long will Oracle support PeopleSoft 9.2?

At least until December 2037 on the current chart, and that date keeps moving. PeopleSoft 9.2 is a Continuous Innovation release, so Oracle lists Premier Support "through at least" a date instead of giving it a fixed end.

Oracle has rolled the date forward roughly once a year: from 2033 to 2034, then to 2035, then to December 2036. In March 2026 it announced 2037, and the applications chart effective August 2026 shows December 2037. Check the current version before you quote any date in a business case.

Does the long runway argue for staying with Oracle?

Account teams present the runway as a reason to stay. We read it the other way. A release Oracle intends to support for another decade is a release you can safely run for a decade without new Oracle code.

The useful question is what the annual support fee buys on a system that applies two or three updates and the payroll tax updates each year. Oracle's rolling date cannot answer that. Your own update history can.

What have we seen in PeopleSoft support decisions in 2024 and 2025?

Across roughly 30 to 40 PeopleSoft and Oracle applications support engagements I advised on in 2024 and 2025, third party support held up where the release was stable and the customizations were mature. We do not resell support or take fees from providers. The figures below come from our own engagement files.

• Fee level. The third party fee landed at 45 to 55 percent of the Oracle support fee.
• Project savings. In roughly half the cases, deferred upgrade and PUM effort saved more than the fee difference itself.
• Staying power. In about 4 out of 5 switches the customer ran for years with no forced return to Oracle support.
• Cause of failure. Where a switch went wrong, the cause was an infrastructure upgrade that had never been scheduled. A missing application fix was never the cause.

That last pattern is why this page spends more time on PeopleTools and the platform underneath PeopleSoft than on application fixes.

How much does leaving Oracle support save on PeopleSoft?

Usually 40 to 50 percent of the Oracle support line, once every cost is counted. Oracle support runs at 22 percent of net license fees per year, subject to the renewal adjustments in the Oracle Software Technical Support Policies, and providers price at roughly half that.

The fee difference is the visible saving. On PeopleSoft the larger number is often the project work you stop doing, because selective adoption still costs testing, regression and change management time in every PUM cycle.

What does a five year model look like?

Take a hypothetical PeopleSoft customer with a $2.4 million annual Oracle support line. A provider at 50 percent takes that to about $1.2 million a year, which saves roughly $6 million over five years before Oracle's renewal adjustments. The table then takes out the costs a business case tends to forget.

The deductions are illustrative and sized for a large installation. The model also leaves out avoided PUM and upgrade effort, which in our files was often the bigger number, so treat the 40 percent as a floor for a system like this.

Which costs do business cases usually leave out?

• Security controls. Internal effort to own the compensating controls that used to arrive as Oracle patches, usually in network segmentation, web tier hardening and monitoring.
• Infrastructure work. Any platform upgrade you now have to do differently because PeopleTools is frozen, including extra testing on an uncertified combination.
• Tax update testing. You test the provider's updates as you tested Oracle's, so this is a transfer of effort rather than a new cost. That is why the model above leaves it out.
• The lost option. A cheap way back to Oracle, since reinstatement carries a penalty fee covered below.

Why does PeopleTools decide whether third party support works?

Because PeopleTools is what certifies PeopleSoft against everything underneath it, and you cannot take a new PeopleTools release once you leave Oracle support. Your platform matrix freezes on the day you terminate.

PeopleSoft runs on a certified stack: a PeopleTools release, an Oracle Database or other supported database version, an operating system, an application server, and supported browsers. Oracle publishes certification per PeopleTools release, so a platform version missing from that list runs uncertified.

How does a frozen PeopleTools release catch buyers out?

1. Your database version reaches the end of its own support window under the Lifetime Support Policy.
2. To move to a newer database you need a PeopleTools release certified against it.
3. You are off Oracle support, so no new PeopleTools release is available to you.
4. You now choose between an uncertified stack, a reinstatement at a penalty rate, or a migration you did not plan.

How do you check your own PeopleTools position?

• Tools and application release. The About This Page link on any PeopleSoft page shows both. A DBA can also read the TOOLSREL column of the PSSTATUS table.
• Updates actually applied. The PS_MAINTENANCE_LOG table records the fixes and change packages applied through Change Assistant. Count them by PUM cycle to see what you really adopt.
• Certified platforms. The Certifications tab in My Oracle Support lists the databases, operating systems and browsers certified for your PeopleTools release. Export it while you still have access.
• Database version. On Oracle Database, SELECT banner FROM v$version returns the release. Compare it with the end dates in Oracle's Technology support chart.
• Operating system and middleware. List every server tier with its version and the vendor's end of support date, in one sheet next to the support anniversary.

How do you defuse the PeopleTools problem before you sign?

• Map the support end dates for your database, operating system and middleware against the PeopleSoft decision, and do it before any other step.
• Apply the newest PeopleTools release you are entitled to before termination, even if you do not need it today.
• Download and archive that PeopleTools release and its certification documentation while you still have access.
• Ask the provider in writing how it supports customers whose infrastructure has to move under a frozen PeopleTools release.
• If a database or operating system upgrade is due within three years, sequence it before the support exit.

What do you give up by leaving Oracle support?

You give up new Oracle intellectual property in every form it takes: no new fixes, no new PeopleSoft Update Images, no new PeopleTools releases, and no upgrade rights while you are away. You also lose Oracle's quarterly Critical Patch Updates, which is why security controls appear in the cost model.

On a stable, heavily customized installation those rights are often worth less than the fee. For a customer with a busy infrastructure roadmap they are worth a great deal.

Why are payroll tax updates the main delivery risk?

A late payroll tax update is the support failure most likely to reach a regulator. Oracle ships tax updates for Payroll for North America on a fixed annual rhythm, and year end processing carries statutory deadlines that do not move.

Ask every provider for the last two years of delivery dates by jurisdiction, measured against the statutory deadline. Ask specifically about year end forms, such as the W-2 in the United States and the T4 in Canada, and about Global Payroll country extensions if you run them.

What does going back to Oracle cost?

• Reinstatement at 150 percent. Oracle's support policies price a return at 150 percent of the last annual support fee you paid for the relevant programs, prorated back to the date support lapsed.
• The lapsed period and the new year. The proration means you pay for the time you were away, and the fee for the new support period comes on top.
• Matching service levels. Oracle requires every license in a license set to sit at the same support level, so a partial return to cover only a few modules is rarely possible.
• Time. Reinstatement is a negotiation with Oracle, and it rarely closes fast. Allow a quarter.

In the hypothetical above, a return after two years away costs 150 percent of $2.4 million for each lapsed year, which is $7.2 million. Add $2.4 million for the new support year and $9.6 million falls due at once.

Those two years on third party support saved $2.4 million, so the reinstatement fee alone is three times the saving. That is why the sequencing work comes before the provider contract. Our guide to dropping Oracle support and reinstatement covers the return process.

Is your PeopleSoft system a good candidate for third party support?

Usually yes. PeopleSoft is one of the strongest fits in the Oracle catalog, because the application is mature and the customizations are stable. Your infrastructure roadmap decides the answer more than the application does.

Which seven questions qualify a PeopleSoft system?

1. Are you on PeopleSoft 9.2 with a PeopleTools release that is current or near current?
2. Is any database, operating system or middleware upgrade due in the next three years?
3. How many updates did you actually apply in the last two PUM cycles?
4. Which jurisdictions do you need payroll and statutory updates for?
5. Do you run Global Payroll country extensions, and which ones?
6. Is there a funded plan to replace PeopleSoft, and what is its realistic date?
7. Will your security function accept compensating controls in place of vendor patches?

Three or more uncomfortable answers mean the switch needs sequencing work before it needs a provider shortlist.

How does the answer change with your situation?

Why we reject the warning that third party support strands you

Oracle account teams warn that leaving support strands you on unsupported software and forces a painful return. Forced returns happen, but in the cases we saw the application held up and the platform under it did not.

In roughly four out of five PeopleSoft switches I advised on, the customer ran for years on a stable release with tax updates on time. The rest failed on an infrastructure upgrade no one had placed next to the support decision. Model the database and operating system roadmap first, and price the support saving after that.

Third party support is a maintenance decision rather than a license decision. The question is what 22 percent a year buys on a release you have no intention of leaving.

What will Oracle's account team say, and how should you answer?

Expect the same few arguments once Oracle learns you are pricing an alternative. Each one has a factual reply, and it helps to agree the replies internally before the first call.

Should you use a third party quote to renegotiate Oracle support instead?

Often, yes, and decide that before you run the process. A credible third party quote is the strongest bargaining position most buyers ever hold on an Oracle support line.

Oracle rarely discounts the support rate itself. The concessions come in the terms around it, and on a large PeopleSoft contract they are worth real money.

• A capped renewal adjustment written into the order, which is worth more over five years than a one year discount.
• Support Rewards credits against the Oracle Database and middleware support that sits under PeopleSoft, where you already consume Oracle cloud services. See the Support Rewards guide for the rules.
• A repriced license set where shelfware is terminated cleanly instead of carried at full support. Oracle's policies reprice the remaining licenses at the current support list price minus the standard discount, so the saving is often smaller than the shelfware's share of the bill. Ask for the repriced figure in writing before you agree.
• Roadmap commitments in writing on the release you run, which cost Oracle little and help you.

Two rules make this work. Run a real process with real providers, because account teams can tell the difference. And decide in advance which offer would make you stay, so you negotiate toward a number you set yourself. Our Oracle support cost analysis and renewal negotiation guide cover the Oracle side.

Which contract terms should you ask a provider for?

• Tax update delivery by jurisdiction. Dates set against each statutory deadline, with a service credit if one slips, because payroll is where a miss costs most.
• A named coverage schedule. Every module, PeopleTools release, database and operating system version covered, so there is no argument later about scope.
• Security response terms. How the provider reviews each Oracle Critical Patch Update and how fast it delivers a mitigation, so your security team can sign off.
• A price hold for the full term. Any increase capped in the contract, since the saving erodes fast if the provider raises fees every year.
• An indemnity. Cover for defense and settlement of claims arising from the provider's support method, surviving termination.
• Exit assistance. Return of every fix and document written for you, so you can change provider or go back to Oracle without starting cold.

Our third party support guide covers these terms across the wider Oracle catalog.

How do you run the transition safely?

Treat it as a project with a hard date, because the Oracle notice period does not bend. Twelve weeks is a realistic run from decision to cutover on a large PeopleSoft installation.

What must you download before My Oracle Support access ends?

While the Oracle contract is live you still have My Oracle Support. Access ends when the contract ends, and nothing you failed to download comes back without reinstatement. The archive window is the step teams most often skip.

• The latest PeopleSoft Update Image you are entitled to, plus the two before it.
• The newest PeopleTools release and its full certification documentation.
• Installation media for every product and version you run.
• The last two years of tax update documentation and your applied patch history.
• Your complete service request history, exported.

What does the provider need from you on day one?

Give the provider your customization inventory, your integration map and your batch schedule before day one. A provider that starts cold on a customized PeopleSoft system will take two cycles to be useful.

What is the timeline to the support anniversary?

What to do next

This sequence works whether you are 60 days or 270 days from renewal. Closer in, run the first four steps in parallel and use the model in step 6 in your Oracle negotiation.

1. Confirm the release position. Your PeopleSoft release, your PeopleTools release, and the current Premier Support "through at least" date on Oracle's chart.
2. Map the infrastructure roadmap. Database, operating system and middleware support end dates over five years. These dates settle most cases.
3. Count what you actually adopt. Updates applied in the last two PUM cycles, and the effort each one cost.
4. List the jurisdictions. Every payroll and statutory reporting jurisdiction, with its deadline calendar.
5. Shortlist two providers plus a specialist. Require a named coverage schedule and two years of tax update delivery history.
6. Model five years both ways. Include internal effort, deferred projects, and a return to Oracle in year three as a sensitivity.
7. Take the newest PeopleTools release, then archive. Apply it before you give notice, and download everything on the archive list before the contract ends.
8. Time notice to the anniversary. Count the contractual notice period backwards and put the date in the diary now. Our Oracle advisory team can run the model with you, and you can reach us through the contact page.

Frequently asked questions