Oracle wants you to read the December 2027 Agile PLM support cliff as a forced march into Fusion Cloud PLM. This guide separates the real deadline from the manufactured urgency, and shows where your leverage sits when the perpetual license becomes a subscription.
Oracle wants you to read the December 2027 Agile PLM support cliff as a forced march into Fusion Cloud PLM. This guide separates the real deadline from the manufactured urgency, and shows where your leverage sits when the perpetual license becomes a subscription.
Two clocks are running, and Oracle deliberately blurs them. The real one: premier support for Agile PLM 9.3.6 ends December 31, 2027, after which the estate falls to Sustaining Support with no new security patches, bug fixes, or technical assistance. The invented one is the implication that Fusion Cloud PLM is your only landing spot. It is not. Fusion is one option, third-party support is another, and staying on Sustaining Support is a third. Treat those as competing bids, not a single migration you are obligated to fund.
Context sharpens your position. The last major Agile release shipped in 2016, and Oracle removed version 9.3.7 from its roadmap in October 2023, making 9.3.6 the terminal release. You are being asked to abandon a perpetual asset for a subscription because Oracle stopped investing in the product nine years ago. That is a negotiation fact, not a courtesy. When Oracle's account team frames the move as an upgrade, correct them on the record: it is a rebuild on a different architecture, and the pricing conversation should reflect a competitive net-new deal. For the underlying entitlement mechanics you are leaving, start with our Oracle Agile PLM licensing buyer guide.
Fusion Cloud PLM is not a direct upgrade. It is a competitive net-new deal on a different data model, and it should be priced like one.
The mechanical change is a shift from a perpetual Named User Plus license (paid once, maintained annually at 22 percent) to a Hosted Named User subscription (paid every year, forever, with no perpetual fallback). Oracle Fusion is available exclusively as SaaS. There is no on-premise deployment option, so the moment you sign, you have surrendered the perpetual license and accepted a renewal cliff every three years.
Both definitions carry the same trap: they count individuals authorized to access the system, whether or not those individuals ever log in. Under Agile's Named User Plus terms, a non-human operated device (an integration account feeding your ERP, CAD, or MES systems) counts as a license in addition to every authorized human. Fusion's Hosted Named User inherits the same authorized-not-active logic. Do not assume the metric got friendlier. The exposure moved from a one-time true-up to a recurring subscription line that renews at your named-user peak. For the metric detail on the model you are leaving, see our comparison of Agile PLM Named User versus Concurrent.
| Dimension | Agile PLM (on-prem) | Fusion Cloud PLM (SaaS) |
|---|---|---|
| License basis | Perpetual Named User Plus / Concurrent / Restricted | Subscription: Hosted Named User + Product Hub record metric |
| Payment shape | One-time license, then 22% annual support | Recurring per-user monthly, typical 3-year term |
| Counting rule | Authorized individuals + non-human device accounts | Authorized individuals (active or not) |
| On-prem fallback | Yes, perpetual right survives | None. SaaS only |
| Restricted/supplier tier | Restricted user class for external parties | Must be re-mapped; no direct equivalent |
| Support model | Premier through Dec 2027, then Sustaining | Included in subscription, renews with it |
| Price signal | 22% of license cost per year, rising 4-8% annually | SCM band $300-$450 per user per month list; SelectHub cites ~$625 as a starting figure with a 10-user minimum |
Note the second Fusion metric: Product Hub Cloud Service is priced by product record, defined as a unique product used by the enterprise, counting finished goods, phantom items, style items, sku items, pack items, assemblies, components, and model/option items, but excluding instance items, organization assignments, and revisions of the same item. If your Agile deployment leans heavily on Product Hub for item master data, model this metric separately and audit the definition line by line. Oracle's proposal will assume a generous record count. Your bill of materials complexity, not Oracle's estimate, sets the number.
You cannot negotiate a migration deal without pricing the alternative, and the alternative is not free. On Premier Support you pay 22 percent of the original license cost every year, and Oracle Agile has been raising support 4 to 8 percent annually. The compounding is brutal. The published worked example: a customer who paid $100K upfront in 2000 and thereafter paid 22 percent with 8 percent yearly increases would see annual support alone reach $151K by 2025, roughly 81 percent of the original inflation-adjusted purchase value. Staying still costs, and it costs more each year.
Two hidden traps compound the math. First, reaching a supported patch level is not automatic: upgrading to Agile 9.3.6 RU 29 typically runs $40,000 to $60,000, and Oracle patches only the most recent release update. Second, reinstating lapsed maintenance is punitive. One documented case put reinstatement at $150,000 upfront plus $25,000 annually with CPI increases, climbing past $225,000 through 2027. If you let support lapse thinking you will pick it back up, price that penalty before you decide. Our analysis of when leaving Oracle support pays lays out the bridge option in detail.
You cannot negotiate a Fusion deal without a priced alternative on the table. Third-party support and Sustaining Support are both legitimate BATNAs, and Oracle knows it.
Fusion Cloud PLM is built on an entirely different architecture and data model. It is not a lift-and-shift. Organizations routinely rebuild change management, quality, and governance workflows from scratch and redesign integrations with ERP, CAD, MES, and supplier systems. A structured migration for an enterprise with significant data, integrations, and compliance requirements typically runs 8 to 12 months. That is not a subscription cost. That is an implementation cost, and it is the sleeper line in every Fusion deal.
The buyer-side discipline is blunt: the implementation cost is the lever most often neglected. A customer who focuses only on knocking down the subscription can pay 30 percent more to the implementation partner than they saved on the license. Bid implementation separately from subscription. Put two or three implementation partners in competition. Lock fixed-price phases rather than time-and-materials. Oracle will happily let you obsess over the per-user rate while the systems integrator writes an open-ended change-order stream behind it.
The single largest lever is user-tier mix. Oracle's default proposal assumes a high ratio of professional (full) users. Most PLM deployments are a pyramid: a small core of professional users and a much larger base of self-service and view-only participants. Published buyer-side experience puts the saving from accurately mapping this before signature at 30 to 50 percent versus Oracle's initial proposal. Before any pricing conversation, build the actual user census from your Agile role and privilege data. Do not let Oracle count your Restricted (supplier and distributor) population as full Fusion users. That mapping problem is exactly why we wrote our note on counting suppliers and external users.
The second lever is the competitive alternative. Enterprise customers who negotiate with a defensible deployment forecast and a genuine competitor on the table land realized pricing 35 to 55 percent below list. That competitor is real: most existing Agile users have declined Fusion Cloud PLM precisely because the architecture requires rebuilding integrations and core processes anyway. If you are rebuilding regardless, a rival PLM (or third-party support to extend the runway) is a credible destination, and Oracle's discount authority responds directly to that credibility.
| Lever | Mechanism | Documented range |
|---|---|---|
| User-tier mapping | Correct professional-to-self-service ratio before signature | 30-50% below Oracle's initial proposal |
| Competitive alternative | Defensible forecast + credible rival on the table | 35-55% below list |
| Implementation bidding | Two or three partners, fixed-price phases | Prevents 30% overspend that erases subscription savings |
| Third-party support bridge | Independent Agile support during transition | Up to 50% annual support savings, up to 90% TCO (vendor-advertised) |
Treat the third-party support figures as vendor-advertised ceilings, not guaranteed outcomes. They are directional and useful as a leverage exhibit. The point of introducing them into a Fusion negotiation is not necessarily to buy them. It is to prove to Oracle that you have a costed, executable path that does not send them a dime, which is the only thing that moves discount authority above the standard band.
Do not sign a Fusion subscription while an unresolved Agile compliance gap sits behind you. Oracle's leverage in a migration is highest when your legacy position is exposed, because a threatened audit finding becomes a bargaining chip against your new subscription price. Before you enter the Fusion conversation, reconcile your Agile named-user count, your module entitlements, and any embedded database usage. Module sprawl is a common finding: add-ons that were switched on years ago and never entitled surface during migration due diligence, and Oracle will price them into the exit. Our guides on Agile PLM module sprawl and the restricted-use database license under Agile map exactly where those findings hide.
Build the evidence pack before Oracle asks. If your named-user records, device-account inventory, and module deployment map are documented and defensible, a migration-adjacent audit has a hard ceiling. If they are not, Oracle sets the ceiling. The discipline is identical to a standalone audit defense: know your true consumption, prove it, and cap the exposure before the commercial conversation starts. See our Agile PLM audit-defense evidence pack for the exact artifacts to assemble.
With the December 2027 cliff two-plus years out and an 8-to-12-month migration window, the planning decision is due now, but the signature is not. Use the runway. Run the three options in parallel, price your actual user pyramid, close your Agile compliance gaps, and bid implementation competitively before you let Oracle anchor the subscription. The migration is a rebuild either way, which means Oracle's product is no longer the default. Make them win the deal on price, not on the deadline.
Premier support for Agile PLM 9.3.6 ends December 31, 2027. After that date the software runs on Sustaining Support only, with no new security patches, bug fixes, or technical support. Version 9.3.6 is the terminal release since Oracle removed 9.3.7 from the roadmap in October 2023.
No. Fusion Cloud PLM is built on an entirely different architecture and data model. Core processes, change management and quality workflows, and integrations with ERP, CAD, MES, and supplier systems generally have to be rebuilt from scratch. Treat it as a competitive net-new implementation, not a version upgrade.
Fusion Cloud PLM sits within the Fusion Cloud SCM band, which Oracle lists at roughly $300 to $450 per user per month. Some sources cite starting figures around $625 per user per month with a 10-user minimum depending on modules. Realized pricing typically lands 35 to 55 percent below list when you negotiate with a defensible forecast and a credible alternative.
Implementation. A structured migration for a complex enterprise runs 8 to 12 months, and buyers who focus only on cutting the subscription can pay up to 30 percent more to the systems integrator than they saved on the license. Bid implementation separately, fixed-price, across multiple partners.
Yes, via Oracle Sustaining Support or an independent third-party support provider. Third-party support providers advertise up to 50 percent savings on annual Agile support fees. Staying is a legitimate BATNA that strengthens any Fusion negotiation, but reconcile your compliance position first, because lapsed maintenance reinstatement carries steep penalties.
Build your actual user pyramid from Agile role and privilege data before requesting a quote. Oracle's default proposal assumes a high ratio of professional users, but most deployments have a small core of full users and a large self-service base. Correct mapping before signature can cut licensing 30 to 50 percent versus the initial proposal.
Oracle prices Fusion ERP Cloud per employee, not per user, which inflates true cost. The buyer side guide to module economics and the modernization discount.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
