Full disclosure before I start: my company provides production support for JD Edwards, for thousands of users around the world, so "stay on JD Edwards" is a conclusion I profit from. I know that. So I am not going to ask you to trust me. I am going to tell you a story, give you the facts, and let you decide.
There is a conversation happening in boardrooms right now. A consultant clicks to a slide, and the slide says your ERP is a dead end. You are behind, you are exposed, you need to modernize before you are stranded. Everyone in the room nods, because everyone knows it is true.
What if everyone in the room is wrong? Not about the dead end, that part is true. About everything that comes after it.
Something strange has happened in enterprise software. The safest place to be is now a product nobody is trying to sell you anymore, and the most dangerous place to be is the shiny new thing everyone is racing toward.
I have spent three articles on how that cage gets built: the boardroom that sets your roadmap , the maintenance bill that was always a bond , and the door to your own data that is becoming a market . This is the one about the way out. And it starts, like most things in enterprise software, with a hostile takeover.
It started with a hostile takeover
Twenty years ago Oracle wanted PeopleSoft. PeopleSoft did not want to be wanted. What followed was one of the ugliest takeover fights in tech history, and when Oracle finally won, in early 2005, it did something that told you exactly what kind of marriage this was going to be. It fired about five thousand PeopleSoft employees almost immediately. A year later it swallowed Siebel too.
Now put yourself in the customer's chair. You had bought PeopleSoft, or JD Edwards, or Siebel, and the company that made your software just got eaten by a giant famous for one thing: making you buy the giant's software instead. Everyone assumed Oracle would kill these products and force the migration. Customers started eyeing the exits. Some started calling SAP.
So Oracle did something to calm them down. In 2006 it made a promise and gave it a name: Applications Unlimited. The promise was simple. We will keep supporting these products. We will keep enhancing them. We will not force you off. Run them as long as you like. It worked. The panic stopped, the customers stayed, and they kept paying. From Oracle's side it was a masterstroke. A leash, dressed as a gift.
The leash became a lifeboat
Because the world moved to the cloud, and the cloud turned out to be a cage. When your ERP lives in the vendor's cloud, you do not choose where it runs, you do not hold the keys to your own data, and you cannot walk away from the bill. The vendor owns the door, and lately it has started charging you to walk through it to reach your own records. And the one group immune to all of it is the group Oracle put on a leash in 2006.
Here is the twist that makes it almost too perfect. Oracle today is the most aggressive data-landlord in the business. Its chairman gets on stage and brags that Oracle's databases hold most of the world's most valuable private data. Oracle would love to pull its JD Edwards and PeopleSoft customers into its cloud right now and meter every byte. It cannot, because of a promise it made in 2006 to keep them calm. The company most desperate to build the cage is the one contractually holding the door open.
If you think this is just a clever story, look across the aisle at SAP. SAP never made that promise, and SAP is doing the exact thing Oracle cannot: marching its entire base off its own ERP, on a hard 2027 deadline, with no reprieve. JD Edwards, meanwhile, is supported past 2037, and that date keeps moving out. Same industry, opposite fate, and the only difference is a promise one vendor made and the other never did.
Neglect is the new freedom
So here is the rule underneath all of this, because it is bigger than JD Edwards. When a vendor modernizes a product today, that word means one thing: it moves the product into SaaS, where the vendor takes control. And that is expensive. You have to rebuild the whole thing. So vendors only do it to the products they intend to keep as the future.
Which means the products they will not modernize are the ones they can no longer control. A product your vendor will not rebuild as SaaS is a product it cannot cage.
Say that back to yourself, because it inverts twenty years of instinct. The system you were taught to be embarrassed about, the legacy one, the one with no roadmap, is the one thing in your building the vendor cannot take from you.
Now, I promised you honesty, so here it is. JD Edwards has no future as a product. Oracle keeps it patched and current, but it is never being reborn as a modern cloud suite. It is a dead end. When I say stay, I am not telling you it has a roadmap. I am telling you it has something better. It has no leash.
But what about AI?
Fair. JD Edwards is not getting the AI Oracle is stuffing into its flagship, and that sounds like the reason to leave. It is the reason to stay.
Two things. First, that AI is not free. SAP already charges for it by the unit. Oracle gives it away inside Fusion, which sounds generous until you see why: the AI is the bait to get your data into its cloud. Free or metered, you pay.
Second, and this is the one that matters, the AI you actually want was never going to live inside your ERP anyway. The value of AI in a business is reasoning across everything at once, your finance and your operations and your customers, not the sliver trapped in one app. Even Oracle admits this; its whole pitch is tearing down the walls between your data so the models can see all of it. It is right. It just wants that to happen inside its cloud. But if you own your data, and JD Edwards lets you, you can point the best models in the world at all of it yourself, without anyone's permission or meter. The company with no AI in the ERP is the company free to do AI the right way.
And here is the question that should stop the migration cold. If AI is about to hollow out the application layer, the screens and the workflows and the forms, why would you spend three years and millions of dollars moving onto a brand-new application suite? You would be making your biggest bet on the layer AI is about to make matter least, and giving up your data and your control to do it. The boring move is the smart one: keep your data, keep your costs low, and wait to see what AI actually does before you bet the company on a migration you cannot take back.
We have been here before
Step back far enough and the whole thing is a circle. For forty years the industry told us to get off the mainframe. Stop renting time on someone else's machine. Own your systems, run them yourself, hold your own data. So we did; we spent a generation moving off the glass house.
Then SaaS marched us right back into it: a vendor's data center, a vendor's machine, your software on it, and a bill that scales with every person who logs in. We did not modernize past the mainframe. We rebuilt it and handed back the keys. The shops that never left the own-it era are not behind. They kept the one thing the last forty years were supposed to be about.
What you actually do with this
You stop apologizing. You stop treating JD Edwards as a problem to escape and start treating it as the position of strength it is. You own your infrastructure, your data, and your support bill. Run it on-premise and that last one has teeth: stop paying maintenance and Oracle cannot do a thing, because you own the license and possess the software. In SaaS, a missed payment is a light switch. Almost nobody left in enterprise software still holds that kind of leverage.
And then you do the one thing that turns a nice idea into money. You drive the cost of running it down, hard, every year. Because a dead-end product does not hurt you by breaking. It hurts you by quietly getting more expensive until you are spending everything just to keep the lights on, with nothing left to fund a move on your own terms. Compress that cost and the missing future stops being a threat and becomes optionality. You migrate when you decide it is worth it, or you run lean and free for another decade. Your call, not the vendor's.
For twenty years we felt sorry for the JD Edwards customers. The laggards. The ones who did not modernize. It turns out they were the ones who got away.
Oracle was too busy harvesting JD Edwards to lock it in a cage, and that indifference is now the most valuable thing you own. You are not stranded. You are standing on the last safe harbor in enterprise software, one your own vendor built by accident and cannot take back. Do not flee it. Play it.
