An analysis for executives, analysts, partners, and customer decision-makers.
The views below are my own, based on publicly available information and my work in the JD Edwards ecosystem. Nothing here represents inside knowledge of Oracle's strategy. Oracle would likely tell this story differently. I welcome that conversation.
The Short Version
Oracle tells the market that JD Edwards EnterpriseOne is supported through at least 2037. It says the same thing, broadly, about PeopleSoft, E-Business Suite, Siebel, and Hyperion under the Applications Unlimited umbrella. Oracle's official language says Premier Support is available through at least 2037 on current Continuous Innovation releases, with an annual review to decide whether to extend the window again (Oracle Lifetime Support Policy).
That sounds reassuring. It is supposed to. But it also creates a strange signal.
Most enterprise software vendors handle long-term product commitments in one of two ways. If the product is modern SaaS, it is evergreen. There is no support date because there is no customer-owned version aging out. If the product is an older on-premise product, there is usually a real end-of-life date, a successor product, and a migration path.
Oracle's Applications Unlimited products fit neither model cleanly.
They are not evergreen SaaS. But they are also not really being sunset. The 2037 date looks like a deadline, while Oracle's annual-extension pattern suggests the deadline may keep moving forever.
That is the paradox.
Oracle is creating the perception of a sunset for products it does not appear to be retiring, while implying migration paths that do not always work for the industries those products serve.
The problem is not that Oracle has abandoned these products. It has not.
The problem is that Oracle has preserved the products technically while allowing the story around them to decay.
How We Got Here
The current framing made sense once.
Charles Phillips, then Oracle's co-president, gave customers the answer that became Applications Unlimited.
Oracle told customers it would keep supporting and developing the acquired product lines. No forced migration. No immediate sunset. No panic.
That commitment probably protected an enormous amount of maintenance revenue. It also gave customers a reason to stay calm long enough for Oracle to manage the acquisition.
To make the promise work, Oracle used the support mechanism we still see today: Premier Support through at least a future date, with annual review for possible extension.
In 2005, that was elegant. There was no mature Fusion Cloud ERP story. There was no OCI investor narrative. There was no twenty-year history of dates being extended again and again.
Today, the same mechanism feels different.
What started as reassurance now creates doubt. It makes a continuing product line sound like a product approaching a date.
Oracle Deserves Credit for the Product
It is important to be fair about this.
Oracle has not abandoned JD Edwards technically. Tools 9.2 has continued to receive releases. Application 9.2 has gained user-defined objects, orchestrations, notifications, and citizen-developer capabilities. The Orchestrator platform gave JDE customers a modern automation and integration layer before many comparable products had anything as useful.
Oracle has honored the core promise in real ways. There has been no forced migration. There has been continued support. There has been genuine product evolution.
That is exactly what makes the current situation so frustrating.
The engineering story is better than the market story.
Oracle has continued investing in the software, but the public positioning makes the product feel less strategic than it actually is.
Why the Framing Looks So Odd Now
The rest of the market tells cleaner stories.
Workday, Salesforce, Microsoft Dynamics 365, SAP S/4HANA Cloud, NetSuite, and Oracle Fusion Cloud are positioned as evergreen platforms. They are cloud products. They keep evolving. Customers do not think in terms of a support end date.
Older on-premise products are different. They usually have lifecycle dates, successor products, and migration paths. SAP, for example, says it will provide mainstream maintenance for SAP Business Suite 7 core applications through the end of 2027, with optional extended maintenance through the end of 2030. SAP also announced an innovation commitment for SAP S/4HANA through the end of 2040 (SAP support strategy).
Oracle's Applications Unlimited products sit in the middle.
They are not SaaS. But they are also not really on a sunset path. Oracle says Premier Support runs through at least 2037 and that it will review annually whether to extend support again (Oracle Lifetime Support Policy).
That is technically reassuring. Strategically, it is messy.
It creates the feeling of an expiration date without the clarity of an actual end-of-life plan.
And for JD Edwards customers, the implied destination is not always realistic. Fusion Cloud ERP is a strong product for many use cases, but it does not simply replace JDE in every industry JDE serves.
A few specific examples make this concrete. JDE's real estate management module handles commercial leasing, percentage rent, CAM reconciliation, and tenant accounting at a depth Fusion does not match. JDE's project costing and job cost modules remain the standard for construction and engineering firms, with subcontractor management, retention handling, and AIA-format billing that Fusion's project capabilities have not replicated. JDE's manufacturing depth, particularly for process manufacturers with co-products and by-products and for discrete manufacturers with deep configurator requirements, exceeds what Fusion currently delivers. These aren't edge cases. They're the core operational systems for entire industry segments that JDE owns.
JDE is not just generic ERP. Its value is in operational depth, in industry-specific patterns that are hard to replicate. For many customers, JDE is not old software they have failed to replace. It is the system that still fits their business better than the fashionable alternatives.
The Brand Problem
This is the part vendors often miss.
Enterprise software customers do not just buy features. They buy a future.
When a company chooses an ERP system, it is making a fifteen-to-twenty-year bet. It will hire around that system. Train around it. Integrate around it. Build reporting, workflows, customizations, controls, and institutional knowledge around it.
That customer needs to believe the vendor believes in the same future.
Walk up to SAP and the answer is one sentence. "You're going to be on the SAP platform. ECC today, S/4HANA tomorrow, an S/4HANA innovation commitment through 2040. One vendor. One roadmap. We're going to be your ERP partner for the next twenty years."
Walk up to Microsoft and the answer is one sentence. "You're going to be on Dynamics 365. Cloud-native, continuously updated, clear modernization paths from anything older. One vendor. One platform."
Walk up to Workday and the answer is one sentence. "You're going to be on Workday. SaaS. Evergreen. Continuously evolving. We don't have a sunset because we don't have versions."
Now walk up to Oracle.
The answer isn't one sentence. The answer is a flowchart.
There's JD Edwards, supported through 2037, with annual reviews. There's PeopleSoft, supported through 2037, with annual reviews. There's E-Business Suite, supported through 2037, with annual reviews. There's Siebel, on its own track. There's Oracle Fusion Cloud ERP, the strategic direction, which doesn't actually do what JDE does for your industry. There's NetSuite, for companies smaller than yours. There's OCI underneath all of it.
Which one are you committing to? What's your future with Oracle? Where is your investment compounding?
Oracle's answer to that question, as best as anyone can tell, is "it depends."
That's not a brand commitment. That's a portfolio.
A vendor sees product flexibility. A customer sees vendor indecision. A vendor sees "we have an offering for every segment." A customer sees "you don't know which of these will still be your priority five years from now."
That's what JDE was for those customers, once. A clear brand commitment. A long-term relationship with a vendor that was going to keep investing. The 2037 framing has quietly turned that clear commitment into a question mark. Not because the support is actually going away, but because the framing makes it impossible for a customer to believe they're committing to a future rather than an extension.
The competitive reality matters here. The mid-market business that JDE used to win is now going to specific competitors in specific tiers. At the upper end, SAP S/4HANA and Microsoft Dynamics 365 F&O are winning customers who want global standardization. In JDE's traditional sweet spot, NetSuite, Acumatica, Microsoft Dynamics, and SAP are all actively competing for selections that would have been JDE wins a decade ago. At the lower end, NetSuite has effectively captured the segment. Every one of these competitors can tell a customer a coherent twenty-year story about their platform's future. Oracle, in this segment, cannot.
In enterprise software, the cleanest future story often wins.
Right now, Oracle's JDE story is not as clean as the product deserves.
What This Is Probably Costing Oracle
The cost does not show up all at once.
ERP maintenance revenue is sticky. Customers do not rip out a core ERP system because of one confusing support phrase. They wait. They budget. They evaluate alternatives. They defer upgrades. They move a piece at a time. They test third-party support. They stop hiring into the platform. They stop inviting the product into new strategic conversations.
That is how erosion happens.
Net-new JDE selections have become harder to find. Implementation partners have diversified away from Applications Unlimited work. Senior consultants are aging out faster than new practitioners are entering. ISV investment has slowed. Third-party support providers like Rimini Street and Spinnaker Support continue to compete for Oracle maintenance dollars.
None of that creates an immediate revenue cliff. Together, it reduces the future value of the installed base.
The Growth Engine Has Slowed
A healthy ERP ecosystem needs net-new implementations.
New logos create more than license and maintenance revenue. They give partners projects to staff. They give consultants careers to build. They give ISVs customers to sell into. They give universities and training programs a reason to produce new talent. They give user groups fresh energy.
When new logos slow down, the ecosystem does not collapse. It just starts living off the installed base.
That is what the JDE community increasingly feels like.
It is easier to see if you remember what these events used to look like.
Ten or fifteen years ago, the floor at INFOCUS, BLUEPRINT 4D, and the regional user group events included a meaningful number of attendees who weren't yet JDE customers. They were prospects. They were companies evaluating ERP systems, walking the booths to talk to partners, comparing options, gathering information so they could go home and make a decision. You could tell who they were because they asked different questions than the existing customers did. They wanted to understand the product, the partner landscape, the implementation timeline, the total cost. They were shopping.
That cohort is largely gone now.
The faces at these events are the same ones who were there last year. And the year before. And the year before that. The customers in the room are mostly existing JDE customers reinforcing decisions they made a decade or two ago. The sponsors are partners and ISVs servicing the existing installed base, not partners chasing new logos. The conversations are about extending the life of current investments, not evaluating JDE for new projects.
The functional purpose of the event has changed. These conferences used to be marketplaces where prospects came to evaluate the JDE ecosystem and decide whether to enter it. They are now reunions of the people already in it.
And here's the tell that anyone in enterprise software will recognize immediately. The vendors at these events aren't competing for net-new prospects. They're competing to pick each other's customers off. The hosting providers want to win customers from other hosting providers. The managed services firms want to displace incumbent managed services firms. The ISVs want to swap out a competitor's add-on with their own. The implementation partners want to take over an existing customer relationship from another partner.
That's not growth. That's a zero-sum scramble inside a shrinking pie.
When you ask SI partners at the sponsor booths about their net-new logo wins over the past year, the answers get quiet. Most won't volunteer the number. The ones who do usually mention a handful of deals, mostly from existing customers expanding their footprint, almost none from companies new to JDE making a fresh selection.
You can also see the same dynamic in the session content itself. Walk the schedule at any JDE event from the past year and notice how nearly every education session is prefaced with AI. AI and JDE orchestration. AI-enabled financial close. AI for warehouse management. AI agents for HR. AI this, AI that. The session titles tell you exactly where the partner and ISV community believes future revenue lives.
Then you actually attend the sessions.
And the substance often isn't there. The titles promise AI. The slides show a few demos that are mostly OCI services bolted onto the side of JDE functionality that has worked the same way for fifteen years. The case studies are thin. The customer panels are mostly speculation about what might be possible. The presenters are doing their best, but you can feel the gap between what was promised by the session title and what's actually being delivered.
You see the same pattern at the booths themselves. When a vendor needs a guy with a guitar playing in the booth to attract foot traffic, or a magician, or a high-stakes prize wheel, or any of the other increasingly elaborate gimmicks that have crept into these events, what you are watching is not a healthy market. Booths in growing markets don't need gimmicks. They have prospects walking up because the prospects want to know more about the product. When the only way to get someone to stop at your booth is to entertain them first, the underlying demand for what you are selling is not where it needs to be.
This is what an ecosystem trying to stay relevant looks like.
Partners are not slapping AI onto every session because they have rich AI offerings. They are slapping AI onto every session because they have to. They are not hiring guitarists for their booths because their products are so exciting people need musical accompaniment to celebrate them. They are doing it because the community has collectively agreed that AI is where the energy needs to be and that attention is the scarce resource, because every other growth conversation has gotten harder to have. Net-new JDE selection? Hard. Services expansion? Hard. Partner-led infrastructure work? Going to Oracle. Current JDE customers? Silently being pushed to Oracle Fusion.
That's not a one-off. That's the model. Every component of event participation, from the meaningful to the ridiculous, has been priced upward year after year while the leads generated by attendance have moved in the opposite direction.
Let me be clear about what this is and isn't saying. The events themselves are well-run. Quest produces real value for the community, and the cost of producing professional enterprise software conferences is genuinely high. Venue costs are real. AV is real. Logistics, registration systems, programming, staff time, security, food and beverage minimums, all of it is real. The people running these events are doing serious work.
The problem isn't the cost of the events. The problem is what's happening to the value side of the equation.
Five years ago, the math worked. Partners paid the sponsor fees, attended the conferences, met prospects, generated leads, and turned a meaningful percentage of those leads into business. The cost of participation was justified by the pipeline it produced.
Today, the same costs are being charged into a market where the leads have disappeared. The same sponsor fee that produced a clear ROI in 2020 is producing significantly less in 2026, not because the event got worse but because the underlying market the event serves has been progressively undermined.
The issue is that the events sit downstream of Oracle's decisions about JDE's positioning, services strategy, and ecosystem investment. When those upstream decisions damage the partner ecosystem's economic model, the events become economically harder to sustain, even when the events themselves are still excellent.
The User Group Signal
The local user group issue deserves more attention than it gets.
There was a time when Oracle's presence at local JDE user groups felt connected to the product organization. Product people showed up. Oracle co-led these events. Oracle helped support programming. Customers had visible access to people connected to roadmap and engineering.
That era is over. Today, Oracle's presence at most local user group events is a single product manager dialed in by video to give a generic update on a new feature or function. No co-leadership. No financial support. No sustained product team presence. Just a virtual cameo and a marketing slide.
In Oracle's absence, partners and vendors have taken over the leadership of these user groups. That is not a criticism of the partners. They stepped up because Oracle stepped back, and the community would have lost its gathering places entirely without them. But it changes what a user group fundamentally is.
A user group led by the product owner is a feedback loop into engineering and roadmap.
A user group led by partners and vendors is a marketing and services channel for the existing installed base.
Both have value. They are not the same thing, and Oracle's customers deserve the first one.
The cost of fixing this would be trivial. A handful of plane tickets per quarter. A few hours of product team time. The decision not to make that investment, made year after year, has become its own form of communication. When the community sees that Oracle will not spend even modest money on the gathering places that hold the customer base together, the community draws the obvious conclusion. JDE is not a priority. The user groups are not a priority. And by extension, neither are the customers and partners who depend on both.
The Partner Economics Problem
The partner side is where the math gets harder.
Over the past several years, Oracle has progressively captured infrastructure and database revenue that used to flow through partner channels. As Oracle has built out OCI and its autonomous services, the economics of hosting and managing JDE environments have shifted. When a JDE customer moves their workload to OCI, the infrastructure spend goes to Oracle. When autonomous database services handle patching and tuning automatically, the partner labor that used to bill for that work shrinks.
Partners still provide most JDE-specific managed services. But the underlying platform layer has been progressively absorbed into Oracle's revenue stream. The technical work hasn't disappeared, but the labor-intensive portion that partners used to bill hours for is being automated and absorbed into Oracle's platform economics.
None of this is irrational for Oracle. OCI growth matters. Autonomous services scale better than manual labor. Customers like simpler infrastructure operations. Oracle has every reason to capture more of the platform economics underneath its installed base.
But the ecosystem effect is real.
The pattern is clear when you step back. First, Oracle's platform and autonomous services progressively reduced the technical labor that partner managed services providers used to bill for. Now, Oracle is automating away similar work that its own employees were doing. The technical labor that used to support Applications Unlimited customers is being progressively replaced by automation, on both sides of the customer relationship.
For a JDE partner trying to run a sustainable practice on labor-intensive infrastructure and database work, the math has stopped working. The partners that survive are increasingly the ones positioned around higher-value application functional work, custom development, and orchestration enablement. The partners exposed to commoditizing technical labor are getting squeezed out.
Oracle's Real Constraint
Oracle is not making these decisions in a vacuum.
That is the story investors are buying.
So no, Oracle is not going to suddenly make Applications Unlimited the center of its corporate narrative. That would not be realistic.
Inside that environment, a massive new Applications Unlimited investment program is not realistic.
But that is not what is needed.
The point is not to make JDE the new center of Oracle's strategy. The point is to stop weakening a profitable, loyal, industry-specific installed base through avoidable ambiguity.
Oracle can keep leading with OCI, AI, Fusion, and NetSuite while still giving Applications Unlimited customers a clearer reason to keep investing.
What Oracle Could Actually Do
Reframe the support commitment. The highest-leverage move is also the simplest. Move from "Premier Support through at least 2037, reviewed annually" to language closer to "Premier Support continues with no planned end date as part of the Applications Unlimited program." That preserves Oracle's optionality. It costs almost nothing. And it removes the date anchor doing so much perception damage.
Publish a portfolio-level commitment. Oracle does not need to say JDE, PeopleSoft, E-Business Suite, Siebel, and Hyperion are strategically equal to Fusion. It does need to say Applications Unlimited is a durable portfolio category for customers whose industries, operating models, and investments make those systems the right fit.
Show up for local user groups. This is the lowest-cost, highest-signal move available. Send product people. Attend consistently. Provide modest funding. Make local groups feel connected to Oracle again. The goal is not to take control away from partners. It is to reconnect customers to the product organization.
Connect Applications Unlimited to OCI and AI. Oracle is already investing heavily in OCI and AI. Applications Unlimited customers should see a clear commitment that those investments will reach them too. The message should not be that JDE becomes Fusion. The message should be that JDE customers can benefit from Oracle's cloud and AI investments without giving up the application depth that made JDE the right system in the first place.
Strengthen partner economics. Partners are the natural growth channel for Applications Unlimited. Expanded co-marketing, better deal registration, stronger enablement, and targeted incentives for net-new opportunities would be far cheaper than rebuilding a direct sales motion. Partners also need confidence that Oracle wants them to grow, not simply maintain the installed base while platform economics move elsewhere.
Assign clear executive ownership. Applications Unlimited needs a named senior executive accountable for ecosystem health, not just maintenance performance. The metrics should include partner activity, net-new wins, talent pipeline, user group health, ISV participation, third-party support attrition, and customer confidence. If no one owns those metrics, the portfolio will keep looking healthier in financial reports than it feels in the field.
What Happens If Nothing Changes
The likely outcome is not collapse. It is thinning.
Partner practices continue to diversify away from JDE. The talent pipeline stays constrained. Consultant rates rise even as the total practitioner base shrinks. ISVs invest where they see growth. Third-party support providers keep attacking the maintenance base. Quest vendor attendance drops as partner ROI on conference sponsorship continues to deteriorate, putting financial pressure on the organization that holds the broader JDE community together.
These risks move slowly, but they compound.
Once a partner reallocates its best people to another platform, rebuilding that practice takes years. Once younger consultants stop entering an ecosystem, the skills gap takes a decade to repair. Once ISVs move their roadmaps elsewhere, ecosystem richness does not come back quickly.
By the time the damage is obvious in Oracle's reported numbers, it will be much more expensive to reverse.
The Bottom Line
Applications Unlimited was an elegant answer to a 2005 problem. It reassured acquired customers, protected maintenance revenue, and gave Oracle room to manage a complex portfolio.
But the mechanism has aged.
What once created confidence now creates ambiguity. Oracle has preserved the products technically while allowing the strategic story around them to weaken.
The fix is not complicated. It does not require Oracle to pretend JDE is Fusion. It does not require Oracle to make Applications Unlimited the center of the investor narrative. It requires clearer language, stronger ecosystem signals, better partner economics, and visible senior ownership.
JDE still has the product depth to serve the industries it was built for. It still matters to manufacturers, contractors, project-based businesses, real estate operators, distributors, and other companies whose requirements do not fit neatly into generic cloud ERP positioning.
The products are worth it. The customers are worth it. The ecosystem is worth it.
The fix is straightforward. The harder question is whether anyone at Oracle wants to make it.
If Oracle truly cares about its partner ecosystem, its user groups, and the middle market companies that depend on JD Edwards, someone inside the company needs to finally stand up. Stand up for the JDE customers who have been loyal for two and three decades. Stand up for the JDE partners who built their businesses around the product and are now being squeezed from every direction. Stand up for the local user groups holding the community together. Stand up for Quest's future as the gathering place that makes this ecosystem possible. And most of all, stand up for the mid-market manufacturers, contractors, and project-based businesses that need an ERP product that is not Fusion, not NetSuite, not SAP, and not Dynamics.
That product exists. It is JD Edwards. It has existed for decades. It is still the best fit for the segment it serves. And it deserves a vendor that says so out loud.
Personal analysis by John Mathieu, offered as one practitioner's perspective on a portfolio dynamic that does not get discussed enough. Originally published on LinkedIn. Substantive disagreement or alternative reads welcome.
