At INFOCUS 2026, we hosted a panel of IT leaders from across industries who are all navigating the same challenge: their most experienced JD Edwards professionals are approaching retirement, and the knowledge those people carry isn’t easy to replace. The panelists were candid that most organizations aren’t prepared to maintain operational continuity when the people who know the system best move on.
This conversation started with a single LinkedIn post that reached over 12,500 members and gained more than 28,000 impressions. It clearly struck a nerve — not because it’s a future-state problem companies should plan for, but because it’s happening right now in real JDE shops.
The good news is that this is solvable if you’re willing to act before the tribal knowledge disappears. This blog breaks down both a proactive approach for when you have time and a more urgent playbook for when you don’t.
What Tribal Knowledge Means in a JD Edwards Environment
Every JDE shop has some documentation. But tribal knowledge is found in the layer underneath — the things that never get written down because the people who hold them don’t even think of it as specialized knowledge anymore.
In most JD Edwards environments, this shows up as the developer who knows a custom business function was modified years ago to handle a tax edge case that would break invoicing is anyone reverted it. The analyst who manually adjusts records every month because an integration doesn’t handle a particular scenario correctly. The administrator who knows that one batch job has to run before another or the general ledger won’t balance.
This kind of knowledge spans across finance, distribution, manufacturing, and the technical infrastructure underneath it all. It also includes the history behind customizations, the dependencies between seemingly unrelated processes, and the informal rules that keep operations running.
The challenge is that the people who hold this knowledge don’t realize how much of it is theirs alone. They’ve been doing it so long it feels obvious — until the day that person is gone, and everything gets questioned.
The Cost of ERP Knowledge Management When Employees Leave
The impact rarely shows up all at once but rather surfaces gradually over time. A process that used to take an hour now takes days because no one knows the shortcut. An upgrade project stalls because the team can’t determine which customizations are still in use. An integration that no one fully understands breaks, and it takes weeks of reverse engineering to fix it instead of a simple phone call to the person who designed it.
With these gaps, organizations end up paying for the same knowledge twice. Once, when the original employee built it over years on the job, and again when a replacement must reconstruct it through trial and error or external support. And in a market where experienced JD Edwards professionals are increasingly hard to find, that reconstruction timeline keeps getting longer.
None of this is inevitable, but it requires treating knowledge transfer as a real business priority. The approach looks different depending on how much time you have to prepare.
Proactive JDE Knowledge Transfer Plan: When You Have Time to Make a Plan
If you have a planned retirement or reorganization on your calendar for the next few years, you have the advantage of building a structured approach before the pressure hits.
Start with a knowledge audit
Identify who holds critical knowledge of each module or process and map your single points of failure. If one person leaving would create a serious gap in your infrastructure, that’s where you focus first.
Run documentation sprints
Dedicate focused time for key people to document what they know — decision logic, exception handling, and the “why” behind configurations. A facilitator or consultant guiding these sessions helps ensure the output is usable going forward.
Build a cross-training program
Pair adjacent or junior-level staff with your senior JDE people for hands-on knowledge transfer over time. This “internal farm system” was one of the approaches our INFOCUS panel discussed, working to develop bench strength before you need it.
Baseline your configurations and customizations
Before any transition, document your current-state system, including custom code, integrations, orchestrations, and workflows. If it’s not written down somewhere, assume the person leaving is the only one who knows it exists.
Bring in a senior JDE consultant to work with your team
A dedicated consulting team who augments your existing staff learns the environment in real time while creating a strong safety net for the planned transition. This is core to how Surety Systems supports clients by absorbing institutional knowledge and ensuring continuity.
Urgent Knowledge Transfer Plan: What to Do When a Key JDE Employee Leaves
Unfortunately for some organizations, not every transition comes with a long runway to prepare. Sometimes you find out a critical person is leaving in weeks, not months. The goal here shifts from comprehensive knowledge capture to damage control that protects the highest-risk areas first.
Triage your knowledge gaps
With a shortened timeline, you can’t capture everything. Identify the processes, modules, and integrations that would cause the most operational damage if no one understood them.
Conduct quick extraction sessions
Plan reviews around specific modules and business processes and have the critical person show you every manual touchpoint in a critical integration. Record everything. The goal is to pull out as much actionable knowledge as possible in the compressed timeframe.
Begin a “what we don’t know” log
Accept that gaps will exist and create a living document where the team flags unknowns as they surface. This turns reactive discovery into a structures recovery process rather than a series of surprises during the next close cycle.
Lean on trusted JDE expertise
Leverage senior consultants who already know the JD Edwards platform and can stabilize operations and begin reverse-engineering undocumented processes. Our team at Surety Systems offers this on-demand support, stepping in with deep platform knowledge so your team isn’t starting from zero.
Protect Your JD Edwards Investment Before the Expertise Leaves
The JDE talent pool is shrinking, and the knowledge your most experienced people carry isn’t getting any easier to replace. But good news — this is a solvable problem whether you have a year to prepare or need urgent support.
If you want to hear how real IT leaders are navigating this firsthand, watch our full panel discussion from INFOCUS 2026.
If you’re dealing with this problem in your own organization, Surety Systems can help. Whether you need help creating a knowledge transfer plan, senior-level expertise to augment your team, or immediate support to fill a critical gap, we put the right people on the problem. Get in touch with our team today.
