The bottom line
The structural decision that shapes every downstream variable — timeline, cost, disruption, and technical debt.
Before you pick a platform, pick a path
Before selecting a platform or an SI, your organization needs to decide how it will migrate. This decision shapes every downstream variable — timeline, cost, disruption, and technical debt. Most JDE companies encounter these terms for the first time during vendor demos, which means the SI is already framing the conversation.
Understanding the trade-offs independently — before any vendor relationship creates bias — is what Stage 1 advisory exists for. The three approaches below are not good, better, best. They are structural choices with distinct cost profiles, risk signatures, and organizational prerequisites.
The wrong path doesn't just cost money — it burns 18-36 months of organizational energy on an approach that doesn't fit the business. Getting this right before the SI's preference shapes the conversation is the highest-leverage decision in the entire lifecycle.
Greenfield — total re-engineering
Start with a blank slate. Design every process from modern best practices. No data migration of historical transactions — only master data moves forward. All technical debt is eliminated.
Best For
- Organizations ready to fundamentally redesign operations
- Companies where JDE customizations have created more problems than they solved
- Situations where the legacy process design is the bottleneck, not the platform
Trade-Offs
- Longest timeline — typically 24-36 months
- Highest change management burden — every user relearns their workflow
- Highest risk of scope creep — "blank slate" invites endless design debates
- Requires the most capacity from the client team
Brownfield — system conversion
Lift existing processes and data into the new platform. Historical transactions, configurations, and workflows are converted rather than redesigned. The fastest path with the least user disruption.
Best For
- Organizations that need speed and continuity
- Companies where existing processes are sound but the underlying platform is the constraint
- Situations with regulatory or audit requirements that mandate historical data accessibility in the new system
Trade-Offs
- Carries over technical debt — outdated configurations and inefficient processes
- The new platform inherits yesterday's problems
- Data mapping complexity is highest — every legacy field must reconcile with the target schema
Bluefield — selective transformation
A hybrid approach. Retain critical, specialized customizations (often in manufacturing, supply chain, or industry-specific workflows) while redesigning core areas (finance, HR, procurement) for the modern platform.
Best For
- Complex JDE footprints with legitimate, business-critical customizations that don't exist natively in any target platform
- Organizations that need modernization without the full disruption of greenfield
- Companies with 15+ years of JDE investment where not everything should be thrown away
Trade-Offs
- Requires the most sophisticated planning — you're making keep/redesign decisions on hundreds of processes
- The SI must be experienced in selective transformation (many are not)
- Dual-run periods are longest — legacy and modern processes coexist during the transition
We do not perform implementations — the SI executes the migration regardless of which path you choose. Allari's role in Stage 1 is to help your organization understand which approach fits your business complexity before the SI's preference shapes the conversation.
Whichever path you choose, someone has to keep the current JDE running while the migration is underway. In Stage 3, the same team holds that continuity through the dual-run window — where legacy and new systems run side by side — so the project doesn't cannibalize production stability and your people stay on the migration instead of being pulled back to keep the lights on. Because that accountability carries across the project boundary, there's no support-team handoff gap on day 91.
The full framework
This decision is one component of the 6-stage JDE Lifecycle Framework. Understanding greenfield vs. brownfield vs. bluefield is Stage 1 work — but the decision has implications for every stage that follows.
Not sure which path fits?
A working session includes a migration methodology assessment. We'll evaluate your business complexity, customization footprint, and team capacity against all three approaches.
Related Reading
What happens 90 days after ERP go-live
JDE to Fusion: Not an upgrade
Why ERP Migrations Fail
