Qualify before you write
Knowing an account runs JD Edwards, and which product line, tells you whether your offer is relevant before you spend a sequence on it. That is the difference between an ERP-specific pitch and a generic one.
Installed base view
See the JD Edwards Companies You Can Identify
Explore how JD Edwards user data can be organised by company, industry, location, technology environment and decision-maker.
Technology
JD Edwards
ERP TechnologyJD Edwards EnterpriseOneJD EdwardsJD Edwards World
Sample JD Edwards Installed Base View
Sample dataAtlas Manufacturing Group
Manufacturing
Dallas, TX
JD Edwards EnterpriseOne
NorthStar Distribution
Wholesale Distribution
Chicago, IL
JD Edwards EnterpriseOne
Summit Industrial Products
Industrial Manufacturing
Houston, TX
JD Edwards
Pacific Equipment Holdings
Industrial Equipment
Los Angeles, CA
JD Edwards EnterpriseOne
Harbor Point Construction
Construction and Engineering
Tampa, FL
JD Edwards EnterpriseOne
Cedar Ridge Foods
Food and Beverage
Minneapolis, MN
JD Edwards World
Technology Profile
Sample dataTechnology CategoryERP
VendorOracle
ProductJD Edwards EnterpriseOne
DeploymentOn-premises / cloud / hybrid, where known
IndustryManufacturing
LocationDallas, Texas, United States
CompanyAtlas Manufacturing Group
Technology tagging is confirmed before a record ships
Geographic Segmentation
Sample statesUnited StatesCanadaUnited KingdomIndiaAustraliaNetherlandsMexicoUnited Arab Emirates
Markers show a sample of states you can segment by, not a count of accounts in each. JD Edwards adoption is international, so lists can be cut by country and region as well as by US state and city.
Find JD Edwards Accounts
Technology
Industry
Country
State
Company Size
Job Title
City
Revenue
Technology Version
Deployment
Industry, country, state, city, company size, revenue band and job title are standard filters. Product edition and deployment model are captured where public evidence supports them, so treat those two as narrowing filters rather than fields present on every record.
Decision-Makers You Can Target at JD Edwards Accounts
CIOCTOIT DirectorVP of ITERP DirectorEnterprise Applications ManagerJD Edwards AdministratorERP ManagerIT ManagerCFO
These are the roles worth asking for when you market JD Edwards related products or services. They are not a promise that every record carries all ten titles; tell us which of them matter and we will scope the count against those titles.
01JD Edwards
02Companies using JD Edwards
03Company and technology intelligence
04Decision-makers
05Targeted B2B campaigns
The company names, technology profile and filter selections above are illustrative, used to show how the data is organised. They are not customer claims. Publicly documented JD Edwards users are named separately below, each with the source the claim rests on.
TL;DR
JD Edwards Installed Base: The Short Version
- A JD Edwards customers list is a set of organisations identified as running JD Edwards ERP, with the company, technology, location and contact detail available for each.
- Yes, organisations still run JD Edwards. Oracle commits Premier Support for JD Edwards EnterpriseOne 9.2 through at least 2037 and ships cumulative innovation to the 9.2 code line rather than forcing a major upgrade.
- There are two product lines to target differently: JD Edwards EnterpriseOne, the current line, and JD Edwards World, which moved to Sustaining Support in May 2025 and drives migration demand.
- Adoption concentrates in manufacturing, wholesale distribution, construction and engineering, energy and utilities, agribusiness, consumer products and real estate.
- The buying committee is IT and ERP led: CIO, IT Director, ERP Director, enterprise applications and CNC administrators, with the CFO joining on finance-touching projects.
- Records can be filtered by industry, country, state, city, company size, revenue band and job title. Product edition and deployment model are available where public evidence supports them.
What is it
What Is a JD Edwards Customers List?
A JD Edwards customers list is a collection of organisations identified as using JD Edwards ERP technology, together with the company, technology, geographic and contact information available for each of them. It tells you which companies run JD Edwards, what kind of business they are, where they operate and who inside them owns the ERP decision.
Businesses use that information to build target account lists rather than to blast a file. A consulting firm filters for JD Edwards manufacturers in a handful of states and pitches optimisation work. A cloud provider filters for JD Edwards accounts still running their own infrastructure. A staffing agency filters for JD Edwards accounts and offers CNC and developer contractors. A software vendor filters for the industries its product already serves and leads with an ERP integration story.
Every record carries a company profile rather than an email address on its own: company name, website and domain, industry, country, state and city, employee band, revenue band, and named contacts with title, business email, phone and LinkedIn where those are available. Field availability varies by record and by the dataset you select, which is why we scope a count against your filters before anything is delivered.
Custom list
Build a Custom JD Edwards Dataset
There is no single JD Edwards file to buy. Different campaigns need different cuts of the same install base, so the dataset is assembled against your brief and the count is confirmed before anything is delivered.
Pick the attributes that matter to your offer, tell us the titles you need, and we will come back with the achievable count and the field coverage for that exact segment. If a filter combination produces a list too thin to run a campaign against, we would rather tell you before you buy than after.
02Top customers
Companies That Use JD Edwards
Organisations whose JD Edwards usage has been publicly documented by Oracle, by conference and user-group material, by trade press or by the organisation's own hiring. The Evidence column names what each entry rests on. Sources were checked in August 2026; publicly documented usage is a point-in-time fact, so confirm current status before you build a campaign on any single name.
Campaign reach
Why Businesses Need JD Edwards Installed-Base Intelligence
A JD Edwards install base is a finite, identifiable set of accounts with a shared technical reality, which is what makes it a better campaign target than an industry list. Consulting firms use it to find organisations that may need functional or technical optimisation work. ERP migration specialists use it to find organisations weighing modernisation, particularly the ones still on JD Edwards World now that A9.4 has moved to Sustaining Support. Cloud providers use it to find JD Edwards accounts that still run their own infrastructure and would benefit from a lift to a managed platform.
The same list serves adjacent categories. Integration vendors target accounts that need JD Edwards connected to a CRM, an e-commerce front end, a warehouse system or a data platform. Cybersecurity vendors target organisations running mission-critical ERP where patch cadence, access control and audit are board-level topics. Managed service providers target accounts with complex ERP infrastructure and thin internal teams. Recruiting and staffing firms target organisations that will need CNC administrators, developers and functional analysts, a skill set with a genuinely tight supply. Training providers target the same accounts on the same trigger. Software vendors target organisations with an established ERP that they need to sit alongside rather than replace.
What all of these have in common is that the technology signal is the qualifier. Knowing an organisation runs JD Edwards tells you more about whether they will answer your email than knowing their revenue band does.
03Definition
What Is JD Edwards?
JD Edwards is an ERP suite founded in Denver, Colorado in March 1977 and named after its three founders, Jack Thompson, Dan Gregory and Ed McVaney. PeopleSoft acquired the company in 2003, and Oracle acquired PeopleSoft in January 2005, which is how JD Edwards became an Oracle product. Oracle sells and supports it today as Oracle JD Edwards, which is why searches for JD Edwards and for Oracle JD Edwards return the same software.
JD Edwards EnterpriseOne is the current line. It is the web-based product that grew out of OneWorld, and its modules cover financial management, discrete and process manufacturing, distribution and order management, supply chain, asset lifecycle management, project costing, real estate and home construction, agriculture, rental management, transportation management and human capital management. Release 9.2 is the current code line, and Oracle now delivers innovation as cumulative updates to 9.2, branded by year (Release 25, Release 26 and so on) rather than as disruptive major upgrades.
JD Edwards World is the older line. It descends from the original WorldSoftware written for IBM midrange hardware and runs on IBM i, the platform many teams still call the AS/400. It remains in production at organisations that never moved to EnterpriseOne, but its most recent release, A9.4, moved from Extended Support to Sustaining Support on 1 May 2025, which changes the calculus for the organisations still on it.
Organisations choose and keep JD Edwards for the same reasons in most cases: it handles mixed-mode manufacturing and complex distribution well, it has deep asset, project and real estate functionality that generic ERP lacks, it can be configured and extended heavily, and it runs on a stack the team already knows. That depth is also why replacing it is a multi-year decision rather than a purchase.
04Adoption
Which Companies Use JD Edwards?
JD Edwards concentrates in asset-heavy and inventory-heavy industries, and in organisations large enough to need real ERP but not so large that they standardised on a single global suite. In practice that means discrete and mixed-mode manufacturers, wholesale distributors, construction and engineering firms, industrial equipment makers, energy and utilities operators, agribusinesses, food and beverage producers, consumer products companies, real estate and property operators, mining and metals businesses, automotive suppliers, chemical processors and transportation operators.
Each of those maps to a specific reason for the fit. Manufacturers use JD Edwards because it handles discrete, process and mixed-mode production in one system. Distributors use it for advanced pricing, warehouse and order management. Construction and engineering firms use it for job costing, subcontractor management and the home construction and real estate modules. Energy, utilities and mining operators use it for asset lifecycle management and capital projects. Agribusinesses use grower and blend management, which very few ERP suites offer at all. Real estate operators use the property management and lease administration modules.
The company-size profile is distinctive. JD Edwards accounts cluster in the middle of the enterprise market, with the densest band from roughly 500 to 5,000 employees, where there is a real ERP team but not the standardisation pressure of a global conglomerate. Very large enterprises appear too, usually running JD Edwards in a division, a region or a recently acquired business alongside another ERP, which is a segment worth targeting separately because the buying trigger is consolidation rather than replacement.
05Adoption
What Industries Use JD Edwards?
JD Edwards adoption follows its module strengths. The industries below are ordered by how densely the suite appears in them, with the functional reason for the fit.
A relative read of the table above. Bars show adoption density, not a share of any published customer count.
Discrete and Mixed-Mode Manufacturing
Very High
Wholesale Distribution
Very High
Construction and Engineering
Very High
Industrial Equipment and Machinery
High
Energy, Oil and Gas
High
Utilities
High
Consumer Products
High
Food and Beverage
High
Agribusiness
High
Real Estate and Property Management
High
Mining and Metals
Moderate–High
Automotive Suppliers
Moderate–High
Chemicals and Process Manufacturing
Moderate–High
Transportation and Logistics
Moderate
Pharmaceuticals and Life Sciences
Moderate
Professional and Field Services
Moderate
Manufacturing and distribution are the two densest clusters, and they are dense for a functional reason: JD Edwards handles discrete, process and repetitive production in one code line, and its advanced pricing and warehouse modules are more capable than most mid-market ERP alternatives.
Construction, engineering and real estate are structurally over-represented relative to the suite's overall market share, because JD Edwards has dedicated home construction, real estate management and contract billing modules that most competitors either lack or bolt on through partners.
Agribusiness is the most under-appreciated segment for vendors. Grower management and blend management are close to unique in mainstream ERP, so the growers, processors and cooperatives running JD Edwards have very few alternatives, which makes them long-tenured accounts and strong targets for adjacent software rather than replacement.
Asset-intensive industries such as energy, utilities and mining cluster around JD Edwards asset lifecycle management and capital project functionality. These accounts buy maintenance, mobility, IoT and integration services more readily than they buy ERP replacement.
Where JD Edwards appears inside very large enterprises, it is usually a divisional or regional deployment rather than the global standard. Target those accounts on consolidation, integration and reporting rather than on optimisation.
Product adoption
JD Edwards EnterpriseOne vs JD Edwards World
Buyers search for both names, and they are not interchangeable. EnterpriseOne is the current product line; World is the older IBM i line. Support status is the field that matters commercially, because it is what moves an account from steady state into a project.
Oracle reviews the EnterpriseOne Premier Support date annually and has extended it repeatedly, so confirm the current commitment before quoting it in a campaign. Sustaining Support keeps access to existing fixes and support tools but does not include new updates or new regulatory and certification work, which is what makes World accounts a distinct segment rather than a subset of the EnterpriseOne base.
06Geo coverage
Where JD Edwards Companies Are Located
JD Edwards has a genuinely international installed base, with concentrations that follow industrial and agricultural economies rather than software-buying centres.
The United States is the deepest market by a wide margin, which is unsurprising for a suite founded in Denver and sold through a North American channel for its first two decades. Most campaigns should start with a US cut and expand outward.
The Middle East is worth a dedicated campaign for construction and engineering vendors specifically. JD Edwards has a long history with contractors and developers in the Gulf, and the project costing and contract billing modules are the reason.
India, Australia and South Africa concentrate around asset-heavy industries, mining, metals and engineering, where the asset lifecycle management modules do the work. Vendors selling maintenance, mobility and reliability tooling should treat those three as one campaign segment.
European adoption is more selective than in North America, sitting mainly in food and beverage, horticulture, distribution and industrial manufacturing rather than across the board. Segment Europe by industry rather than by country to avoid a thin list.
07US footprint
JD Edwards Adoption Across US States
US concentration tracks industrial and agricultural density rather than population, which is why the map does not look like a list of the largest states.
Texas and California are the two largest single-state segments and are worth splitting further by metro. Houston and Dallas skew to energy, industrial equipment and construction; the Central Valley and Los Angeles skew to agriculture, food and consumer products.
The industrial Midwest, Ohio, Michigan, Indiana, Wisconsin and Illinois, is the densest manufacturing block in the JD Edwards installed base. If you sell to manufacturers, these five states plus Pennsylvania will usually outperform a national list on reply rate.
Colorado deserves a line of its own. JD Edwards was founded in Denver, the local partner and consulting ecosystem is unusually deep, and the state's energy, construction and utility base fits the suite well.
08Segmentation
JD Edwards Adoption by Company Size
The JD Edwards installed base sits in the middle of the market. Understanding where it thickens tells you which of your offers will land.
Relative adoption density by employee band. Bars compare bands against each other, not against a published customer count.
Under 100 employees
Low
100 to 499 employees
Moderate
500 to 999 employees
High
1,000 to 4,999 employees
Very High
5,000 to 9,999 employees
High
10,000+ employees
Moderate–High
The 500 to 5,000 employee band is the core of the installed base and the best starting segment for almost any JD Edwards campaign. Below 500 employees, budgets are thinner and the IT team is often one or two professionals, so lead with managed services and packaged offers rather than transformation. Above 10,000 employees, JD Edwards is usually one ERP among several, so lead with integration, consolidation, reporting and coexistence rather than with optimisation of a system the account may already be planning to retire.
09Buyer titles
JD Edwards Decision-Makers Worth Targeting
JD Edwards buying committees are IT-led and unusually stable, because the same professionals often own the system for a decade or more. These are the roles to ask for, subject to what is available for a given account.
Multi-thread from the start. The ERP Director or enterprise applications manager will tell you whether a project is realistic, the CNC administrator will tell you whether it is technically possible, and the CIO or CFO will decide whether it is funded. Campaigns that touch only one of those three stall in evaluation. On migration and modernisation offers, the CFO matters earlier than most vendors expect, because the trigger is usually a support or infrastructure cost conversation rather than a functional gap.
10Tech stack
The Technology Stack Around JD Edwards
JD Edwards rarely sits alone. Knowing the surrounding stack tells you what else an account has already bought and where the integration conversations start.
Compared
JD Edwards Compared With Other ERP Install Bases
If you sell into ERP install bases generally, it helps to know how the JD Edwards cohort differs from its neighbours in shape rather than in size.
We do not publish per-platform install-base counts, because a credible global figure does not exist for most on-premises ERP suites and an invented one would be worse than silence. What the comparison is for is choosing which cohort to run first: JD Edwards rewards vendors selling into manufacturing, distribution, construction and asset-heavy operations at mid-enterprise scale, which is a different motion from selling into the SAP or Oracle EBS enterprise base.
11Benefits
What a JD Edwards Installed-Base List Lets You Do
Segment by the thing that matters
Cut the base by industry, country, state, city, company size and revenue band, then layer job title on top. A JD Edwards manufacturer in Ohio with 1,200 employees is a different conversation from a JD Edwards property operator in Dubai.
Time the outreach to a real trigger
Support status changes, cloud migrations and code-currency programmes are the events that create budget. Segmenting World accounts separately from EnterpriseOne accounts lets you write to the trigger instead of around it.
Run account-based marketing properly
A defined technology cohort is what ABM needs: a finite named account list, multiple titles per account, and a shared context that makes personalised messaging possible at scale.
Feed the CRM without guesswork
Records arrive with firmographics, technology tagging and named contacts in a CRM-ready format, so your team can route, score and sequence them rather than re-researching each one.
Size the market honestly
A count built against your actual filters tells you whether the segment supports a campaign at all. That is more useful, and more honest, than a headline number that includes accounts you would never sell to.
Who buys this list
How to Build a JD Edwards Target Account List
The workflow below is the one that produces campaigns worth running. It takes about an hour of thinking before any data changes hands, and it is the difference between a list and a target account list.
01
1. Identify JD Edwards users
Start from the technology signal rather than from an industry or a revenue band. The install base is the constraint; everything after this narrows it.
Use case: Filter: Technology = JD Edwards. Decide now whether EnterpriseOne, World or both fit your offer.
02
2. Select geography
Set the countries, states and cities you can actually service, sell into and follow up in. Geography is the filter most teams set too wide.
Use case: Filter: Country, state, city. Field sales should cut to metros; inside sales can go national.
03
3. Select industry
Choose the industries where your reference customers already are. Manufacturing, distribution, construction and agribusiness behave differently enough to deserve separate messaging.
Use case: Filter: Industry, SIC or NAICS. One industry per campaign, not four.
04
4. Define company size
Employee band predicts ERP team size, deal size and sales cycle better than revenue does. Set it against the deal you can actually close.
Use case: Filter: Employee band, revenue band. The 500 to 5,000 band is the densest part of the base.
05
5. Identify relevant decision-makers
Name the two or three titles that will decide, and the one that will block. Ask for those specifically rather than for a seniority level.
Use case: Filter: Job title. For example ERP Director plus CNC Administrator plus CIO.
06
6. Segment the accounts
Split the resulting list into tiers by fit and by trigger, so the highest-value accounts get a different treatment from the long tail.
Use case: Tier 1 gets research and personalisation; tier 2 gets a segment-level sequence.
07
7. Build personalised outreach
Write to the segment's actual situation. A World account on Sustaining Support and a code-current EnterpriseOne account have almost nothing in common.
Use case: One message per segment, referencing the product line, industry and the specific problem.
08
8. Prioritise high-value accounts
Work the accounts where the technology fit, the size band and the trigger all line up first, and let the rest run on automation.
Use case: Multi-thread tier 1 accounts across all three titles before touching tier 2.
If you want, send us the brief rather than the filters. Describe who you sell to and what problem you solve, and we will propose the segmentation and confirm the count against it.
12Buyer use cases
Who Should Buy JD Edwards Customer Data?
Oracle partners and JD Edwards consultancies
Find organisations that may need functional or technical consulting, code currency work, module rollouts or optimisation. Segment by product line and industry so the first email names a problem the account actually has.
ERP migration and modernisation firms
Target organisations weighing a move, with JD Edwards World accounts as the clearest segment now that A9.4 sits in Sustaining Support. Avoid inferring migration intent from product age alone; use it to prioritise, then qualify in the conversation.
System integrators
Reach accounts that need JD Edwards connected to CRM, e-commerce, WMS, MES or a data platform, and that need someone to own the programme end to end.
Cloud providers and hosting partners
Identify JD Edwards organisations still running their own infrastructure, or running it in a data centre they want to exit. Infrastructure cost and disaster recovery are the two openings that work.
Managed service providers
Target accounts with complex ERP infrastructure and a small internal team, where 24x7 support, patching and environment management are a genuine constraint.
Cybersecurity vendors
Reach organisations running mission-critical ERP where access control, patch cadence, segregation of duties and audit evidence are board-level concerns.
Data integration and analytics vendors
JD Edwards data is valuable and awkward to get at. Vendors selling pipelines, warehousing, reporting and BI have a clear, specific problem to lead with.
Enterprise software vendors
Sell alongside rather than against. Planning, quality, field service, e-commerce, tax, expense and procurement tools all land better when the pitch acknowledges the ERP the account intends to keep.
Recruitment agencies and IT staffing firms
JD Edwards CNC administrators, developers and functional analysts are scarce. Organisations running the suite are the entire addressable market for that skill set.
Training providers
Target the same accounts on the same trigger. Upgrades, tools releases and Orchestrator adoption all create demand for structured training.
13Data dictionary
What Information Can Be Available?
The fields below are what a JD Edwards installed-base record can carry. Availability varies by record and by the dataset you select, so treat this as the menu rather than a guarantee that every field is populated on every row. We confirm which fields are populated for your specific segment when we scope the count.
14Trust signals
Why Source JD Edwards Data From BizzContacts
Technology-first, not industry-first
The install base is built as a technology cohort, so JD Edwards is a filter in its own right rather than something inferred from an industry list.
Product lines kept separate
EnterpriseOne and World are different commercial situations, and the data reflects that rather than flattening both into one JD Edwards tag.
Counts before commitments
You get the real count for your filter combination before you buy. If the segment is too thin to run, we will say so.
Named contacts, not role inboxes
Records carry named individuals with titles, so multi-threading across the ERP, IT and finance buying committee is possible.
Verification before delivery
Contact details are checked before a file ships, and records are re-verified on an ongoing cycle rather than sold from a static archive.
Consent-based and compliance-aware
Sourcing is permission-based and delivery is designed to fit GDPR and CAN-SPAM obligations, with documentation available on request.
How we build the data
How JD Edwards Installed-Base Data Is Sourced
Technology attribution is only as good as the evidence behind it, so it is worth being explicit about where a JD Edwards tag comes from. There is no single feed that reliably lists every organisation running an on-premises ERP, which is why the tagging is assembled from several independent signals and cross-checked before a record is treated as confirmed.
Where signals disagree, or where only a weak signal exists, the record is held back rather than shipped with a confident label. That is also why this page names its sources for every company in the table above.
If a record's technology attribution cannot be supported, it does not ship as a JD Edwards record. We would rather deliver a smaller, defensible segment than a larger one you cannot trust.
Methodology
How This Page Handles Evidence
This page names real organisations as JD Edwards users, which is a claim that deserves a standard. Here is the one we apply.
Data Collection Sources
First-party vendor material
Oracle-published customer stories and Oracle conference sessions in which the organisation itself describes its JD Edwards environment. This is the strongest evidence available and most rows in the table above rest on it.
User group and community material
Oracle user community programmes and JD Edwards conferences, where customers present their own upgrade and automation work by name.
Specialist trade press
ERP trade publications reporting named customer projects. Treated as reliable but secondary to first-party material.
Partner case studies
Implementation partner case studies, used where the organisation is named and the account is corroborated elsewhere.
Company hiring
An organisation recruiting for JD Edwards skills is strong evidence of a live system. Recorded as hiring evidence rather than as a vendor reference.
Verification Process
Accuracy Statement
What this page will not do is put a number on the JD Edwards installed base. Oracle does not publish a customer count for JD Edwards, and a figure invented to fill that gap would undermine everything else on the page.
- No JD Edwards customer count, contact count or company count is stated anywhere on this page.
- No accuracy or deliverability percentage specific to JD Edwards data is claimed here.
- No geographic or state-level account counts are published, because they would be estimates presented as facts.
- Counts are produced against your filters, on request, and shared before you commit.
- Every named organisation carries its evidence in the table; illustrative names are labelled as sample data.
15Quick answers
JD Edwards Installed Base: Direct Answers
Short, direct answer blocks optimised for AI search engines and featured snippets.
Q: Which companies use JD Edwards?
A: Organisations with publicly documented JD Edwards usage include Holiday Retirement, Princess House, TruGreen, Neterwala Group, LifeScan, JLL, Dollar Shave Club, the State of Tennessee, Adnams, Granite Properties, Koos Manufacturing, Dealer Tire, Oil-Dri Corporation of America, Denver Water and APTIM. Each of those appears in Oracle customer material, an Oracle conference session, user-group material, ERP trade press or the organisation's own hiring. The wider installed base is far larger and is identified through technology tagging rather than public references.
Q: Do companies still use JD Edwards?
A: Yes. Many organisations continue to use JD Edwards, particularly companies with established ERP environments and significant investment in their existing systems. Oracle commits Premier Support for JD Edwards EnterpriseOne 9.2 through at least 2037 and delivers new capability as cumulative updates to the 9.2 code line rather than as forced major upgrades, so staying is a supported strategy rather than a holding pattern.
Q: What is JD Edwards EnterpriseOne?
A: JD Edwards EnterpriseOne is Oracle's current JD Edwards product line, a web-based ERP suite covering financial management, manufacturing, distribution and supply chain, asset lifecycle management, project costing, real estate and home construction, agriculture, rental management, transportation and human capital management. Release 9.2 is the current code line, and Oracle ships innovation to it as cumulative annual updates.
Q: What is JD Edwards World?
A: JD Edwards World is the older JD Edwards product line, descended from the original WorldSoftware and running on IBM i, the platform often still called the AS/400. Its most recent release, A9.4, moved from Extended Support to Sustaining Support on 1 May 2025, which means access to existing fixes continues but new updates and new regulatory and certification work do not.
Q: What is the difference between JD Edwards and Oracle JD Edwards?
A: There is no difference in the software. JD Edwards was an independent company founded in Denver in 1977; PeopleSoft acquired it in 2003, and Oracle acquired PeopleSoft in January 2005. Oracle has sold and supported the suite ever since, so Oracle JD Edwards is simply the vendor-qualified name for the same products.
Q: What industries use JD Edwards most?
A: Discrete and mixed-mode manufacturing, wholesale distribution, and construction and engineering are the densest. Industrial equipment, energy and oil and gas, utilities, consumer products, food and beverage, agribusiness, and real estate and property management follow. The pattern tracks JD Edwards module strengths in manufacturing, distribution, job costing, asset management and property.
Q: What size companies use JD Edwards?
A: The installed base is weighted toward the middle of the enterprise market, densest between roughly 500 and 5,000 employees. Smaller organisations appear, often on JD Edwards World or a lean EnterpriseOne footprint, and very large enterprises typically run JD Edwards in a division, region or acquired business alongside another ERP.
Q: Can I get a list of companies using JD Edwards ERP?
A: Yes. BizzContacts maintains JD Edwards as a filterable technology cohort, so a list can be built for the industries, countries, states, cities, company sizes and job titles you specify. Rather than publishing a fixed count, we confirm the achievable count for your exact filters before you commit.
Q: Can I target JD Edwards users by industry?
A: Yes. Industry is a standard filter, with SIC or NAICS classification available on most records, so you can restrict a campaign to manufacturers, distributors, construction and engineering firms, agribusinesses or any other segment where your product already has references.
Q: Can I target JD Edwards companies by location?
A: Yes. Country, state or region, and city are all standard filters. US campaigns can be cut to state or metro level for field sales, and the installed base extends well beyond North America into Canada, the UK, India, Australia, the Netherlands, Mexico and the Gulf.
Q: Can I identify IT decision-makers at JD Edwards companies?
A: Yes. Job title is a standard filter, and the roles most worth asking for are CIO, CTO, IT Director, VP of IT, ERP Director, Enterprise Applications Manager, ERP Manager, JD Edwards or CNC Administrator, IT Manager and CFO. Contact availability varies by account, so the count is confirmed against your title list before delivery.
Q: Can I filter JD Edwards accounts by product line or deployment?
A: Where the evidence supports it, yes. Product line, EnterpriseOne or World, and deployment model, on-premises, cloud or hybrid, are captured where public evidence establishes them. Treat both as filters that narrow a list rather than as fields guaranteed on every record.
Q: How many companies use JD Edwards?
A: Oracle does not publish a JD Edwards customer count, and we will not invent one. Third-party estimates circulate but vary widely and rarely explain their method. What we can tell you is the count for a defined segment: give us the industries, geographies, sizes and titles you want, and we will confirm the number for that brief.
Q: Is JD Edwards being discontinued?
A: No. Oracle sells and supports JD Edwards EnterpriseOne today, has extended the Premier Support commitment for release 9.2 repeatedly, and currently commits to at least 2037. Oracle also markets its own cloud applications to the same customers, so many JD Edwards organisations are actively weighing whether to stay, extend or move, which is what makes the installed base commercially interesting.
Q: Why do organisations stay on JD Edwards?
A: ERP lifecycles are long, and JD Edwards estates tend to carry years of configuration, custom objects, integrations and process dependencies. Data migration is complex, retraining is expensive, and the functional depth in manufacturing, distribution, job costing, agriculture and property is hard to replace. With Premier Support running into the late 2030s and innovation shipping to the existing code line, staying is often the rational choice rather than the default one.
16Search insights
People Also Ask About JD Edwards
17FAQ
JD Edwards Customers List FAQs
Why act now
JD Edwards Campaign Examples That Work
JD Edwards consulting campaign. Target JD Edwards accounts in manufacturing, in a defined set of states, with IT leadership and ERP management titles, in the 500 to 5,000 employee band. This works because manufacturing is where JD Edwards functionality is deepest and where accumulated customisation makes optimisation work an easy business case. Lead with a specific functional problem, shop floor visibility, costing accuracy, EDI reliability, rather than with a capability list.
ERP migration campaign. Target JD Edwards World accounts and organisations running older EnterpriseOne releases, with CFO and IT Director titles. The trigger is real and public: World A9.4 moved to Sustaining Support on 1 May 2025, so new updates and new regulatory work are no longer part of the deal. Do not infer that an account is planning to migrate simply because its product line is old. Use the support status to prioritise who to talk to, then let the conversation establish intent.
Cloud modernisation campaign. Target JD Edwards accounts with IT leadership and infrastructure titles, focusing on organisations running their own hardware or exiting a data centre. Oracle's own customer stories are dominated by exactly this move, which makes the reference material easy to assemble. Lead with infrastructure cost, performance and disaster recovery rather than with the word transformation.
JD Edwards staffing campaign. Target organisations using JD Edwards with IT and ERP management titles, filtered to the industries and geographies your contractors can serve. The pitch writes itself: CNC administrators, developers and functional analysts are hard to hire, and the organisations that need them are precisely the ones running the suite. Segment by product line, because World and EnterpriseOne skills are not interchangeable.
18Full technology index
Every Technology Users Database Inside BizzContacts
Browse every install-base and technographic database BizzContacts maintains. Every link below points to a live BizzContacts landing page with verified customer records, decision-maker contacts, and buyer-center intel for that platform, updated on a continuous verification cycle.
142 technology users databases covered. Every entry links to a verified install-base landing page with buyer contacts.