PeopleSoft third party support. The buyer side case.

PeopleSoft third party support replaces Oracle maintenance with an independent provider at roughly half the fee, while you keep the license you already own.

The case for it on PeopleSoft is not that Oracle support is ending. It is not. Oracle publishes Premier Support for PeopleSoft 9.2 on a rolling "through at least" date that it keeps moving forward.

The case is that you are paying 22 percent a year for a stream of updates most PeopleSoft estates barely apply. This page prices that honestly, including the one constraint that decides it.

What is third party support for Oracle PeopleSoft?

It is a maintenance contract from an independent provider instead of Oracle for PeopleSoft. Your license does not change. Only who answers the phone and who writes the fix changes.

Oracle continues to publish the official roadmap and the Lifetime Support Policy chart for Applications. Third party support is a commercial alternative to that path, not a license event.

Who provides PeopleSoft third party support?

• Rimini Street. The largest independent provider across Oracle applications, and publicly listed, so its financials and litigation status are readable.
• Spinnaker Support. The other established broad provider in this market.
• PeopleSoft specialists. Smaller firms, often staffed by former Oracle or implementation partner people, strong on specific modules or regions.

Score them the way you would any provider. The full framework sits on our provider selection page, and the legal position is set out on the legality page.

What does not change 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.

What ends is the service: new Oracle fixes, new PeopleSoft Update Images, new PeopleTools releases, and access to My Oracle Support.

How long is PeopleSoft actually supported by Oracle?

Longer than most buyers assume, and on a date that keeps moving. PeopleSoft 9.2 is a Continuous Innovation release, which changes how the lifecycle works.

Oracle's applications chart lists these releases with a Premier Support "through at least" date rather than a fixed end. That date has been rolled forward repeatedly, from 2033 to 2034 to 2035 and, in the current chart, to December 2036. Check the current version before you quote it in a business case.

Why that timeline changes the argument, not the answer

An account team will use the long runway as a reason to stay. Read it the other way. A release Oracle intends to support past 2036 is a release you can safely run for a decade.

The honest question is not whether PeopleSoft survives. It is what you get for 22 percent a year on an estate that applies two or three updates and a payroll tax update annually.

What are the economics of leaving Oracle support?

Oracle support runs at 22 percent of net license fees per year, subject to the renewal adjustments set out in the Oracle Software Technical Support Policies. Third party providers anchor at roughly half that.

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

How large is the saving in practice?

Take a PeopleSoft estate with a 2.4 million dollar annual Oracle support line. A provider at 50 percent takes that to roughly 1.2 million, or about 6 million saved over five years before uplift.

Now subtract the parts nobody budgets. A realistic net is usually 40 to 50 percent rather than the headline half.

• Internal effort to own the security compensating controls that used to arrive as patches.
• Any infrastructure upgrade you now have to do differently because PeopleTools is frozen.
• Testing the provider's tax updates, which you would have done for Oracle's anyway.
• The optionality you gave up on returning to Oracle at 150 percent.

Why is PeopleTools the constraint nobody models?

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 applications run on a certified stack: a PeopleTools release, an Oracle Database or other supported database version, an operating system, an application server, and supported browsers. Certification is published per PeopleTools release.

The chain that catches people 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 are now choosing between an uncertified stack, a reinstatement at 150 percent, or a migration you did not plan.

How to defuse it before you sign

• Map the support end dates for your database, operating system and middleware against the PeopleSoft decision. Do this first, not last.
• 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 needs 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 rather than after.

What do you give up by leaving Oracle support?

New Oracle intellectual property, in every form it takes. That means no new fixes, no new PeopleSoft Update Images, no new PeopleTools releases, and no upgrade rights while you are away.

On a stable, heavily customized estate those rights are often worth less than the fee. On an estate with an infrastructure roadmap they are worth a great deal.

Tax and regulatory updates are the real delivery risk

Payroll is where a support failure becomes a regulator letter. Oracle ships tax updates for Payroll for North America on a fixed annual rhythm, and year end processing has statutory deadlines that do not move.

Ask any provider for the last two years of delivery dates by jurisdiction against the statutory deadline. Ask specifically about year end forms and about Global Payroll country extensions if you run them.

What does going back to Oracle cost?

• Reinstatement at 150 percent. Oracle's published policies price a return at 150 percent of the last annual support fee you paid for the relevant programs.
• The lapsed period. Expect to pay for the time you were away as well.
• Matching service levels. Oracle requires every license in a license set to sit at the same support level, so partial returns are rarely simple.
• Time. Reinstatement is a negotiation, not a button. Allow a quarter.

Is your PeopleSoft estate a good fit?

PeopleSoft is one of the strongest fits in the Oracle catalog, because the application is mature and the customizations are stable. Fit is decided by your infrastructure roadmap rather than by the application.

The qualifying test

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 and the move needs sequencing work before it needs a provider shortlist.

Where the common advice on PeopleSoft third party support is wrong

The standard Oracle account team warning is that leaving support strands you on unsupported software and forces a painful return. We disagree, but not for the usual reason. In roughly four out of five PeopleSoft third party moves Fredrik Filipsson advised on, the estate ran for years on a stable release with tax updates delivered on time, and no buyer was forced back. What did cause trouble was never a missing application fix. It was an infrastructure upgrade nobody had put on the same page as the support decision. The buyer side move is to model the database and operating system roadmap first, and only then price the support saving.

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

How do you run the transition safely?

Treat it as a project with a hard date, because the Oracle notice period is unforgiving. Twelve weeks is a realistic run from decision to cutover on a large estate.

The archive window is the part people skip

While the Oracle contract is live you still have My Oracle Support access. That ends when the contract ends, and nothing you failed to download comes back without reinstatement.

• 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 in the estate.
• The last two years of tax update documentation and your applied patch history.
• Your complete service request history, exported.

Knowledge transfer that actually transfers

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 estate will take two cycles to be useful.

Should you use the quote as leverage instead of leaving?

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

Oracle rarely discounts the 22 percent rate itself. What moves is everything around it, and those concessions are worth real money on a large PeopleSoft estate.

• A capped renewal adjustment written into the order, which is worth more over five years than a one year discount.
• Support Rewards credits applied against the on premises fee where you already consume Oracle cloud services.
• A repriced license set where shelfware is terminated cleanly instead of carried at full support.
• Roadmap commitments in writing on the release you run, which is cheap for Oracle and useful to you.

Two rules make this work. Run a real process with real providers, because account teams can tell the difference. And decide in advance what offer would actually make you stay, so you are negotiating rather than bluffing.

What should a buyer do next?

Use this sequence. It works whether you are 60 days or 270 days from renewal.

1. Confirm the release position. PeopleSoft release, PeopleTools release, and the current Premier Support "through at least" date from Oracle's chart.
2. Map the infrastructure roadmap. Database, operating system and middleware support end dates over five years. This decides the answer.
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 150 percent reinstatement in year three as a sensitivity.
7. Apply the newest PeopleTools release you are entitled to. Do this before you give notice.
8. Run the archive window. Everything in the list above, verified and stored, before the contract ends.
9. Time notice to the anniversary. Count the contractual notice period backwards and diarize it now.

White Paper · Oracle PeopleSoft

Oracle PeopleSoft Licensing

Authorization, not usage, and the support runway. Read it free.

Read the white paper

Frequently asked questions

Is Oracle ending support for PeopleSoft?

No. PeopleSoft 9.2 is a Continuous Innovation release and Oracle publishes Premier Support "through at least" a rolling date, currently December 2036 in its applications chart. That date has moved forward repeatedly, so check the current chart rather than a figure quoted in an older article.

How much does PeopleSoft third party support save?

Providers usually anchor at about half of the Oracle fee, which itself runs at 22 percent of net license fees per year. Realized savings in our engagements landed at 45 to 55 percent on the fee, with the net closer to 40 to 50 percent once internal effort and deferred work are counted properly.

What happens to PeopleTools if we leave Oracle support?

You freeze on the last PeopleTools release you were entitled to, and that freezes your certified database, operating system, application server and browser matrix. This is the single most common thing buyers fail to model, so map your infrastructure support dates before you decide.

Will a third party provider deliver payroll tax updates?

Established providers do, and this is the part to diligence hardest. Ask for two years of delivery dates by jurisdiction measured against the statutory deadline, and ask specifically about year end forms and any Global Payroll country extensions you run.

Can we return to Oracle support later?

Yes, at a price. Oracle's published technical support policies set reinstatement at 150 percent of the last annual fee you paid, and you should expect to pay for the lapsed period as well. Model a return in year three as a sensitivity before you leave.

Does third party support cover our customizations?

Usually yes, and on a heavily customized PeopleSoft estate this is a genuine advantage. Oracle support is limited to Oracle delivered code, while independent providers typically support custom objects, interfaces and reports as part of the base service.

What do we lose access to on the day we terminate?

My Oracle Support, and with it new fixes, new PeopleSoft Update Images, new PeopleTools releases and the download library. Run an archive window before termination and pull down every image, release, media file and document you are entitled to.

Which PeopleSoft estates are poor candidates?

Estates with a database or operating system upgrade due inside three years, estates with a funded and dated replacement project already underway, and estates whose security function will not accept compensating controls in place of vendor patches. In those cases fix the sequencing first.

How Redress engages on PeopleSoft

Redress runs PeopleSoft support strategy on the buyer side. We do not resell support, we take no fee from any provider, and every engagement is led by a former Oracle licensing executive.

Read the related third party support guide, the Oracle support cost analysis, the PeopleSoft compliance and audit practices page, the Oracle services page, and the contact page.