Short answer: JDE third-party support is independent maintenance for Oracle JD Edwards, delivered by a non-Oracle firm at roughly 50% of Oracle's 22% annual fee. You keep your perpetual licenses and get fixes, tax and regulatory updates, and a help desk for your existing version — but lose access to Oracle patches and new releases. It suits a frozen, stable JD Edwards estate, and the switch should be timed against your renewal and any cloud plans.
Key Takeaways
- JDE third-party support typically costs about 50% of Oracle's 22% fee, so an estate paying $440,000 a year to Oracle would pay roughly $220,000 to an independent provider.
- You keep the perpetual JD Edwards licenses you own — third-party support is a maintenance choice, not a licensing change.
- You give up Oracle patches, new releases, and portal access; the provider supports your frozen version with its own fixes and regulatory updates.
- Re-entry to Oracle support later carries reinstatement fees plus back-support for the lapsed period, so the switch is a multi-year commitment, not a one-year experiment.
- Across JD Edwards support reviews, the strongest third-party-support candidates are frozen estates consuming few Oracle patches, where the switch removes roughly half the annual maintenance spend (Oracle Licensing Experts, 2026).
What is JDE third-party support?
Short answer: JDE third-party support is software maintenance for Oracle JD Edwards provided by an independent firm instead of Oracle. The provider delivers bug fixes, tax and regulatory updates, security mitigations, and help-desk support for your existing version — typically at about 50% of Oracle's 22% annual fee, without access to Oracle's patches or new releases.
JDE third-party support is independent maintenance: you keep the perpetual JD Edwards EnterpriseOne or World licenses you already own, but you buy ongoing support from a specialist firm rather than from Oracle. Established providers in this market support your current, frozen version — writing their own fixes, delivering tax and regulatory updates, providing security mitigations, and running a help desk — for roughly half what Oracle charges. The licenses do not change; only who maintains them does.
This matters because Oracle's 22% fee is built on the assumption that you are continuously consuming the full support bundle — patches, new releases, and technical support. A mature JD Edwards estate running a frozen version often consumes almost none of that, yet pays the full rate. Third-party support exists precisely to close that gap. The economics of the fee it replaces are set out in JDE Support Costs & the 22% Fee, and the firm-wide view across all Oracle products lives in our Third-Party Support advisory.
How much does JDE third-party support save?
Short answer: Independent third-party support usually costs about half of Oracle's standard fee. Oracle charges 22% of net license value per year; third-party providers typically charge close to 50% of that, so an estate paying $440,000 a year to Oracle would pay roughly $220,000. The saving compounds because providers generally do not apply Oracle's annual repricing uplift.
The headline saving is roughly half the annual maintenance fee, but the compounding effect is larger than the first-year number suggests. Oracle reprices its 22% base upward by as much as 8% per year on renewal; most third-party providers hold their fee flat or close to it. Over a typical multi-year horizon, the gap between a rising Oracle line and a flat independent line widens every year, so the cumulative saving outpaces the simple 50% comparison.
| Factor | Oracle support | Third-party support |
|---|---|---|
| Annual fee | 22% of net license value | ~50% of the Oracle fee |
| Renewal uplift | Up to 8% per year | Typically flat / minimal |
| Bug fixes | Oracle patches | Provider's own fixes |
| New releases | Included (rights to download) | Not available |
| Tax / regulatory updates | Yes | Yes |
| Best fit | Active upgrade roadmap | Frozen, stable version |
The right figure for your estate depends on your net license value and current support invoice, which is why the saving should be modeled on your actual numbers rather than the headline percentage. Our Support Reduction service benchmarks the two paths side by side.
Our Third-Party Support advisory models the saving on your real numbers and protects your license position through the switch. See our manufacturing case study: $4.2M of cost and risk removed.
What do you give up with JDE third-party support?
Short answer: Leaving Oracle support means losing the right to download Oracle patches and new JD Edwards releases, plus access to Oracle's support portal. The provider supports your frozen version with its own fixes. The main consequence is that returning to Oracle later triggers reinstatement fees plus back-support, so the switch should be treated as a multi-year commitment.
The trade-offs are concrete and need to be weighed honestly rather than waved away. You lose three things: the right to download new JD Edwards releases, access to Oracle's official patch stream, and use of My Oracle Support. For a frozen estate that is not upgrading, none of those may be in active use — which is the whole point — but they are not zero-value, and the loss should be a deliberate decision.
The bigger consideration is re-entry. If you later decide to return to Oracle support — for instance because you choose to upgrade or move to a model that requires it — Oracle charges reinstatement fees plus back-support for the period you were away, which can erase part of the saving. This is why third-party support is a multi-year strategy, not a one-year cost cut: the decision only pays off if the estate genuinely stays frozen for the duration. The audit-posture implications of leaving Oracle support are covered in our Oracle Audit Defense Guide.
Is JDE third-party support legal and audit-safe?
Short answer: Yes. Using independent third-party support for JD Edwards is legal, and you keep the perpetual licenses you own. The conditions are that the provider must support you using your own entitlements and licensed materials, not Oracle intellectual property they have no right to distribute. A buyer-side review confirms the arrangement protects your license position.
The legality question comes up because Oracle's retention team raises it, not because the answer is in doubt. You own perpetual JD Edwards licenses; nothing in dropping Oracle support forfeits them. The boundary that matters is that the third-party provider must support you using materials you are entitled to — your own licensed software and documentation — and must not distribute Oracle-owned patches or code it has no right to. Reputable providers operate inside those lines and have done so for years.
The practical risk is not legality but audit posture. Oracle sometimes responds to a support departure with closer compliance scrutiny, so the time to clean up your license position is before you leave, not after. Reconcile your JD Edwards user counts, confirm the perpetual entitlements you are relying on, and document the position so that any subsequent audit meets a defensible estate. That forensic preparation is exactly what we do buyer-side — challenge Oracle's framing with evidence rather than accept it — through our Audit Defense service.
Get the JD Edwards Third-Party Support Decision Framework
The buyer-side framework we use to model the saving, check re-entry exposure, and protect your license position before leaving Oracle support — free from our research team.
When should you switch JD Edwards to third-party support?
Short answer: The strongest case is a stable, frozen JD Edwards version not being upgraded and consuming few Oracle patches or new releases. Timing should align with the support renewal date to avoid paying both, and any OCI or cloud plans must be checked because BYOL requires active licenses. Begin the evaluation six to nine months before renewal.
Three conditions make a JD Edwards estate a strong third-party-support candidate. First, the version is frozen — no upgrade on the roadmap that would require Oracle's new releases. Second, support consumption is low — few tickets, little patch activity, no reliance on the download library. Third, the estate is stable enough that a multi-year commitment is realistic. When all three hold, paying Oracle's full 22% is buying optionality you are not using, and the switch is straightforward economics.
Timing is the part buyers get wrong. The switch must align with your Oracle support renewal so you are not paying both Oracle and the new provider for an overlap. It also has to be checked against any cloud plan: a move to OCI under BYOL requires your licenses to stay active, and the support decision interacts with that, as set out in JDE on OCI vs On-Premise. Start the evaluation six to nine months before renewal, get a credible third-party benchmark on the table, and let it also serve as leverage in any final negotiation with Oracle — the mechanics of which sit in our Contract Negotiation service and the full estate strategy in the JD Edwards Licensing Guide.
How do you choose a JDE third-party support provider?
Short answer: Choose a JD Edwards third-party support provider on its track record with your specific version, its tax and regulatory update coverage for your jurisdictions, its security mitigation approach, and contractual clarity on IP boundaries. Run the selection buyer-side and independently, so the provider that best fits your estate is chosen on evidence, not the loudest sales pitch.
The provider market is established but not uniform, and the right choice depends on your estate. The selection criteria that matter: demonstrable experience supporting your exact JD Edwards version and modules; the breadth and timeliness of tax and regulatory updates for every country you operate in; a credible approach to security without Oracle's patches; and contract terms that keep the provider clearly inside the IP boundaries that make the arrangement safe. Service-level commitments and the transition plan from Oracle support round out the comparison.
Because we are independent and buyer-side — we do not resell any provider's service — we evaluate the options against your estate without an agenda. That neutrality is the point: the decision to leave Oracle support and the choice of who replaces it should both be evidence-based and unbiased. When you want that run for you, start with a confidential assessment from Oracle Licensing Experts.
The third-party-support decision framework, re-entry math, and the audit-posture checklist Oracle's retention team leaves out — free from our research team.
JD Edwards Third-Party Support FAQ
What is JDE third-party support?
JDE third-party support is software maintenance for Oracle JD Edwards provided by an independent firm instead of Oracle. The provider delivers bug fixes, tax and regulatory updates, security mitigations, and help-desk support for your existing JD Edwards version, typically at about 50% of Oracle's 22% annual fee, without access to Oracle's patches or new releases.
How much does JDE third-party support save?
Independent third-party support for JD Edwards usually costs about half of Oracle's standard fee. Oracle charges 22% of net license value per year; third-party providers typically charge close to 50% of that, so an estate paying $440,000 a year to Oracle would pay roughly $220,000. The saving compounds because third-party providers generally do not apply Oracle's annual repricing uplift.
What do you give up with JDE third-party support?
Leaving Oracle support means losing the right to download Oracle patches and new JD Edwards releases, and access to Oracle's support portal. The third-party provider supports your frozen version with its own fixes. The main consequence is that returning to Oracle support later triggers reinstatement fees plus back-support for the lapsed period, so the switch should be treated as a multi-year commitment.
Is JDE third-party support legal?
Yes. Using independent third-party support for JD Edwards is legal, and you keep the perpetual licenses you own. The key conditions are that the provider must support you using your own entitlements and licensed materials, not Oracle intellectual property they have no right to distribute. Reputable providers operate within these boundaries, and a buyer-side review confirms the arrangement protects your license position.
When should you switch JD Edwards to third-party support?
The strongest case is a stable, frozen JD Edwards version that is not being upgraded and consumes few Oracle patches or new releases. Timing should align with the support renewal date to avoid paying both, and any OCI or cloud plans must be checked because BYOL requires active licenses. Begin the evaluation six to nine months before renewal so the switch is deliberate, not rushed.
Does leaving Oracle support increase audit risk for JD Edwards?
Oracle sometimes applies closer compliance scrutiny after a customer leaves support, so the time to reconcile your JD Edwards license position is before the switch, not after. Confirm user counts and perpetual entitlements and document the estate so any subsequent audit meets a defensible position. The departure itself is legal; the discipline is preparing the evidence in advance.
Can I return to Oracle support after using a third-party provider?
Yes, but it is costly. Oracle charges reinstatement fees plus back-support for the period you were on third-party support, which can erase a meaningful share of the saving. This is why third-party support works best for estates genuinely committed to a frozen version for several years rather than those expecting to upgrade and return to Oracle support soon.
Model your JD Edwards support switch before Oracle's retention team calls
We model the saving on your real numbers, check re-entry exposure, and protect your license position through the switch — independent, buyer-side, built on 600+ engagements.