On this page
- What is Oracle Agile PLM?
- When does Oracle Agile PLM support end?
- Does Agile PLM for Process end on a different date?
- What actually changes after December 2027?
- What are the options for Oracle Agile PLM customers?
- How long does a PLM transition take?
- How do you decide which option fits?
- Frequently asked questions
What is Oracle Agile PLM?
Oracle Agile PLM is an on-premise product lifecycle management platform. Oracle acquired it through the Agile Software Corporation acquisition and sold it for two decades into manufacturing, high-tech, medical devices, and process industries. It manages product records, bills of material, change orders, quality processes, and supplier data.
Agile PLM for Process, sometimes shortened to P4P, is the process-industry extension. It adds formulation, specification, and regulatory data structures used by food and beverage, cosmetics, and other formula-based manufacturers. It runs on its own release and support schedule.
Oracle Fusion Cloud PLM is a separate, cloud-native product. It is not an upgrade path from Agile PLM. It has a different architecture and a different data model, so moving to it is a re-implementation rather than a version upgrade.
TAKEAWAY:Agile PLM and Fusion Cloud PLM are two different products. Any move between them is a new implementation, not an upgrade. |
| Milestone | Date | What it means |
|---|---|---|
| Premier Support ends | December 31, 2027 | Agile PLM 9.3.x moves to Sustaining Support. No new patches, security fixes, or critical-bug updates. |
| Agile PLM for Process ends | May 2027 | Premier Support for P4P 6.2.4 ends seven months before the core platform. |
| Final release | Already confirmed | Version 9.3.6 is the last release. Oracle removed 9.3.7 from the roadmap in October 2023. |
Sources: Oracle Agile PLM Roadmap and the Oracle Lifetime Support Policy. Dates verified August 2026.
TAKEAWAY:Two dates, not one. Confirm which applies to your contract before you plan anything else. Teams running Agile PLM for Process have seven months less runway than they may assume. |
Does Agile PLM for Process end on a different date?
Yes. Agile PLM for Process 6.2.4 has Premier Support through May 2027, per Oracle’s published roadmap. The core Agile PLM platform runs to December 31, 2027.
This matters most in food and beverage, cosmetics, and other formula-based manufacturing, because P4P is where formulation, specification, and regulatory data structures live. Those are the records with the longest audit tails and the hardest migration profile.
TAKEAWAY:If your regulatory and formulation data sits in Agile PLM for Process, your planning window closes in May 2027, not December 2027. |
| Area | What changes |
|---|---|
| Security | No new security patches. Any vulnerability disclosed after the date has no vendor fix. |
| Defects | No critical-bug updates. Defects found after the date stay in the system. |
| Regulatory content | No platform updates to reflect new regulation. PPWR, MoCRA, FSMA 204, and anything that follows land on a static platform. |
| Integrations | No Oracle support for integration issues with ERP, LIMS, or other connected systems. |
| Escalation | No Oracle support tickets and no escalation path to Oracle engineering. |
| Talent | Agile PLM specialists become harder to source and more expensive to retain as the platform ages. |
For regulated manufacturers, the operational question is narrower than the technical one. An auditor is not asking whether the system runs. An auditor is asking whether product data integrity can be demonstrated on a platform that no longer receives security patches.
TAKEAWAY:The risk is not downtime. It is an unpatched system of record holding regulatory data, and whether that position is defensible under audit. |
What are the options for Oracle Agile PLM customers?
Keep running the platform as-is. Lowest immediate cost and no migration risk. You accept an unpatched system, frozen regulatory capability, and a shrinking talent pool. Generally hardest to defend in regulated environments, and hardest to sustain the longer it runs.
Option 1: Stay on Agile PLM under Sustaining Support
Keep running the platform as-is. Lowest immediate cost and no migration risk. You accept an unpatched system, frozen regulatory capability, and a shrinking talent pool. Generally hardest to defend in regulated environments, and hardest to sustain the longer it runs.
Option 2: Third-party support
Independent providers offer support for Oracle products past end of Premier Support, typically at lower annual cost. This extends the runway and buys planning time. It does not add capability, and it does not update the platform for new regulation. Best understood as a way to buy time, not a destination.
Option 3: Move to Oracle Fusion Cloud PLM
Oracle positions Fusion Cloud PLM as the path forward for Agile customers. It keeps the relationship with a single vendor. It is a re-implementation rather than an upgrade, so workflows, integrations, and governance are rebuilt rather than carried across. Whether it fits depends heavily on your integration landscape and on how much of your process-industry capability sits in P4P today.
Option 4: Move to an alternative PLM platform
If the platform is being re-implemented either way, the evaluation is genuinely open. This is the moment to ask whether the next system should be selected on vendor continuity or on fit with how your organization actually develops regulated products.
TAKEAWAY:Three of the four options require a full implementation. Once that is true, vendor continuity stops being a shortcut and becomes one criterion among several. |
| Phase | Planning assumption |
|---|---|
| Evaluation and selection | 6 months to 2 years |
| Implementation and data migration | 9 to 18 months, depending on complexity and deployment model |
| Parallel run and cutover | 2 to 4 months |
| Buffer | 3 to 6 months. Assume at least one scope or timeline adjustment |
These are planning assumptions, not benchmarks. Ask every vendor to confirm the timeline for an organization of your size.
Run the arithmetic backward from your own date. If Premier Support ends December 2027 and a full transition takes 12 to 24 months plus buffer, a funded evaluation needs to start by Q3 2026. If you are on Agile PLM for Process, that window has already closed on the comfortable end.
TAKEAWAY:Deployment model is the variable most teams underestimate. Ask every vendor who performs the implementation, how long it takes, and which reference customers will confirm both. |
How do you decide which option fits?
Three questions separate the options faster than any feature comparison.
- How much regulatory exposure sits in the platform? The more product data drives labeling, claims, and market compliance, the harder Sustaining Support is to defend.
- How many systems does your PLM connect to, and how many are non-Oracle? Integration breadth is the strongest predictor of migration cost and risk.
- How much of your product data would you migrate as-is today? If the honest answer is not much, the audit comes before the vendor decision.
This is the question many teams skip. Migrating unreliable data into a new platform does not solve the problem; it reproduces it at higher cost.
NEXT STEP:Audit before you evaluate. The Oracle Agile PLM Transition Checklist sets out what product data to audit, which regulatory workflows to protect, and what to ask any vendor. When you are ready to fund the move, the Oracle Agile PLM Replacement Business Case Template structures the internal case. |
Frequently Asked Questions
Does Oracle Agile PLM stop working after December 2027?
Is there a version after 9.3.6?
No. Oracle removed version 9.3.7 from the Agile PLM roadmap in October 2023, making 9.3.6 the final release.
Will Oracle extend the December 2027 date?
Nothing published indicates an extension. Plan against the published dates and treat any change as upside rather than assumption.
What is the difference between Premier Support and Sustaining Support?
Premier Support includes new patches, security fixes, and critical-bug updates. Sustaining Support does not. Existing fixes and documentation remain available.
Does the May 2027 date apply to everyone?
Only to customers running Agile PLM for Process. If you are on the core Agile PLM platform, your date is December 31, 2027. Confirm which applies to your contract.
Can we stay supported past 2027 without migrating?
Third-party support providers offer support for Oracle products past end of Premier Support. This extends the runway. It does not add platform capability or update the system for new regulation.
About Trace One Devex PLM
Trace One Devex PLM is a product lifecycle management platform for food and beverage, cosmetics and personal care, consumer packaged goods, and chemicals manufacturers. It supports project and portfolio management, formulation, product development, regulatory compliance and labeling, packaging management, supplier collaboration, quality management, and analytics, deployed by Trace One’s own professional services team. Regulatory coverage spans legislation sources across 85+ countries, including more than 400 vertical and horizontal guidelines and 2 million restrictions. This capability is supported by a global team of 25+ regulatory professionals working across 14 languages.
Disclaimer: This page references published Oracle support timelines verified July 2026, sourced from the Oracle Agile PLM Roadmap and the Oracle Lifetime Support Policy. Oracle Agile PLM, Agile PLM for Process, and Oracle Fusion Cloud PLM are trademarks of Oracle Corporation. Trace One is not affiliated with Oracle. This is an independent planning resource. Company and customer figures published at traceone.com and in GRC Outlook, May 2026 (grcoutlook.com/trace-one).
Let’s Get in Touch
Connect with our certified PLM professionals to get started.