Primavera Cloud vs P6 EPPM licensing: which model costs less at scale.

Over five years at 100 or more users, on premises P6 EPPM perpetual licensing plus support usually costs less than a Primavera Cloud subscription. Here is the break even arithmetic, what the subscription hides, and how to answer Oracle's 2026 migration push.

What is the difference between Primavera Cloud and P6 EPPM licensing?

You are choosing between two cost structures. On premises P6 EPPM is a perpetual license, a large fixed cost paid once, plus annual support at 22 percent of the net license fee, repriced upward every year. Primavera Cloud is a per user, per month subscription with support included and no separate maintenance line.

Which one costs less depends on three things: how many users you license, how many years the deployment will run, and how tightly you control who gets an account. Oracle also sells more than one cloud product, and quotes often mix them up, so fix the product before you compare prices.

Which Oracle products and price points are on the table?

P6 EPPM Cloud Service keeps your schedules, codes and integrations as they are, with Oracle running the servers. Oracle Primavera Cloud is a different application, and moving to it means reworking data, reports and user roles. The two cloud rates sit $25 apart per user per month, while the conversion work for Oracle Primavera Cloud can take months.

Why should you treat every published Primavera price as a reference only?

Oracle no longer publishes current public pricing for Primavera Cloud. The tiers that circulate derive from the Construction and Engineering Global Price List dated November 10, 2016, and Oracle treats them as reference only. Actual pricing varies by reseller, region and contract size.

Use the figures on this page to build a model, then replace them with the numbers on your own order forms. For how Primavera fits with Unifier and Aconex in the wider portfolio, see our Oracle Construction and Engineering licensing overview.

If your business case rests on a 2016 price list, you are negotiating without a price.

When does P6 EPPM perpetual licensing become cheaper than a cloud subscription?

At list prices, on premises P6 EPPM becomes cheaper just after year three. For 100 named users, the subscription costs $89,500 a year more than on premises support ($150,000 against $60,500), so the $275,000 license is recovered in a little over three years. From year four on premises is cheaper every year, and the gap widens with each renewal.

The comparison vendors usually present stops at the first three rows. At three years the two lines sit within $6,500 of each other, which makes the subscription look like a wash. Run it to five years and the perpetual license is ahead by $172,500 before any uplift.

Why does the uplift assumption change the answer?

Support escalation compounds on the on premises line, and most buyers set it too low. Industry renewal data from early 2026 puts Oracle's median support uplift at 6.0 percent a year, above the 4 percent most buyers assume. In the contracts where no cap was negotiated, roughly 44 percent of those reviewed, Oracle applied its standard 8.0 percent.

Apply the same escalation to the cloud line. Cloud subscriptions reset at renewal and Oracle can reprice them each term, so the $125 rate is not fixed for the life of the deployment. As the table shows, uplift on both sides widens the gap in favor of on premises, because it compounds on a larger subscription base.

How does the result change at $100 per user or with a different user count?

At the lower Oracle Primavera Cloud rate the break even comes later, but it does not disappear. Say the same 100 users sign at $100 per user per month. The subscription runs $120,000 a year, $59,500 more than support, and the license pays back in a little over four and a half years.

• Five years, no uplift. $577,500 on premises against $600,000 in the cloud, a gap of $22,500.
• Five years, 6 percent uplift on both lines. About $616,000 against about $676,000.
• Different user counts. Both models are priced per user, so the payback year stays the same at 20 users or 2,000. What changes with size is the discount you can win, the weight of seat minimums on small teams, and the fixed cost of running servers yourself.

That last point is why subscription pricing wins for small, short lived or volatile user populations. It also wins where provisioning is so loose that you already pay support on named seats your people never use.

Where does Primavera Cloud subscription pricing hide costs?

Primavera Cloud hides cost in the way seats are counted and bundled. It looks simple because support is included and there is no separate maintenance invoice, yet four features of the license raise the effective rate per user:

• Minimum seat floor. You buy a minimum of five user licenses per module. A three person scheduling cell still funds five seats, and small pilots pay for capacity they do not use.
• Module fragmentation. Oracle Primavera Cloud has four license types: Portfolio and Capital Planning, Progress, Schedule, and Task Management. A scheduler who also does portfolio work needs more than one license.
• Bundled license models. Under the Project model every user automatically receives the Progress, Schedule and Task Management licenses. The Enterprise model adds Portfolio Planning for everyone, which raises spend across the whole population. Both remove the ability to size licenses person by person, which is where the savings are.
• Renewal repricing. The subscription rate has no floor. When the term ends Oracle can raise the per user rate, and protections you negotiated into an on premises contract do not carry over.

Which Oracle Primavera Cloud license model should you pick?

For most companies, the Named Users model. Oracle offers it alongside the Project and Enterprise models, and it is the only one where you assign each license type to the people who need it. Application Administrators are automatically assigned every enabled license type, so keep that group small.

The example assumes 10 portfolio planners, 20 schedulers, 30 people who only update progress, and a 3 person task management cell drawn from the schedulers. Ask Oracle to price each column. The per unit rates for the bundled models look lower, and this count is how you test whether the total is.

Should you migrate to the cloud to escape support increases?

We advise against it, even though it is a common recommendation. The argument runs that a subscription ends the annual support uplift. In practice, Oracle is removing pricing protections in 2026 that on premises customers relied on. Customers who migrate often assume their negotiated caps and discounts transfer, and they do not.

Cloud subscription contracts reset pricing at renewal. A migration made to escape support escalation can trade a capped 6 percent increase for an uncapped renewal. Negotiate the cap on the contract you already have, and migrate only when the five year model favors it on its own terms.

Why is Oracle pushing P6 customers to the cloud in 2026?

Oracle is pushing migration because its 2026 growth plan depends on cloud revenue, with OCI at the center. In March 2026 it guided to total cloud revenue growth of 46 to 50 percent year over year in US dollars for the quarter ending May 2026. To reach numbers like that, sales teams are pressing on premises customers to move.

The pitch uses two tools: positioning around the support lifecycle, and migration business cases that overstate the savings. Oracle markets Primavera P6 Migration to the Cloud as "the last upgrade you'll ever do", delivered through Oracle Soar. That line is a sales message. Nothing in P6 on premises forces a cloud migration.

What does Oracle Soar include, and what does it leave out?

Soar is Oracle's migration service. Oracle says it includes a discovery assessment, an environment analyzer, automated data and configuration migration utilities and rapid integration tools, and it claims up to a 30 percent reduction in migration time and cost. Ask what baseline that 30 percent is measured against.

The tooling covers the technical transfer. It does not cover the commercial terms, which is where the long term cost sits.

What happens if you let P6 support lapse?

The license keeps working, but the cost of coming back is high. Perpetual licenses do not expire. Without active support you cannot upgrade to newer versions, and Oracle reserves the right to request a migration and charge backdated support fees.

If you later reinstate support, or an audit finds you running software without current support, Oracle's support policies set a reinstatement fee of 150 percent of the last annual support fee, prorated over the lapsed period. That is the back support plus half again. Our guide to dropping Oracle support and reinstatement covers the rules in detail.

What does a SQL Server to Oracle Database migration add?

Customers running P6 on SQL Server must migrate to an Oracle database as part of the cloud upgrade. That is a project cost, a risk of moving platforms, and a possible new Oracle Database licensing exposure. None of it appears in Oracle's migration business case, so put a hard number on it before you accept the cloud TCO Oracle presents.

What will the Oracle account team say, and how should you answer?

• "This is your last upgrade." Answer: "Show us the five year cost at our user count, with renewal uplift on the subscription line, next to our current support run rate."
• "Your version is going out of Premier Support." Answer: "We will decide on support separately. The license is perpetual and the migration has to pay for itself."
• "Your current discount carries over." Answer: "Put the renewal rate cap for every future term in the order form, or we assume it does not."
• "Soar makes the migration nearly free." Answer: "Price the database migration, integration rework and training alongside the Soar service, and we will compare the totals."

Which licensing traps apply to both P6 and Primavera Cloud?

Most audit findings and cost overruns come from how users and data are counted, and that risk follows you into either model. These five traps come up most often:

• Provisioning inflation, on premises. Every user defined in P6 counts toward your license obligation, including inactive, test and dormant admin accounts. A company that provisioned 150 users but actively uses 80 still owes 150 named user licenses. This is the most common overspend a customer causes itself, and the easiest to fix before renewal.
• Indirect access. If your ERP, analytics platform or data warehouse pulls P6 data and shows it to employees, those employees may need P6 licenses even if they never open the P6 interface. This is a top audit finding in both models.
• Reporting tools. P6 licenses cover scheduling and running standard reports through Oracle Analytics Publisher. Creating new or custom reports requires a separate full use Analytics Publisher license, and custom dashboards are a frequent finding of unlicensed use.
• Restricted use repricing. When an audit finds a restricted component used outside its intended context, Oracle's position is that the use was never licensed. The remedy it asks for is full use licensing at list for the entire deployment, often with back support. See our analysis of the restricted use Oracle Database under P6 EPPM and restricted use licenses in Primavera P6.
• External contractors. Contractors and joint venture partners who access your P6 environment usually need their own licenses, which scales badly on large capital projects. Our guide on counting external contractors in Primavera deployments covers the exposure.

How do you check who is actually using P6?

Start with the data P6 already holds. These sources give you a count you can defend in a renewal or an audit:

1. The Users page. In P6, the Users page lists every account and its module access (Projects, Resources, Portfolios, P6 Professional, Team Member, Timesheet and others). Export it and mark each account active, dormant, test or admin.
2. Integration flags. Accounts with Integration API or Web Services module access show which systems pull P6 data. Each one is a place to check for indirect access.
3. Session metrics. If you monitor P6 through Oracle Enterprise Manager, the P6 EPPM metrics report logged in and concurrent users, sessions by module, and historical unique total logins.
4. Contractor accounts. Match every external login against a current contract and a license, and set an end date on each account.

If you pay support on 150 named users and 80 use the system, roughly 47 percent of your on premises support spend covers unused seats before you compare anything. At $605 a user, the 70 unused seats cost $42,350 a year in support.

Why can dropping one P6 support line raise your other costs?

Oracle reprices the support on the licenses you keep. Under Oracle's support policies, if you terminate a subset of the licenses on a single order, support for the remaining licenses on that order is repriced at Oracle's list price for support minus the standard discount. Your negotiated discount on the lines you keep can disappear.

The new price is capped at what you paid before for the whole order, plus any country annual adjustment. It also cannot fall below what you already paid for the licenses you keep, so the saving can shrink to nothing.

What are the cleaner ways to cut P6 support cost?

Model the repricing on every order before you terminate a partial support line. Oracle also requires all licenses in a license set to carry the same support level, so you cannot keep some P6 licenses on support and leave the rest unsupported. These routes avoid the repricing trap:

• Clean up before renewal. Remove dormant accounts first, so the count you need to cover matches the people who work in P6.
• Terminate whole orders. The repricing rule covers a subset of licenses terminated on a single order. Giving back every license on a separate shelfware order, rather than leaving licenses you keep unsupported, can leave the discount on your main P6 order untouched. Check any price hold first, because licenses bought under a price hold on the reduced order are repriced as well.
• Consider third party support. For stable versions you do not plan to upgrade, see our analysis on moving Primavera and Unifier to third party support.

What have we seen in Primavera cost models?

Our models show the same pattern each time. On premises P6 EPPM costs more in the early years because of the upfront license, then pulls ahead and stays ahead once that cost is sunk. At 100 or more users over five years, perpetual plus support has won in almost every case we have modeled.

Three other findings come up repeatedly in our work on these decisions:

• Migration costs are left out. The SQL Server to Oracle Database migration, the platform change and the lost pricing protections routinely add 15 to 30 percent to the true first year cloud cost.
• Provisioning changes the answer. Where subscription pricing does win, loose account control is often part of the reason, and that can be fixed without migrating.
• Audits follow resistance. Oracle audit activity tends to increase when a customer turns down a migration, so prepare your usage records before you say no.

The 2026 migration push is a revenue strategy, not a cost argument in your favor. Keep the perpetual license you have paid for unless your own five year numbers favor leaving it.

What should you get in writing before you renew or migrate?

Get a written cap on every price that can rise. Roughly 44 percent of the contracts reviewed had no support cap and paid 8 percent. A cap of 3 to 4 percent, compounded, saves six figures over a five year term once support reaches a few hundred thousand dollars a year.

Say your P6 support bill is $300,000 a year. Over five years, 8 percent uplift costs about $1,760,000, while 3 to 4 percent costs about $1,593,000 to $1,625,000. The cap is worth roughly $135,000 to $167,000.

Which terms should you ask for?

• Support uplift cap (on premises). A written maximum annual increase for each renewal, so the 8 percent default never applies.
• Renewal rate cap (cloud). A ceiling on the per user rate at each renewal, since the subscription has no floor of its own.
• Price hold for added users. New seats during the term at the signed rate, instead of a fresh quote.
• Reduction right at renewal. The right to lower cloud user counts at each renewal without repricing the remaining seats.
• License model choice. The Named Users model written into the order, with the right to change model at renewal.
• Migration costs in the quote. Database migration, Soar services and any parallel running period priced on the signed order.

When should you start preparing?

What to do next

1. Count real usage. Measure the seats people actively use and clean up dormant and test accounts before renewal, because the count changes the break even.
2. Model five years. Run on premises (license sunk, support at 6 percent and 8 percent uplift) against the cloud (per user subscription plus renewal repricing) at both the $125 and $100 rates.
3. Price the hidden migration costs. Add the SQL Server to Oracle Database migration, the platform change and the lost pricing protections to any cloud business case Oracle presents.
4. Negotiate the cap in writing. If you stay on premises, cap the annual support uplift at renewal. If you migrate, cap the renewal rate for every term.
5. Do not let support lapse by default. The reinstatement fee and backdated support make a lapse far more expensive than it looks. If you want to leave Oracle support, do it deliberately through third party support.
6. Prepare for the audit. Have the account export and integration map ready before you turn down a migration, and read our overview of Oracle audit scope across Primavera deployments so you know what an auditor will ask for.

Frequently asked questions