How Long Does a JDE to SAP Migration Actually Take?
The answer nobody publishes.
The SI says 12 to 18 months. Oracle's SOAR methodology says 20 weeks. Gartner puts complex ERP transformations at 18 to 36 months. Analysts who have watched S/4HANA migrations closely note that only 8% complete on the original schedule.
75%
ERP Failures
8%
S/4HANA On Schedule
90 days
Collapse Pattern
38.4%
Pre-Migration Capacity Loss
The honest answer is that it depends on something none of those estimates account for: whether your team can actually show up for the build.
The Three Timelines Running Simultaneously
| Timeline | Duration | What It Measures |
|---|---|---|
| SI Timeline | 12-18 months | The project plan presented to the board |
| Operational | 18-30 months | How long JDE must keep running |
| Human | ~90 days | When the team hits the wall |
The SI timeline. Sprint schedules, configuration workshops, testing cycles, proposed go-live date. For mid-market JDE-to-SAP migrations, typically 12 to 18 months.
The operational timeline. How long your JDE environment needs to keep running at full production quality. Includes pre-migration data remediation and post-go-live stabilization. Realistically: 18 to 30 months end-to-end.
The human timeline. How long your core team can sustain two full workloads before quality degrades or people start leaving. From what we've seen: about 90 days before the cracks appear. This is the timeline nobody models.
The 90-Day Collapse Pattern
Days 1–30: Adrenaline carries both workstreams. Status reports are green. The SI's workshops are well-attended.
Days 31–60: Reactive JDE work starts winning. The SI's data requests get delayed. Workarounds replace root-cause fixes.
Days 61–90: Something breaks. A production incident consumes the SMEs the SI depends on. The project's first timeline extension gets approved. The team's strongest people start updating their resumes.
The cost of a two-week timeline extension in a complex ERP migration is not two weeks. It is the compounded cost of rescheduling, re-baselining, and re-approving a project that is now visibly behind.
Why SI Estimates Are Structurally Optimistic
Across 62 Fortune 500 environments, the median percentage of core team time consumed by reactive operations is 38.4%. At 60% effective availability for SAP-focused work, a 12-month SI timeline becomes 18 to 22 months of calendar time.
For context on how capacity constraints play out across ERP migrations, see Why ERP Migrations Fail.
SAP-Specific Complexity Factors
Business Partner data model. SAP S/4HANA requires converting customers, vendors, and contacts into a unified Business Partner structure. For JDE environments with decades of Address Book data, this conversion alone can require 6 to 12 months of data remediation work.
Clean Core. SAP's extensibility philosophy is more restrictive than what JDE allows. JDE customizations need to be evaluated one by one.
Cultural and operational shift. JDE and SAP have different operational philosophies, navigation models, and support paradigms. Training and change management are almost always underscoped.
Honest Timeline Ranges
| Complexity | SI Timeline | Operational Timeline | With Airlock |
|---|---|---|---|
| Simple (< 3 modules) | 12-18 months | 18-24 months | SI timeline holds |
| Mid (3-5 modules) | 18-24 months | 24-30 months | SI timeline holds |
| Complex (global, multi-plant) | 24-36+ months | 30-42 months | SI timeline holds |
"Before committing to a timeline, measure your team's actual capacity. Not headcount. That number determines how long your migration will take."
Without an Operational Airlock, add 30 to 50 percent to each range.
The Variable That Changes Everything
One thing separates migrations that finish close to schedule from migrations that don't: whether someone else is handling JDE production while the build happens.
The W.L. Gore migration: over 24 months, 26,518 JDE service interactions handled with zero escalations to the SAP build team. 25 FTEs freed. The migration finished on schedule. See W.L. Gore Field Report.
Before committing to a timeline, measure your team's actual capacity with a Pre-Migration Health Check.
Find out where your team stands.
Model your migration timeline accurately.
Take the Executive Diagnostic →