The state of PeopleSoft and JDE in 2026.
PeopleSoft and JD Edwards remain among Oracle's most stable installed bases. The two product lines together cover thousands of large enterprises across financial services, manufacturing, higher education, public sector, and consumer goods. Oracle has committed to support extensions that run into the next decade, and the active customer count has remained substantially flat for the past five years. The narrative that Oracle is winding these products down is, in commercial terms, incomplete. The support contracts that fund them remain a material line in Oracle's recurring revenue.
What has changed is the negotiation context. Oracle's sales motion now positions PeopleSoft and JDE customers as candidates for Oracle Fusion Cloud Applications, the modern Oracle suite that replaces the on premises functionality with a SaaS subscription. Every renewal cycle now opens with a Fusion Cloud conversation. Procurement teams who do not have a clear position on whether they are migrating, staying, or restructuring will find that conversation defining the commercial terms whether they want it to or not.
The three negotiation paths.
A PeopleSoft or JDE customer in 2026 has three negotiation paths to choose from. The first path is the steady state renewal where the customer continues running the on premises product, pays the annual support fee with the standard uplift, and treats the relationship as a maintenance line item. The second path is the migration path where the customer accepts the Oracle proposal to move to Fusion Cloud and negotiates the migration terms, the parallel run period, the data conversion costs, and the new subscription pricing. The third path is the restructure path where the customer stays on premises but renegotiates the commercial structure, often shifting to third party support or a reduced scope support contract that removes products the business no longer uses.
Each path has a different negotiation playbook. The steady state path is the simplest commercially but is the path where Oracle generates the largest year on year compounding through the standard uplift. The migration path produces the largest one off pricing event in the relationship and is where Oracle expects to capture the largest forward revenue. The restructure path is the most complex but produces the largest immediate cost reduction.
Path comparison at a glance
- Steady state. Lowest disruption, highest compounding cost over 5 years, moderate negotiation leverage.
- Migration to Fusion. Highest disruption, highest one-off commitment, strong negotiation leverage at the deal point.
- Restructure with third party support. Moderate disruption, largest immediate savings (40 to 60 percent), low Oracle co-operation.
What Oracle is measuring.
Oracle measures PeopleSoft and JDE accounts on five internal metrics that shape the renewal conversation. Recurring support revenue. Net new license revenue, which for these products is now small. Cloud migration potential, which is the key number for the account team. Time to next renewal anniversary, which sets the deadline pressure. And competitive risk, which is the probability that the customer will leave Oracle for a different ERP or for third party support. The account team prioritises the conversation differently depending on how these metrics rank.
Understanding what your account team is measuring is one of the highest value pre-negotiation activities. An account where Oracle measures competitive risk as high will receive different concession behaviour than an account where Oracle measures cloud migration potential as high. The conversation can be steered by deliberately changing what Oracle believes about the account.
The Fusion Cloud conversation.
Oracle's Fusion Cloud proposal to a PeopleSoft or JDE customer usually arrives with three components. A migration pricing schedule that quantifies the SaaS subscription for the modules the customer currently uses on premises. A migration services proposal that quantifies the implementation work, usually delivered by Oracle Consulting or a named system integrator. And a credit structure that applies the residual value of the existing on premises licenses against the Fusion Cloud subscription cost. Each of these components is negotiable, and the credit structure is where the largest single negotiation lever sits.
The credit structure typically starts at zero to twenty percent of the historic license value. Buyer side negotiation routinely takes this to 40 to 60 percent. The credit structure can be applied as a reduction to the first year subscription cost, as a reduction over multiple years, or as a credit toward Oracle Cloud Infrastructure consumption. Each structure has different cash flow implications and different accounting treatment.
The third party support option.
Third party support providers such as Rimini Street and Spinnaker Support offer ongoing maintenance for PeopleSoft and JDE at typically 50 percent of Oracle's published support fee. The technical proposition is mature. The legal context has stabilised after years of litigation between Oracle and third party support providers. Customers who move to third party support save a substantial portion of the recurring cost and gain extended support lifetimes for older product versions that Oracle has formally exited.
The negotiation implication of third party support is broader than the cost saving alone. Even customers who do not intend to leave Oracle support find that introducing third party support as a credible alternative materially changes Oracle's behaviour at the renewal table. Oracle account teams have explicit internal targets to retain customers from third party support transitions and are authorised to offer concessions that would not otherwise be available.
The customisation trap.
PeopleSoft and JDE installations carry years of customisations. These customisations were built to address business processes that the standard product did not cover. They are also the single largest barrier to migration and the single largest source of pricing power for Oracle in any migration conversation. Oracle's standard line in migration discussions is that customisations will be reviewed and that some will be carried forward into Fusion Cloud as configurations rather than customisations. The reality is that most customisations cannot be carried forward and must be either retired, rebuilt, or replaced with workarounds.
The negotiation implication is that the cost and risk of customisation conversion should be quantified before any commitment is made to a migration timeline. Oracle's standard practice is to include the customisation conversion work in the migration services proposal at an aggregate fee. Buyer side practice is to require a customisation-by-customisation conversion plan with documented fees, timelines, and acceptance criteria. The two approaches produce materially different commercial outcomes.
The support uplift trajectory.
PeopleSoft and JDE customers who choose the steady state path face a compounding cost trajectory that is often understated in internal procurement planning. The Oracle support uplift is contractually capped at a percentage that varies by contract, but is commonly 22 percent across multiple consecutive years for the same set of licenses. Over a five year period, an annual uplift compounds to approximately two and a half times the starting support cost. Most procurement teams model this as a flat cost when in fact it is exponential.
The negotiation response is to require a multi year support commitment with a contractually capped annual uplift, typically two to four percent rather than the standard rate. Oracle resists this commercially but will agree to capped uplifts in exchange for multi year commitments. The negotiation is one of the highest value items in a steady state renewal because the savings compound across the full term of the agreement.
How we work on PeopleSoft and JDE negotiations.
Our engagement model on PeopleSoft and JDE work depends on the path the customer is taking. Steady state renewals are engaged under the Success Fee model, with the fee set against a baseline determined at engagement start. Migrations to Fusion Cloud are engaged under the Fixed Fee model because the deliverables are scope-defined and the timeline is bounded by the migration calendar. Restructure engagements including third party support transitions are usually engaged under a combined Fixed Fee plus Success Fee structure.
The deliverables across all three paths include a quantified current state assessment, a path comparison with five year cost projections, a counter offer document for the chosen path, and live negotiation support through to signature. Engagement length is typically eight to sixteen weeks depending on the path and the complexity of the estate.
Frequently asked questions.
Is Oracle ending support for PeopleSoft and JDE?
No. Oracle has committed to support extensions that run into the next decade for both products. The narrative of product end of life is incomplete and is often used commercially to drive migration conversations.
What is a typical migration credit from on premises to Fusion Cloud?
Across our recent engagements the negotiated migration credit averaged 47 percent of the historic license value. The range observed is approximately 20 to 70 percent depending on the size of the estate and the negotiation posture.
Should we move to third party support before negotiating the renewal?
The credible threat of third party support is more valuable in the negotiation than the actual move. Oracle account teams are explicitly compensated on retention from third party support providers and will offer concessions to retain the support contract. Some customers move, most negotiate.
How long does a PeopleSoft to Fusion migration typically take?
The published timelines are 12 to 18 months for a mid-complexity estate. Realised timelines are commonly 18 to 30 months once customisation conversion is included. The timeline should be a negotiation input on the commercial structure of the deal.
Can we keep some PeopleSoft modules and migrate others to Fusion?
Yes. Hybrid arrangements are common and Oracle will support them commercially. The integration cost between the on premises and SaaS components should be a contractual input rather than an implementation surprise.
What is the negotiation impact of waiting until the renewal anniversary?
Negotiating after the renewal anniversary substantially weakens the buyer position because the uplift has already been applied and the next negotiation window is twelve months away. Engaging the renewal six months in advance is the practical floor for material savings.
Related reading.
- Our Renewal Negotiation service page for the steady state path.
- Co-Term Renewal deal type page for customers aligning multiple Oracle agreements.
- PeopleSoft product page with product-specific commercial detail.
- JD Edwards product page for JDE-specific commercial detail.
- The Negotiation Playbook 58 page reference paper.
- JDE to Oracle Fusion Cloud Migration sub article on migration paths.