The most experienced JD Edwards professionals in your organization are approaching retirement, and the institutional knowledge they carry about your ERP environment isn’t something you can fill with a normal job posting.
This blog breaks down why JDE environments are uniquely vulnerable to knowledge loss, what it costs when key personnel leave, and critical approaches to closing the gap before it becomes a crisis.
Why the JDE Talent Crisis is Accelerating in 2026
Most organizations running JD Edwards don’t miss out on their ERP investment in a single event. They lose it gradually through retirement, resignation, and unreplaced roles, until the people who understand why the system works the way it does are gone.
This issue is happening in the current JD Edwards landscape and the community sees it. When we posted a single LinkedIn update ahead of our INFOCUS 2026 panel session, it reached over 12,500 members and generated more than 28,000 impressions. IT leaders from large organizations across various industries joined us onstage to talk through what they’re seeing firsthand related to current talent gaps.
The signal was clear: this is one of the most urgent, yet widely unaddressed risks in the JDE ecosystem right now. And for most organizations, the window to act is narrower than they think.
What Makes JDE Environments Vulnerable to Tribal Knowledge Loss
Every ERP system accumulates institutional knowledge over time, but JDE environments are uniquely exposed for a few reasons.
Many JDE implementations have been running for 15-25+ years
Over a span of that many years, layers of customization, orchestrations, integrations, and other business-rule modifications have been built on top of the base system, often by the same people. The logic behind those decisions rarely lives in actual documentation, but rather in the heads of the two or three people who built them.
The JDE talent pool is not replenishing itself
Newer ERP professionals tend to have more specialized knowledge in cloud-native platforms. The deep, module-level JDE expertise that organizations depend on across finance, distribution, and CNC administration is concentrated in a shrinking group of senior professionals. Many of these individuals are within a few years of retirement, and most have no replacement in place to ensure none of their knowledge is lost in the transition.
Smaller JDE shops have no backup
In many smaller JDE landscapes, there’s one person managing the entire system, and they’ve often been embedded in every area of the business for 20 or more years. This makes this person a single point of failure for retirement, an unexpected departure, or any scenario where they’re suddenly unavailable. And because the role has grown around that person for years, there’s no clean job description to recruit against, making it more difficult to find a proper replacement.
JDE environments carry a heavier load of undocumented workarounds
Custom reports, modified business processes, and manual data handling steps often exist because someone years ago solved a problem with the tools they had available at the time, and no one ever wrote it down. That person became the only one who knows why a batch job runs at a specific time, why a particular UBE was modified, or how an integration was structured together.
The Business Cost of Losing Key JD Edwards Personnel
The most apparent cost of losing a senior JDE resource is the open headcount — recruiter fees, months-long searches, ramp time for a replacement who may never fully close the gap…But the deeper costs are the ones that don’t show up on a staffing report.
Operational disruption
When the person who understands a critical integration or custom modification leaves, you don’t just lose a team member. You lose the ability to troubleshoot and maintain that part of the system. Issues that used to take hours to resolve now take days or weeks, if they get resolved at all.
Stalled projects
Upgrades, migrations, and optimizations depend on context: why things were built a certain way, what was tried before, what constraints shaped past decisions. Without that critical context, project teams either slow down to reverse-engineer the environment or move forward on incomplete information.
Regression in system performance
Undocumented workarounds and manual processes tend to break silently when the person managing them is no longer there. Month-end close procedures, reporting logic, and data handling steps that ran smoothly for years can start producing errors that no one on the remaining team actually knows how to trace or fix.
Compliance exposure
Regulatory and audit requirements depend on accurate, repeatable processes. When tribal knowledge leaves, the organization may not realize that a critical process was being maintained manually by one person until an auditor flags it.
Compounding re-learning costs
One of the most underappreciated costs is when institutional knowledge walks out the door, your organization pays to relearn what it already knew prior. External consulting support, internal discovery efforts, and trial-and-error troubleshooting consume the budget and time that could have been avoided with a more proactive knowledge transfer strategy.
Limited viable replacement options
This challenge is most often seen in smaller organizations where a single person has owned the system for years. A “like-for-like” replacement for someone who has spent the past 20 years absorbing every detail of the JDE system usually doesn’t exist in the typical job market. The knowledge they carry has never been scoped into an easily transferrable role, but it’s been accumulated over time and shaped by hundreds of decisions and workarounds. Without documentation of this knowledge and proper transfer to the replacements, organizations lose both an employee and capability that may take years to rebuild.
4 Approaches to Closing the JDE Talent Gap
During the INFOCUS 2026 panel session, the discussion centered on four distinct strategies for managing JDE talent risk. Each carries its own tradeoff, and the right choice depends on where you are currently in your timeline.
1. Outsourcing JD Edwards Support to a Managed Services Partner
Handing full ownership of day-to-day JDE support and maintenance to an external partner provides immediate coverage and eliminates single points of failure. The tradeoff is control — organizations must ensure the partner understands their environment deeply enough to maintain the institutional context.
2. Senior JDE Consulting for 1:1 Knowledge Transfer
Augmenting internal team members with a senior consultant who provides ongoing guidance, coaching, and hands-on support serves as a bridge strategy. This keeps operations stable while actively building internal capability. This approach works best when there’s still overlap, so the person leaving and the incoming support team can work side by side.
3. Building a Cross-Training and Mentoring Program
Developing bench strength from within by cross-training staff and pairing junior team members with senior internal mentors is the most sustainable long-term approach. But it requires the amount of time that most organizations underestimate. The window to start a cross-training program is while the expert is still available, not after they’ve given their notice.
4. Hiring Experienced Talent Externally
Recruiting experienced JDE professionals directly is still an option, but the market reality makes it increasingly difficult. The reality is that the pool of senior JDE talent is shrinking, competition for qualified candidates is increasing, and the lead time to find and onboard the right person can often stretch beyond what most organizations can afford to wait.
Most organizations will need a combination of these approaches, but the key is to start before the pressure hits and be realistic about how long each strategy takes to deliver results. For a closer look at the timeline and structure of a successful knowledge transfer plan, check out our latest post on capturing and keeping JDE tribal knowledge.
How to Start Assessing Your JDE Knowledge Risk Today
Start with an honest inventory of your JDE landscape. How many people can troubleshoot your most critical JDE processes? Is the logic behind your custom modifications and integrations documented anywhere other than someone’s memory? What happens to your month-end close if your most experienced JDE person gives two weeks’ notice tomorrow?
If your answers to any of those questions are uncomfortable, you’re not alone. At Surety Systems, our senior-level JDE consultants work alongside your team to absorb institutional knowledge, stabilize operations, and build the internal capability you need to move forward.
