Oracle Is Cutting 30,000 Jobs. What That Means If You Run JDE, EBS, or PeopleSoft.

The narrative in the press has been that AI is replacing Oracle's workers. That framing is incomplete at best.

Oracle is not cutting 30,000 people because AI can do their jobs. Oracle is cutting 30,000 people because it needs the cash to build data centers.

The company has committed to $50 billion in debt and equity raises in calendar year 2026 alone to fund its AI infrastructure buildout. It has signed a $300 billion agreement with OpenAI. It needs to build the physical facilities — power, cooling, networking, GPU clusters — to fulfill those contracts.

The data centers are not yet profitable. Wall Street analysts project Oracle will not achieve positive cash flow from these investments until approximately 2030. The layoffs are the funding mechanism for the gap between now and then.

"The use of AI coding tools inside Oracle is enabling smaller engineering teams to deliver more complete solutions to our customers more quickly."

— Oracle co-CEO, Q3 FY26 Earnings Call

That is a real efficiency gain. But the primary driver of 30,000 cuts is not efficiency — it is capital allocation.

The people being cut are not being replaced by AI. They are being replaced by concrete, copper, and GPUs.

Oracle has not published a division-by-division breakdown. But analyst assessments and internal reporting provide a reasonably clear picture.

"The pressure will fall heaviest on legacy application suites, overlapping corporate functions, and some international operations."

— Abhishek Singh, Partner, Everest Group

Singh added that "on-premises support and lower-margin infrastructure services could be candidates for carve-outs or divestitures, as Oracle sharpens its focus on hyperscale AI."

"I don't feel that this will impact customers, but it will impact partners."

— Akshara Naik Lopez, Senior Analyst, Forrester

She added that Oracle carries significant corporate "bloat" from years of acquisitions and overlapping functions.

Teams already confirmed as affected include:

• OCI's Enterprise Engineering division
• Fusion ERP
• Data center operations technicians
• Technical project management

Oracle has also internally announced a review of open job listings in its cloud division — effectively freezing hiring.

The pattern is clear: Oracle is consolidating around AI infrastructure and cloud services while deprioritizing legacy application investment, on-premises support, and international operations.

If you run JD Edwards, E-Business Suite, or PeopleSoft, here is what you need to understand.

Your platform is not being discontinued.

Oracle has extended Premier Support for JDE EnterpriseOne 9.2 through at least 2036. E-Business Suite and PeopleSoft carry similar long-duration support commitments. The lights stay on.

But "lights on" is not the same as "invested in."

"CIOs should be asking: is the Oracle stack I depend on at the center of the company's next S-curve, or sitting at the periphery?"

— Abhishek Singh, Partner, Everest Group

JDE, EBS, and PeopleSoft are not at the center of Oracle's next S-curve. Oracle Cloud Infrastructure and AI are.

That does not mean Oracle will abandon these platforms. It means the pace of innovation, the depth of support staffing, the responsiveness of product teams, and the volume of new functionality will likely decrease over time. Not because Oracle wants to neglect these customers, but because 30,000 fewer employees means fewer people available to work on anything — and the remaining headcount will be disproportionately allocated to the areas Oracle is betting its future on.

Forrester has warned for years that Oracle customers running legacy applications should be evaluating the declining value proposition of Oracle's support and maintenance against alternatives. The layoffs accelerate that calculation.

The Practical Risks for Legacy ERP Customers

• Slower response times on support tickets as Oracle's support organization operates with fewer people.
• Fewer new features and less new functionality for legacy product lines, as development resources are redirected.
• Reduced investment in partner enablement which affects the ecosystem of firms that implement and support these platforms.
• Potential divestiture of legacy product lines — Singh explicitly noted that "parts of its legacy applications portfolio" could be "sold off."
• Increased pressure to migrate to Fusion Cloud as Oracle's strategic interest in keeping legacy customers on legacy platforms diminishes.

Oracle's layoffs are releasing tens of thousands of experienced enterprise technology professionals into a job market that was already contracting for specialized ERP talent.

This has a dual effect.

Short-term opportunity: Organizations that have struggled to hire JDE, EBS, or PeopleSoft specialists may find a temporary increase in available talent. Former Oracle employees with deep platform knowledge are entering the market. For organizations that need to backfill critical roles or build internal capability, the next 6–12 months represent a hiring window.

Long-term acceleration of the talent crisis: The layoffs signal to the broader labor market that Oracle is deprioritizing legacy platforms. Early-career professionals deciding where to invest their skills will interpret this as confirmation that JDE, EBS, and PeopleSoft are not growth paths. The training pipeline — already thin — will contract further.

The CNC administrator role, the JDE functional analyst, the EBS technical developer — these are already disappearing specialties. Oracle cutting 30,000 people does not create more of them. It creates a short burst of availability followed by a steeper long-term decline.

Organizations that do not have a talent strategy for their legacy ERP operations — a plan that accounts for knowledge concentration, succession risk, and the shrinking labor pool — are now operating with less margin for error than they had last quarter.

"I don't feel that this will impact customers, but it will impact partners."

— Akshara Naik Lopez, Senior Analyst, Forrester

This matters because most JDE, EBS, and PeopleSoft customers do not interact with Oracle directly for day-to-day operational support. They work through a partner ecosystem — managed services providers, consulting firms, staff augmentation shops — that depends on Oracle's investment in partner enablement, certification programs, training materials, and co-marketing.

When Oracle reduces investment in legacy platforms, the partner ecosystem follows. Smaller partners lose access to technical resources. Training programs shrink. Certification pathways become less relevant. The firms that remain in the ecosystem consolidate — and the ones that leave do not come back.

Oracle first took the infrastructure and sys admin work away from partners with the push to SaaS. That was a business model shift — the work moved from partner-managed on-premises environments to Oracle-managed cloud environments.

Now Oracle is cutting the people who do the work internally. The work did not move to a new model. It is being eliminated to fund a different business entirely.

For customers who depend on the partner ecosystem for JDE, EBS, or PeopleSoft support, the question is no longer "which partner should we work with?" It is "how many partners will still be doing this work in three years?"

The 30,000-job cut does not change your platform's support timeline. It changes the environment around your platform — the talent availability, the vendor's attention, the partner ecosystem's depth, and the long-term trajectory of investment.

First, assess your vendor dependency.

Map every touchpoint where your operations depend on Oracle — support tickets, patches, regulatory updates, Tools Releases, technical guidance. Determine which of those touchpoints are at risk if Oracle's support organization operates at 80% of its current staffing. Identify which ones you can absorb internally or through a partner, and which ones represent genuine operational risk.

Second, hire now if you need to hire.

The next 6–12 months will see a temporary influx of experienced Oracle professionals into the job market. If you have been struggling to fill JDE, EBS, or PeopleSoft roles, this is the window. It will not stay open.

Third, evaluate your support model.

If your current support depends heavily on Oracle's direct support organization — rather than a partner or internal team — you are now more exposed than you were. Consider whether a co-managed model with an independent partner provides more operational resilience than relying on a vendor that is actively reallocating resources away from your platform.

Fourth, document your institutional knowledge.

The risk that Oracle's layoffs create for your organization is not just about Oracle's people. It is about what happens when the broader ecosystem — Oracle's teams, the partner network, the labor market — has fewer people who understand your platform. The knowledge that lives in your internal team's heads is now more valuable and more fragile than it was. Document it. Systematize it. Do not let it depend on individuals who could leave.

Fifth, build your decision framework.

If Oracle divests a legacy product line, if support response times degrade, if your primary partner exits the ecosystem — what is your plan? These are not hypothetical scenarios. They are structurally more probable than they were before the layoffs were announced. Define your triggers and your responses now, while you have time to plan rather than react.