Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle Primavera is the project management and project controls platform of record for capital-intensive industries — energy, construction, engineering, aerospace, and government. Primavera P6 Enterprise Project Portfolio Management (EPPM) and its predecessors manage trillion-dollar portfolios of capital projects worldwide. And Oracle charges 22% annually to support software that, in many organisations, hasn't received a meaningful functional update in years.
If you're running Primavera P6 EPPM, Primavera P6 Professional, or the older Primavera Enterprise platform, and your annual support bill is growing while Oracle pushes you toward Oracle Primavera Cloud (formerly Oracle Construction Intelligence Cloud), you have an alternative that most IT leaders in project-intensive industries haven't fully explored: independent third-party support.
This article explains what third-party support covers for Primavera, how the cost model compares, which organisations are the best candidates, and how the transition works in practice.
What Third-Party Support Covers for Oracle Primavera
Third-party support for Oracle Primavera P6 EPPM and related products covers the full suite of support services that organisations actually use — without the Oracle overhead, the roadmap pressure, and the mandatory upgrade cycle.
Covered under third-party support:
- Break-fix support for Primavera P6 EPPM, P6 Professional, and Primavera Enterprise
- Performance issues — database query optimisation, concurrent user performance, large schedule loading
- Integration support — Primavera integration with Oracle EBS, SAP, IBM Maximo, and third-party ERP/EAM systems
- Custom code support — modifications, APIs, P6 EPPM Web Services integrations, BI Publisher report customisation
- Security vulnerability remediation — CVE assessment and patches for Primavera application and supporting Oracle Database
- Oracle Database support (for P6 EPPM running on Oracle Database)
- Operating system and infrastructure compatibility guidance
- Version freeze support — P6 EPPM 16.x through 23.x supported indefinitely
- Interoperability maintenance as surrounding infrastructure (OS, virtualisation, browser) evolves
Not covered: New features, major version upgrades, Oracle Cloud migration assistance, or Oracle Primavera Cloud product support. Third-party support is for organisations that want to continue running their existing on-premises Primavera environment without disruption.
Who Uses Oracle Primavera — and Why the Support Math Doesn't Work
Primavera P6 is the dominant project controls tool in oil & gas, power generation, nuclear, construction, defence, and civil infrastructure. It's used for multi-billion-dollar capital projects with schedules measured in years, not sprints. The software is deeply embedded in project delivery workflows, integrated with cost management and document control systems, and operated by project controls specialists rather than IT generalists.
This creates a specific support economics problem:
- Primavera P6 environments are stable. Capital project organisations run the same P6 version for 5–10 years. The software is production-critical but change-averse. Oracle's annual 22% support fee assumes a software development relationship that simply doesn't exist for most Primavera customers.
- Oracle Cloud migration has no viable capital project use case. Oracle Primavera Cloud (OPC) is not a feature-for-feature replacement for on-premises P6 EPPM. Large-scale capital project schedules — tens of thousands of activities, earned value, resource-loaded logic — work differently in OPC. Most capital project teams that have evaluated the migration have found it impractical within a 3–5 year horizon.
- Oracle's Sustaining Engineering phase delivers nothing new. Once a Primavera release enters Sustaining Engineering (which Oracle defines as after the end of Premier Support), Oracle provides no new fixes, no new patches, and no regulatory compliance updates. If you're in Sustaining Engineering, you're paying 22% per year for effectively nothing from Oracle.
Are you in Oracle Sustaining Engineering for Primavera?
If you're running Primavera P6 EPPM 16.x, 17.x, or 18.x, you're almost certainly in Sustaining Engineering — paying Oracle for nothing. Get a free assessment of what independent support would cost for your environment.
Get Free Primavera Assessment →Primavera Version Support Matrix
Oracle's official support lifecycle for Primavera P6 EPPM follows the same pattern as all Oracle products — Premier Support, then Extended Support (at additional cost), then Sustaining Engineering (no new fixes). Most organisations running Primavera in production are on versions that have left Premier Support:
| Primavera Version | Release | Oracle Premier Support End | Oracle Support Status (2026) | TPS Available |
|---|---|---|---|---|
| P6 EPPM 23.x / 24.x | 2023–2024 | ~2026–2027 | Premier / Extended | ✓ Yes |
| P6 EPPM 21.x / 22.x | 2021–2022 | ~2024–2025 | Sustaining Engineering | ✓ Yes |
| P6 EPPM 19.x / 20.x | 2019–2020 | ~2022–2023 | Sustaining Engineering | ✓ Yes |
| P6 EPPM 16.x / 17.x / 18.x | 2016–2018 | ~2019–2021 | Sustaining Engineering | ✓ Yes |
| P6 EPPM 8.x / 15.x | 2012–2015 | 2017–2018 | Sustaining Engineering | ✓ Yes |
| Primavera Enterprise 5.x / 6.x | Pre-2010 | Long expired | Sustaining Engineering | ✓ Yes |
The practical reality: if you're running P6 EPPM 18.x or earlier, Oracle has essentially stopped supporting you — but is still invoicing you at 22% per year. Third-party support for these versions is not only available but provides genuinely superior support outcomes compared to Oracle's Sustaining Engineering offering.
The Cost Model: What You're Paying Oracle vs What You Should Be Paying
Primavera P6 EPPM is typically licensed on a named user, concurrent user, or CPU/NUP basis. Annual support is 22% of the net licence value (NLV). For organisations with significant Primavera deployments across capital project portfolios, that support cost can be substantial:
| Organisation Profile | Est. P6 NLV | Oracle Annual Support (22%) | TPS Annual Cost (est.) | Annual Saving |
|---|---|---|---|---|
| Mid-size EPC (200 named users) | £380K | £84K | £29K–£35K | £49K–£55K (58–65%) |
| Energy operator (500 named users + EPPM server) | £780K | £172K | £55K–£70K | £102K–£117K (60–68%) |
| Infrastructure owner (1,000+ named users, enterprise) | £1.6M | £352K | £105K–£140K | £212K–£247K (60–70%) |
| Government / defence (large EPPM + P6 Professional fleet) | £2.8M | £616K | £185K–£240K | £376K–£431K (61–70%) |
The saving range reflects the complexity of the environment, the number of customisations, integration complexity, and the level of support volume required. The percentages are consistent with GoVendorFree's Oracle support portfolio across Primavera-heavy clients.
Oracle Support Cost Reduction Playbook
54-page guide covering every lever for reducing Oracle support costs across EBS, Database, Primavera, Java, and more. Includes negotiation tactics, TPS transition playbook, and cost model templates.
Download Free Guide →Resisting Oracle Primavera Cloud Migration Pressure
Oracle's commercial strategy for Primavera is the same as for every other product in its portfolio: move customers to cloud subscriptions. Oracle Primavera Cloud (OPC) — rebranded from Primavera Cloud Service — is Oracle's SaaS project management product. Oracle's goal is to replace P6 EPPM on-premises deployments with OPC subscriptions.
For most capital project organisations, this migration is not viable in the near term:
- Feature parity gaps: OPC does not support the full earned value management (EVM) capabilities, advanced schedule logic, or large-scale schedule performance of P6 EPPM for the most complex capital projects. Organisations running multi-year, resource-loaded schedules with hundreds of thousands of activities have found OPC insufficient.
- Integration complexity: Most P6 EPPM environments are deeply integrated with Oracle EBS (cost modules), SAP PS/CS, IBM Maximo (work order integration), and custom project reporting environments via P6 EPPM Web Services. Re-integrating these interfaces with OPC requires significant re-engineering investment.
- Subscription cost increase: OPC is sold on a per-user subscription basis that, at scale, typically exceeds the cost of current Oracle P6 EPPM on-premises support even before migration costs are factored in.
- Data sovereignty and security: Many government, defence, and energy organisations have data residency requirements that preclude cloud migration for project schedule data containing sensitive asset information.
Third-party support removes the migration pressure entirely. Oracle cannot withhold support patches to force migration when you're no longer dependent on Oracle for support. You control your upgrade timeline — and you save 50–70% per year while you decide.
Strategic Options for Primavera Support in 2026
Option 1: Third-Party Support (Recommended)
Switch to independent support. Save 50–70% annually. Maintain full P6 EPPM functionality indefinitely. No migration pressure. Transition in 4–6 weeks.
Option 2: Negotiate Oracle Renewal
Use TPS quotes as negotiation leverage. Oracle will often discount 15–25% to retain accounts. Useful short-term but Oracle will recover fees in future renewals.
Option 3: Oracle Primavera Cloud Migration
Only viable for organisations with smaller, simpler P6 environments. Most capital project teams find OPC feature parity insufficient and migration cost prohibitive in the 2024–2027 window.
Option 4: Open-Source PM Tools
Tools like ProjectLibre or Oracle MPXJ are relevant for simple project management but cannot replace P6 EPPM for capital project portfolio management, EVM, or resource-loaded scheduling at scale.
How the Primavera TPS Transition Works
The transition from Oracle Primavera support to GoVendorFree typically takes 4–6 weeks and has zero impact on P6 EPPM production operations. The process:
- Environment assessment (week 1): GoVendorFree documents your P6 EPPM environment — version, database, integration landscape, custom modifications, user population, and current support patterns. This becomes your support handbook.
- Contract transition (weeks 1–2): We coordinate the Oracle support cancellation timing to ensure no gap. Your Oracle licence remains in place — you're only changing the support provider, not your software rights.
- Knowledge transfer (weeks 2–3): GoVendorFree engineers review your environment, integration map, known issues log, and any outstanding Oracle SRs. Open Oracle service requests are triaged and transitioned.
- Parallel support period (weeks 3–5): GoVendorFree supports your environment in parallel before Oracle support formally ends. This de-risks the transition completely.
- Live support (week 5–6 onwards): Full GoVendorFree support activated. 15-minute response SLA. Your P6 EPPM environment continues to operate exactly as before.
Ready to cut your Primavera support costs by 50–70%?
GoVendorFree supports Oracle Primavera P6 EPPM, P6 Professional, and supporting Oracle Database across energy, EPC, government, and infrastructure organisations. Get a free cost comparison within 24 hours.
Start Free Assessment →Sector-Specific Considerations
Energy & Utilities
Energy companies use Primavera P6 for capital project management — upstream platforms, refinery turnarounds, grid infrastructure, and renewable energy construction. The combination of Oracle EBS (or SAP) with P6 EPPM is common. GoVendorFree supports both the ERP and P6 layers, giving energy organisations a single independent support provider for their entire Oracle estate.
Engineering, Procurement & Construction (EPC)
EPC firms are among the heaviest P6 users. Multi-project environments with thousands of named users, complex Primavera-to-SAP integrations, and earned value management reporting are standard. GoVendorFree has experience in complex multi-entity EPC Primavera environments across Europe, the Americas, and the Middle East.
Government & Defence
Government and defence organisations using Primavera for programme management must maintain DISA/NIST/Cyber Essentials security compliance. GoVendorFree provides security vulnerability remediation with documentation compatible with government audit requirements. Data sovereignty requirements are accommodated — support delivery does not require data to leave your environment.
Nuclear & Regulated Infrastructure
Nuclear new build and regulated infrastructure projects have strict change management requirements (IEC 61511, NQA-1). GoVendorFree works within formal change management frameworks and provides the patch impact assessments and release notes required for regulated environment change approval.
Conclusion
Oracle Primavera P6 EPPM is deeply embedded in capital-intensive industries for good reason — it's the most capable project controls platform available for large-scale programme management. But Oracle's annual 22% support fee on a platform that most organisations haven't significantly updated in years represents pure margin extraction, not service delivery.
If you're in Oracle Sustaining Engineering for any Primavera version, you're paying Oracle for a support obligation that Oracle itself has formally wound down. Third-party support from GoVendorFree costs 50–70% less, delivers demonstrably better service outcomes, and removes the artificial migration pressure that Oracle uses to push customers toward Oracle Primavera Cloud.
The transition is low-risk, takes 4–6 weeks, and has no impact on your P6 EPPM production environment. The saving is immediate and permanent. For most capital project organisations, the only question is why they didn't do it sooner.