The people who know your JD Edwards system best are the ones who configured it, customized it, and have built decades of undocumented tribal knowledge about why it works the way it does. The issue? These people are retiring, and the talent pool behind them is thin.
At INFOCUS 2026, we brought together a panel of IT leaders navigating this challenge and explored four approaches to protecting your ERP investment (we broke down all four in The JD Edwards Talent Crisis: How to Manage Institutional Knowledge Risk.) One stood out for its long-term value and simplified transition: the internal “Farm System.”
In baseball, farm systems develop raw prospects into major-league-ready players, so the roster can be replenished. The same principle applies to your internal JDE team, as structured internal training and promotion is designed to build bench strength before you actually need it. This post is the playbook for how to make it work in your organization.
Why JD Edwards Tribal Knowledge is Disappearing
JD Edwards has been a workhorse ERP system for over two decades, but the people who know it best are beginning to leave the workforce. When they go, they take with them the same tribal knowledge that rarely lives in documentation:
- Why specific configurations exist
- How custom workflows were built
- What workarounds are in place
- What business logic is embedded in current integrations
The talent pool of JDE experts is shrinking on both ends, with fewer new professionals entering the landscape and the experienced ones retiring or moving on. Unlike newer cloud-native platforms with eager candidate pools, replacing deep JDE expertise takes patience to find the right fit. This only compounds as senior people leave, and the remaining team absorbs more load, leading to quicker burnout and more departures.
The organizations in the strongest position aren’t the ones scrambling to backfill after a resignation. They’re the ones who started building internal strength before they needed it.
Understanding the Farm System Approach to JDE Cross-Training
In baseball, a typical farm system doesn’t wait for a starter to retire and then scramble to find a replacement. It identified promising talent early, develops them through structured coaching, and moves them up so that when a roster spot opens, there’s always someone ready. Your JDE team should work the same way.
This approach allows organizations to identify the people who hold critical JD Edwards knowledge (i.e., your “starters”) and pair them with existing team members who have relevant skills, ERP aptitude, or strong business process understanding (i.e., your “prospects.”) The goal here isn’t to clone your senior person but rather distribute knowledge across multiple people at different stages of readiness, so no single departure leaves a gap.
What separates this from the ad-hoc training most organizations default to is structure. A typical farm system approach has defined stages, milestones, documentation deliverables, and accountability standards. It treats JDE knowledge transfer as a strategic initiative instead of a side project that seems to always get deprioritized.
How to Plan a JD Edwards Knowledge Transfer Program
1. Conduct a Knowledge Audit
- Map every critical JDE function, module, and integration your organization depends on
- Identify who holds the knowledge for each key function
- Flag single points of failure, or any areas where only one person understands the configuration, custom code, or business logic
- Assess the urgency of the knowledge holders’ retirement, departure, or role change
2. Assess Your Current Talent
- Determine who on your existing team has relevant skills that could be developed toward senior JDE competency
- Consider IT staff with ERP experience on other platforms, business analysts who know the processes outside of the system, help desk or support staff who already troubleshoot JDE issues at the surface, and “super users” who are minor experts in their JDE functions
- Rate each prospect’s aptitude, willingness, and capacity to take on JDE learning alongside their current responsibilities
3. Define Your Readiness Level
- For each key JDE function, define core levels of awareness, competency, and ownership to ensure the replacement personnel can understand what it does, operate and troubleshoot issues, and modify and train others as needed
- Set target timelines for moving prospects through each level
- Set realistic timelines, as JDE knowledge typically takes 12-24 months to develop
4. Build the Roadmap
- Prioritize knowledge transfer by risk: highest-risk areas, like a single knowledge holder close to retirement, get addressed and resourced first
- Sequence the training program so prospects aren’t overwhelmed
- Build in checkpoints and practical assessments to gauge knowledge absorption and readiness to lead each function
If you’re working with a longer runway, our guide to building a JDE tribal knowledge transfer plan before retirement walks through both proactive and urgent playbooks depending on your timeline.
Organizing Your JDE Mentorship Program
Create the Mentor-Prospect Pairing
- Pair each senior mentor with one or two prospects for individual knowledge transfer
- Define the relationship clearly with scheduled time blocks, specific modules to cover, and expected outcomes of each phase
- Give mentors protected time outside of their daily tasks for knowledge transfer
Build a Documentation Framework
- Ensure critical JDE knowledge is captured and stored for future reference
- Build standardized templates for documenting system configurations and their use case, custom code and modification history, integration maps, and other business process workflows with JDE-specific steps
- Make documentation a deliverable of the mentoring process, where the prospect writes the documentation as they learn and the mentor reviews for accuracy
Formalize the Learning Path
- Break each JDE function into learning modules with clear, specified objectives
- Use a progression model that allows prospects to shadow, assist, lead with oversight, and eventually own each function independently
- Include hands-on practice in a sandbox or test environment for critical JDE configurations or workflows
- Build in real-world scenarios and break/fix exercises where prospects troubleshoot simulated issues
Secure Executive Support
- Ensure proper investment from support staff: time from senior mentors, reduced productivity during ramp-up, potential need for external support to backfill while mentors are training
- Frame this to leadership as risk mitigation: the cost of running a farm system is a fraction of the cost of losing critical JDE knowledge with no succession plan
- Secure a trusted executive sponsor who can protect the program when competing priorities try to pull mentors back to actual production work
Sustaining ERP Knowledge Transfer & Avoiding Common Pitfalls
The farm system approach offers a unique operating model that allows organizations to stay updated when new hires, role changes, and system updates create fresh knowledge transfer needs across teams. This program should be built into your team’s quarterly knowledge audits, annual roadmap refreshes, and ongoing mentor assignments that evolve as people grow.
And like any strategic business initiative, it needs measurement. Track prospect progressions through module competency checks. Monitor how much of your JDE landscape is documented versus still stuck in one person’s head. Watch how many areas have moved from single-person dependency to real multi-person coverage. Collect feedback from both mentors and prospects. A program that checks the boxes without actually transferring knowledge is just overhead.
Avoiding Common Pitfalls
- Treating it as a side project: If mentors don’t have dedicated time, knowledge transfer gets deprioritized when more urgent production issues arise.
- Documentation without context: Documentation that simply says “click here, then there” without explaining why doesn’t transfer knowledge; it transfers button sequences.
- Waiting too long to start: The best time to build a farm system is before you actually need it. Organizations that wait until a key person gives notice are already behind. Be proactive.
- Ignoring mentor experience: Senior JDE professionals who are asked to train their replacements should feel valued and included, not phased out. Position the farm system as legacy-building rather than sunset planning.
- Doing it alone: While the farm system is designed to build internal strength, strategic external partnerships can accelerate the process, fill gaps during ramp-up, and provide additional expertise you may not have in every module.
Protecting Your JDE Investment
The JDE talent crisis doesn’t have to be a crisis, but it becomes one when organizations wait. The farm system approach takes effort upfront, but it’s the only approach that compounds over time. Every person you develop, process you document, and knowledge gap you close makes your organization more resilient than it was before.
Surety Systems provides senior consultants to accelerate the farm system approach, strategic staff augmentation to backfill the ramp up period, and guidance on building a knowledge transfer roadmap from scratch.
Ready to talk through your JDE talent strategy? Contact us for a conversation about where you stand and what’s possible.
