Third-party support can cut your Oracle Construction and Engineering support bill by 50 to 65 percent, but only certain Primavera and Unifier estates qualify. This guide names where the savings, the traps, and the leverage actually sit.
Third-party support can cut your Oracle Construction and Engineering support bill by 50 to 65 percent, but only certain Primavera and Unifier estates qualify. This guide names where the savings, the traps, and the leverage actually sit.
Oracle charges 22 percent of net license fee for annual support on your Primavera P6 EPPM and Unifier estate. Third-party support (TPS) providers such as Rimini Street and Support Revolution advertise 50 to 65 percent reductions on that number while you keep every license you own. The question is not whether TPS is legal (it is) or whether it saves money (it does). The question is whether your specific Primavera and Unifier deployment is stable enough to survive without Oracle's updates, and whether you can absorb the loss of the cloud-migration path Oracle keeps pushing you toward. In our experience across two decades of Oracle Construction and Engineering negotiations, the answer is yes for the majority of on-premise P6 EPPM estates that are past their heavy change window, and a qualified no for Unifier deployments still in active business-process rollout.
The single strongest argument for moving Primavera to third-party support is its release cadence. Oracle ships on-premise Primavera updates once a year, timed just before Christmas, an annual tradition that has held for years. Compare that to the cloud, where Primavera Cloud receives four updates per month: a new-feature release at the end of the first week and service packs at the end of weeks two, three, and four, plus weekly patch sets and unscheduled hot fixes deployed as needed. That contrast matters. If you are on-premise, you are already living on a slow, predictable, annual cadence. You are not consuming a stream of monthly innovation. Freezing that estate on its current release loses you very little, because the difference between "one update a year" and "no vendor updates" is far smaller than the difference between "four updates a month" and "none."
P6 has a four-decade track record as the scheduling backbone for engineering and construction, and Oracle itself states that P6 "isn't going anywhere." That stability cuts both ways for the buyer. It means the product is mature, the defect surface is well understood, and the marginal value of each annual patch is low. A mature, stable, slowly changing product is exactly the profile that third-party support was built to serve. This is the same logic we applied when Avis moved stable WebLogic estates to third-party support and saved 8 million dollars over three years.
On-premise Primavera already runs on one update a year. Moving to third-party support removes very little you were actually consuming.
Oracle's published support rate is 22 percent of the list perpetual license fee. For term licenses, the annual list runs from 20 percent of list (1 year) up to 70 percent of list (5 years). Against that 22 percent baseline, the TPS providers make quantified claims. Rimini Street delivers roughly 50 percent savings against Oracle's standard rate. Support Revolution cites a minimum 50 percent saving with a 65 percent average, plus 24/7 support and a 10-minute response SLA. Rimini also frames the longer arc: up to 50 percent off annual fees, up to 90 percent off total support costs, and extension of a system's useful life by up to 15 years.
The table below models the annual math on an indicative Primavera estate. We use published indicative license figures (P6 Professional at roughly 3,520 US dollars per user, P6 EPPM base at roughly 2,750 US dollars per application) because Oracle does not publish Unifier list pricing. Treat these as illustrative, not quotes for your account.
| Scenario | Annual Oracle support (22%) | TPS at 50% saving | TPS at 65% saving | 3-year saving (65%) |
|---|---|---|---|---|
| Est. license base $500K | $110,000 | $55,000 | $38,500 | $214,500 |
| Est. license base $1.5M | $330,000 | $165,000 | $115,500 | $643,500 |
| Est. license base $4M | $880,000 | $440,000 | $308,000 | $1,716,000 |
The figures compound because Oracle raises support annually and TPS providers typically cap or freeze increases. Even at the conservative 50 percent line, a mid-sized Construction and Engineering estate frees six figures a year, money that is currently buying you one annual patch you may not be installing anyway. Before you accept the savings claim at face value, confirm your true support base. Support fees are levied on the full net license fee across your estate, including shelfware, so the first move is always to establish your full Construction and Engineering license position.
Unifier does not share P6's clean TPS profile, for two reasons. First, its pricing is opaque. There is no publicly available Oracle price for Unifier; third-party review sites cite an entry point around 100 US dollars per user, which tells you almost nothing about an enterprise deployment. That opacity is a negotiation trap on both sides: it makes your Oracle support base hard to verify, and it makes TPS scoping harder to price. Second, Unifier is a configuration-heavy platform. The base Accelerator alone ships 65-plus pre-configured business processes and 250-plus layouts, reports, and dashboards, spanning 40 countries, 12 languages, and 183 currencies. Unifier customers tend to be in continuous business-process build-out, not steady state.
That matters because the core structural limitation of third-party support is that you get no new features. The provider maintains what you have and fixes defects; the vendor roadmap is off the table. Support Revolution mitigates this with a bank of Enhancement Days delivered as custom development, but that is a services model, not a product roadmap. For a P6 estate that is not chasing new features, this is a non-issue. For a Unifier estate mid-rollout, losing access to Oracle's evolving standard processes and integrations can strand your program. The practical test: if your Unifier deployment has stabilized and you are no longer activating new modules or process templates, it becomes a viable TPS candidate; if it is still expanding, keep it on Oracle support for now and revisit at the next contract anniversary. Understanding the named-user and module metrics behind Unifier is essential to judging where your estate actually sits on that curve.
P6 is a freeze candidate. Unifier is a stabilization question. Do not treat the two as one decision.
Oracle markets Primavera P6 Migration to the Cloud as "your last upgrade ever," with all future software updates handled for you. The documented migration path covers P6 EPPM, Unifier, and Analytics. Moving to third-party support is, in effect, a decision to step off that escalator, at least for the term of the TPS engagement. That is not automatically a loss. Oracle's cloud path carries real friction the sales narrative omits: SQL Server customers face a forced database conversion to Oracle Database as part of the upgrade, and Primavera Cloud organizes data differently from on-premise P6, requiring data restructuring against Oracle's best practices. In other words, "your last upgrade ever" is a full re-platforming project, not a switch flip.
So the honest framing is: TPS lets you defer the cloud migration on your own timeline rather than Oracle's. You keep your perpetual licenses, run the on-premise estate at half the support cost, and decide when (or whether) the cloud economics justify the re-platforming. Before you can even model that choice, run the Primavera Cloud versus P6 EPPM cost comparison at your scale, because at larger user counts the subscription math frequently favors staying on-premise. One caution: watch the embedded database. P6 EPPM ships with a restricted-use Oracle Database license, and the boundaries of that restricted-use grant are a common audit finding. TPS does not change your database entitlement, so confirm your database usage stays inside the restricted-use limits before and after any move.
The legality of third-party support is settled. Oracle licensees may decline to renew Oracle support and hire a third-party provider or self-support, and doing so does not void your license. Redress and the wider market have confirmed this repeatedly. What the litigation history changed was provider behavior, not buyer rights. Courts found that Rimini Street infringed Oracle's copyrights through certain of its support processes, producing damages and a permanent injunction, even while confirming that third-party support as a concept is lawful. Oracle and Rimini announced a confidential settlement on 7 July 2025, with Rimini required to end PeopleSoft support by July 2028, closing a fifteen-year saga.
The buyer takeaway is precise: your risk is not that TPS is illegal, it is that your provider's methods could infringe, and that you retain audit exposure regardless of who supports you. For a fuller treatment, see our analysis of whether Oracle third-party support is legal and the practitioner's guide to Rimini Street and the alternatives. Ask any prospective provider, in writing, how they build and deliver Primavera fixes and whether their process complies with the post-injunction standards. Get indemnification language in the contract.
This is the point most vendors and providers underplay. Leaving Oracle support does not reduce your compliance obligation, and in market experience it often raises audit likelihood, because Oracle loses the annual support renewal touchpoint and the recurring revenue that came with it. An Oracle audit of a Construction and Engineering estate examines P6 named users, Unifier user and records counts, Aconex project scope, and the embedded database usage. Before you switch, you must lock down your compliance position, not after. The two areas that catch Construction and Engineering customers most often are external-party counting and the Unifier records metric.
Treat this as a segmented decision, not a single yes or no. Split your estate into steady-state and active-change buckets. Steady-state on-premise P6 EPPM is a strong TPS candidate today; move it and bank the 50 to 65 percent saving. Unifier mid-rollout stays on Oracle support until it stabilizes. Then sequence the work: (1) establish your verified license position and close any compliance gaps while you still hold Oracle support, which is the cheapest time to remediate; (2) model the three-year saving against your true support base, not the vendor's headline percentage; (3) shortlist two providers and demand written answers on fix-delivery methods and indemnity; (4) time the switch to your support renewal date, because Oracle bills in full-year increments and mid-term exits waste money. If Unifier is expanding and you are considering the cloud path anyway, price both routes using the cloud-versus-EPPM comparison before committing to either. In every engagement we run, the customers who win are the ones who fixed compliance first and negotiated from a verified position, not the ones who chased the savings number first.
Fix compliance while you still hold Oracle support. Remediation is cheapest before you leave, most expensive after an audit letter arrives.
No. Oracle licensees may decline to renew Oracle support and use a third-party provider or self-support, and this does not void your perpetual licenses. You keep every entitlement you own. What you lose is access to Oracle updates, patches, and the cloud-migration path, not the software itself.
Against Oracle's standard 22 percent annual rate, providers cite 50 to 65 percent reductions. Rimini Street advertises roughly 50 percent, and Support Revolution cites a 50 percent minimum with a 65 percent average. Your real saving depends on your net license base, so model it on your verified support figure rather than the headline percentage.
Only if your deployment has stabilized. Unifier is configuration-heavy and many customers are in continuous business-process rollout, which conflicts with the no-new-features nature of third-party support. If you are still activating modules and process templates, keep Unifier on Oracle support and revisit at the next renewal.
In market experience, yes. Oracle loses the annual renewal touchpoint and the recurring revenue, which can raise audit likelihood. Third-party support does not change your compliance obligation, so you must reconcile your P6 users, Unifier records metric, external contractors, and embedded database usage before you switch, while remediation is still cheap.
Third-party support lets you defer the cloud move onto your own timeline rather than Oracle's. Oracle markets its cloud path as your last upgrade ever, but it is a full re-platforming project, including a forced SQL Server to Oracle Database conversion and data restructuring. Run the Primavera Cloud versus P6 EPPM cost comparison before deciding either way.
Get written detail on how they build and deliver Primavera fixes and confirmation that their methods comply with the post-Rimini injunction standards, plus indemnification language covering intellectual property claims. The Rimini litigation confirmed third-party support is legal but penalized specific infringing processes, so the risk sits in provider methods, not the concept.
When third party support is the right call for Oracle Database, Apps, and Middleware. Rimini Street, Spinnaker, the savings math, and the leverage even non sw
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.
