Outgrown Microsoft Project? Run the whole project in one place.
The Oracle Primavera Cloud service puts scheduling, resources, risk, costs and field planning in one place, on the scheduling logic Oracle built for P6. For a team that has outgrown Microsoft Project files, it is often the right next step. We help you check the fit before you commit.
Checked on 19 October 2026: Primavera Cloud "shares the same trusted scheduling algorithms and pedigree of Primavera P6" and is "welcoming to beginners and experts alike" (Source 1, p3); the contract and field schedules, resources, risk and portfolio capabilities (Source 1, p4; Source 2, pp8 to 12); Oracle's logo rule (Source 14). "Run the whole project in one place" is our view of the benefit, not Oracle's words.
Checked against Oracle's documents on 19 October 2026
Is this you?
If two or more of these ring true, Primavera Cloud is worth a proper look.
- Your schedules live in Microsoft Project files that get emailed, copied and saved over.
- Several projects share the same people, and nobody sees the clash until it happens.
- Site teams cannot update the schedule, so progress comes back by phone or on paper.
- Risk sits in a spreadsheet beside the schedule, not in it.
- Your schedules were in Project Online, which Microsoft retired at the end of September 2026.
- A client asks for P6 files, but your team does not need all of P6.
What you will know
- Whether Primavera Cloud, P6 or staying with Microsoft Project fits how you work.
- What comes across from your Microsoft Project files, and what you set up again.
- What it costs to get going, beyond the subscription.
- Who needs training, and in what.
Checked on 19 October 2026: Project Online retired on 30 September 2026, after which "you will no longer be able to access your projects or any associated data" (Source 10); Primavera Cloud imports Microsoft Project XML files (Source 3) and imports and exports P6 XER and XML files (Source 5, p152; Source 6). The file, clash and site-update lines draw on a competing software vendor's article (Source 13) and our field view; the risk line rests on a community forum answer that Microsoft Project desktop "does not include a feature to perform that analysis" (Source 12). All six are to test in the interviews. To validate
One place for the whole project
Most teams we meet run a project across three or four tools: the schedule in Microsoft Project, the risk register and the cost tracker in spreadsheets, and the site's lookahead on a whiteboard. Primavera Cloud brings them into one service, working from one set of projects, people and dates.
| What you run today | Where it goes in Primavera Cloud | What changes |
|---|---|---|
| The schedule, in Microsoft Project files | Schedule: critical path scheduling on P6's scheduling logic, with many projects in one shared database | One current version of each schedule, with no files to email or save over |
| The risk register, in a spreadsheet | Risk: a register with qualitative and quantitative analysis, run on the schedule | Risks sit against the activities they threaten. See the next section |
| Lookaheads and site plans, on whiteboards or in spreadsheets | Tasks: planning boards for lean and Last Planner methods, with constraints, commitments and a mobile app | The site plan is tied to the contract schedule, and site leads update from their phones |
| Resource clashes, found in meetings | Resources: loading, and clashes within and across projects | Clashes show up before they happen |
| Progress and timesheets, by email or on paper | Timesheets, My Activities and the mobile app | Progress comes in where the schedule is |
| Cost tracking, in a spreadsheet | Costs and funds, against the schedule | Cost and time are read from the same plan |
| The capital plan, in spreadsheets or Project Online | Portfolio and Capital Planning, a separate service for owners | One view from an idea to a funded project |
Our view is that a team moving up from Microsoft Project can retire three or four of those tools. We test that on your own projects before anyone signs.
Checked on 19 October 2026: "an all-in-one solution structurally built to bring office and field teams together", "Stop passing around spreadsheets and manage risk within a system" and "The typical disconnected architecture of contract and field scheduling" (Source 1, product page, updated 14 August 2026); planning boards "supporting lean pull and last planner ® methodologies", resources "within and across all your projects" and "qualitative and quantitative risk analysis" (Source 1, datasheet p4); the modules in the Schedule service, from resources and risk to costs and funds, timesheets, My Activities and mobile (Source 2, p8); Portfolio and Capital Planning (Source 2, pp10 to 12); Project Online's retirement (Source 10). "Three or four tools" and the first column are our view, to test in the interviews To validate. The Microsoft Project pains draw on a competing vendor's article and a community forum (Sources 12 and 13).
Risk, managed the same way on every project
A risk register in a spreadsheet is cut off from the dates it threatens. In Primavera Cloud, risks are linked to the activities they affect, and the analysis runs on the schedule itself. For many teams that is reason enough to use it, even if they schedule somewhere else.
What it does:
- A register for every project and program, with probability, impact, owners and response actions.
- Scoring rules and risk matrices set once for the whole organisation, and a library of reusable risks, so every project scores risk the same way.
- Program registers that bring project risks together in one view.
- Monte Carlo analysis on the schedule and its risks, showing the likely finish dates and costs before and after your responses.
Already on P6? You do not have to move your schedules to use it. Oracle documents a link from P6 EPPM that sends a project to Primavera Cloud for risk analysis and returns the pessimistic start and finish dates, before and after responses, to P6. Teams on P6 Professional can import XER or XML files, which bring their risks, probabilities, impacts and responses with them. Oracle itself suggests "P6 for planning and scheduling and Oracle Primavera Cloud for risk management". If your team still uses Primavera Risk Analysis, Oracle's desktop risk tool, Premier Support for its last release ended in March 2018, and Oracle now lists it among its archived applications.
How it is bought: Risk is part of the Schedule service, not a separate purchase, so the people who use it need Schedule. Oracle's service descriptions list no risk-only service.
What we would check first: whether your risk method (scoring, categories and matrices) is agreed across projects; which schedules are ready for quantitative analysis, with sound logic, constraints and three-point durations; and who owns the register on each project.
Checked on 19 October 2026: the register, response actions, Monte Carlo "probability curves showing expected time and cost outcomes", and "Quantitative risk analysis is available only in the context of projects" (Source 15, Risk Overview); "Risk thresholds and matrixes are configured in the workspace settings" and the "workspace-level library of reusable risks" (Source 15); "The program risk register displays a consolidated view of both program risks and project risks" (Source 15, Risk Register Overview); what a schedule needs for analysis (Source 15, Risk Analysis Prerequisites); the P6 EPPM link, the dates it returns, and the XER and XML import of risks (Source 16); "P6 for planning and scheduling and Oracle Primavera Cloud for risk management" (Source 1, product page FAQ); Primavera Risk Analysis 8.7, Premier Support ended March 2018, Sustaining Support only (Source 17); Risk as a module of Schedule, with no separate Risk service (Source 2, p8). Oracle's marketing speaks of "enterprise risk management" and "risk reporting across all projects and portfolios" (Source 1), but the help pages describe registers at project and program level only, so the page says "the same way on every project" rather than promising one register for the whole business (open point 12). To validate Risk as a value add for P6 teams is our view.
How Oracle sells it
Oracle sells Primavera Cloud as a few services. Most teams start with Schedule, which already holds risk, resources, tasks, costs and timesheets.
| Service | What it includes, in Oracle's terms | Needs |
|---|---|---|
| Oracle Primavera Schedule | Schedule, resources, risk, scope, tasks, costs and funds, timesheets, My Activities and the mobile app | The base service |
| Task Management | Tasks and the mobile app, for people who plan and update field work | Schedule |
| Progress | Timesheets, My Activities and the mobile app, for people who report progress | Schedule |
| Portfolio and Capital Planning | Costs and funds, portfolio analysis, resources, strategic alignment and ideas, for owners planning a capital program | None stated |
How it is counted. Per named user: Oracle counts every person authorised to use the service, whether or not they log in. Risk and resources are parts of the Schedule service, not separate purchases. Oracle's service descriptions set no minimum number of users; what applies to your order is a question to settle before you sign. No prices on this page: we work the numbers through with you.
Checked on 19 October 2026 in Oracle's Primavera Service Descriptions and Metrics, effective 10 September 2026 (Source 2): the services and their contents (pp8 to 12); Task Management and Progress require Schedule (pp9 to 10); the named user definition, "regardless of whether the individual is actively accessing the service" (p5); "all Cloud Services to be provisioned in a tenant must be licensed with the same metric" (p8); no minimum stated anywhere in the document. Whether a minimum applies to Australian orders. To validate Licensing lines are general information, not legal advice.
Moving from Microsoft Project
Oracle's import takes Microsoft Project XML files, one project at a time. The import is quick. The change in how your team works is the long part.
What comes across: project settings, activities, calendars, relationships, resource assignments and the WBS.
What to check:
- Save each project from Microsoft Project as an XML file. Oracle documents XML only, and its MPX import is not supported.
- Projects go in one at a time, into a workspace set up with a Microsoft Project connection.
- The file name becomes the project ID, which decides whether the import creates a project or updates one. Oracle warns that picking the wrong project can corrupt it.
- Oracle's help page does not list what is left behind, so check costs, baselines, custom fields, notes and resource rates on a test project before moving the rest.
- Primavera Cloud exports a project back to Microsoft Project XML, so a subcontractor or client still on Microsoft Project can keep working with you.
Our view of the order of work (drawn from Oracle's guides and our scheduling experience, not from a Primavera Cloud delivery):
- Prove it on two live projects. Import them into a Non-Production workspace and have your planners run a normal week in them.
- Design the workspaces before the rest goes in. Oracle says the structure "cannot easily be reorganized" once project data is in.
- Teach the scheduling habits it expects. Activities driven by logic and calendars, with few typed-in dates and hard constraints.
- Start new projects in Primavera Cloud. Let projects near the end finish in Microsoft Project.
- Bring site teams in last, once the schedules are trusted.
Checked on 19 October 2026: the import scope, "You can only import one project at a time", the Microsoft Project connection, the project ID rule and the caution that "Selecting a non-related project may corrupt the data in your existing project" (Source 3, last published 14 September 2026); export to Microsoft Project XML (Source 4, last published 14 September 2026); MPX import and templates not supported (Source 5, pp23 to 24, 152); Production and Non-Production workspaces (Source 5, p71) and the warning on the structure (Source 5, p11). The list of data to check, because Oracle's page names what comes across but not what stays behind. Steps 1, 3, 4 and 5 are our recommendation.
What changes for your team
The software is the easy part. Plan the change for each group.
- Planners. From one file per project to one database for all of them. Views replace the layouts saved in each file, codes live in workspaces, and the scheduling engine expects logic, not typed-in dates. Training is part of the move, not an extra.
- Project managers and site teams. Planning boards and the mobile app put weekly planning and progress in the same system as the schedule. That only works if site leads use it, so start with one willing team.
- Administrators. Workspaces, permission sets, dictionaries and the Microsoft Project connection are set up once and need to be set up well. Usernames are email addresses.
- IT. No servers or database to run. Oracle updates the service continuously and expects you to stay on a supported release; its policies give no right to skip an update. Data sits in the region chosen for your order, and Oracle states a 12-hour recovery time objective.
- Reporting. Reports and dashboards are built again in Primavera Cloud.
Checked on 19 October 2026: view types and workspace dictionaries (Source 7); usernames as email addresses (Source 5, p49); Task Management for field work and the mobile app (Source 2, pp8 to 10); the continuous-update model and the duty to stay on supported releases, with no right to skip one stated (Source 8, p14 s4.1.3); data stored in the region on the order (Source 8, p4); the 12-hour recovery time objective (Source 2, p9). The planner, site and reporting lines, from how the product is built. Which Australian region Oracle offers for Primavera Cloud; the hosting policies name APAC, not Australia (Source 8, p4). To validate
Already on P6?
Then moving your schedules to Primavera Cloud is a change of tool, not a move of P6 to the cloud; Oracle says so itself. Using it beside P6 for risk is a smaller step, covered under Risk above.
If what you want is P6 without the servers, that is P6 SaaS, covered on our Primavera P6 page. If you are weighing Primavera Cloud anyway, Oracle's 163-page migration guide lists what stops. Expenses, activity steps, the OBS, Visualizer, global search and replace, check in and check out, and cost accounts are among them. Network views stop at 6000 activities. Usernames must be email addresses, privileges are set up again, and reports do not transfer. Oracle documents five ways to move the data, from importing files to a bulk migration run by Oracle Consulting, and P6 and Primavera Cloud can run side by side, synchronised both ways.
What we would check first: which of those features your planners use every week, how big your largest schedules are, and what reads from or writes to P6 today.
Checked on 19 October 2026: "Oracle Primavera Cloud is not Primavera P6 in the Cloud" (Source 1, p3); in the migration guide, expenses (Source 5, p39), steps (pp22, 97), the OBS (p10), Visualizer (pp26, 97), global search and replace (p35), check in and out (pp25, 33), cost accounts (pp97, 103), the 6000-activity network view (pp131, 134), usernames (p49), privileges (p15), reports (p95), the five methods (p74), the framework "entirely managed by Oracle Consulting Services" (p77) and integration as "a bi-directional movement" (p75).
Costs beyond the subscription
The subscription is the number everyone sees. These are the ones that decide whether the move pays.
| Cost | What Oracle's documents say | What we would check |
|---|---|---|
| Getting set up | A direct order for the Schedule or Portfolio and Capital Planning service automatically includes Oracle's Administrator Enablement Service. Its contents are not described in the service descriptions. | What the enablement covers, and what your administrators still do themselves. |
| Moving the data | From Microsoft Project, Oracle's import takes one project at a time, and Oracle describes no migration package. From P6, Oracle Consulting's own migration is scoped at 100 projects, three baselines each, six workspaces and 25 users, and leaves out reports, dashboards, integrations and documents. | How many projects really need to move, and which can finish where they are. |
| Rebuilding what does not move | Reports, views, filters, user accounts and their permissions are set up again. | Which reports and views are used every week, so only those are rebuilt. |
| Integrations | One Oracle integration instance comes with the service, sized at two million messages a month. After three months in a row over that, Oracle may ask for a separate integration subscription. Changes to Oracle's pre-built integrations are yours to make. Using Primavera Gateway needs a Gateway licence, and it is the only route the migration guide gives to Primavera Unifier. Oracle's P6 25.12 release notes mark Gateway as deprecated, so check the current route with Oracle before you plan on it. | Every system that reads or writes schedule data today, and what each one needs. |
| Running two tools | Not addressed. Your current tool keeps running until its last project finishes. For Microsoft Project that is usually cheap; for P6, its support and hosting carry on beside the subscription. | The date the old tool can be switched off. |
| Growth | Under named users, everyone authorised counts, whether or not they log in, including people who only update progress or view reports. | Who needs access as projects are added, and at what level. |
| People | Not addressed. | Training for planners, administrators and site teams, including the scheduling habits a team new to critical path methods needs. |
No prices on this page. We work the numbers through with you, in writing, before anyone signs.
Checked on 19 October 2026: the Administrator Enablement Service included in direct orders (Source 2, pp8, 11, 14); the Microsoft Project import, one project at a time (Source 3); Oracle's migration services described for P6 only (Source 1, p5); Oracle Consulting's Base Migration scope and exclusions (Source 5, pp77, 81); reports and permissions not transferred (Source 5, pp15, 95); the integration instance, its two message packs and the three-month rule, and customisations being "Your responsibility" (Source 2, pp73 to 74); "The use of Gateway requires a Gateway license" and Unifier exchange through Gateway only (Source 5, pp32, 76); Gateway marked deprecated in P6 25.12 (Source 18); the named user definition (Source 2, p5). Oracle's current route from Primavera Cloud to Unifier now that Gateway is deprecated; what the Administrator Enablement Service contains, and whether an order through a partner includes it. To validate Licensing lines are general information, not legal advice.
Who it suits, and who should look at P6 instead
Our view, drawn from Oracle's documents and what we see in project teams. It is not a sales pitch for either product.
Likely to suit
- Teams stepping up from Microsoft Project or spreadsheets to their first enterprise scheduling tool.
- Teams running schedule, risk, site plans and cost in separate tools, who want them in one place.
- Contractors and owners running several projects that share people, who want one view of them.
- Teams that want field planning and mobile updates tied to the schedule.
- P6 teams that want one way of managing risk across their projects, without moving their schedules.
- Owners planning a capital program, with the Portfolio and Capital Planning service.
- Teams that left Project Online and still need critical path scheduling.
- Teams already in Oracle Aconex, whose Packages link only to Primavera Cloud. Aconex's Connected Cost add-on links to P6 EPPM as well.
Look at P6 instead, or test hard first
- Schedules of many thousands of activities, with heavy links between projects.
- Planners who rely on expenses, steps, cost accounts or the resource usage spreadsheet.
- Contracts that name Primavera P6 as the scheduling software. Primavera Cloud exports P6 files, but it is not P6, so read the clause.
- Change control that needs to set the date of every update.
What we would check first, four questions:
- What do your planners do every week in Microsoft Project, or P6, and what would they miss?
- How many projects share people, and how big are the largest schedules?
- What do your contracts say about scheduling software and file formats?
- Who on site will use the planning boards and the mobile app, and who will lead that change?
Checked on 19 October 2026: the Portfolio and Capital Planning contents (Source 2, pp10 to 12); field planning and mobile in the Schedule and Task Management services (Source 2, pp8 to 10); Aconex packages show "your Oracle Primavera Cloud schedule data" (Source 9); the features list and the 6000-activity limit (Source 5, pp97, 131, 134); a public example of a contract naming the software: "the software used must be either Primavera P6 or MS Project 2010" (Source 11, cl 39.3); the continuous-update model (Source 8, p14). Both columns are our view of who gains and who loses most, not Oracle's, and they are to test in the interviews To validate.
Questions we get asked
Can we bring our Microsoft Project schedules across?
Yes, as Microsoft Project XML files, one project at a time. Oracle's import brings project settings, activities, calendars, relationships, resource assignments and the WBS. Test two projects first, and check costs, baselines and custom fields by hand.
Can we still swap files with people on Microsoft Project or P6?
Yes. Primavera Cloud exports projects as Microsoft Project XML, and imports and exports P6 XER and XML files.
Our client's contract asks for P6. Will Primavera Cloud do?
Read the clause. Some contracts name the software, not only the file format. Transport for NSW's general requirements, for example, say "the software used must be either Primavera P6 or MS Project 2010". Primavera Cloud can produce a P6 file, but it is not P6, so ask the client before you rely on it.
How does it compare with P6?
It shares P6's scheduling logic, but it is a different product, and Oracle says so. Oracle's migration guide lists P6 features it leaves out, such as expenses, steps and cost accounts, while Primavera Cloud adds field planning, risk and portfolio in the same service. P6 and Primavera Cloud exchange data, so a team can start here and add P6 later, or keep P6 and use Primavera Cloud for risk.
We were on Project Online. Is this a replacement?
It can be, for construction and engineering teams that need critical path scheduling. Microsoft's own routes are the new Planner, Project Server Subscription Edition and Project Operations. Compare them on your own projects, not on a feature list.
Can planners keep Microsoft Project on the desktop?
They can, and Microsoft says the desktop application is not affected by the Project Online retirement. Two tools for one schedule means two versions of the truth, though, so we would set a date after which new work starts only in Primavera Cloud.
Where is our data held?
In the data centre region named on your order, or chosen when the service is set up. Oracle's policies define a region called APAC rather than Australia, so if your data must stay in Australia, have that written into the order. To validate
We schedule in P6. Can we use Primavera Cloud just for risk?
Yes. Oracle documents a link that sends a P6 EPPM project to Primavera Cloud for risk analysis and returns the pessimistic dates to P6, and P6 Professional users can import XER or XML files with their risks. The people who use it need the Schedule service, because risk is part of it. This is general information, not legal advice.
Who runs the move?
Your own team, a partner or, from P6, Oracle Consulting. We help you choose the route, plan the waves and check each project after it lands.
Checked on 19 October 2026: the Microsoft Project import and what it brings (Source 3); export to Microsoft Project XML (Source 4); XER and XML import and export (Source 5, p152; Source 6); the Transport for NSW clause (Source 11, cl 39.3); "Oracle Primavera Cloud is not Primavera P6 in the Cloud" (Source 1, p3) and the features it leaves out (Source 5, pp22, 39, 97, 103); data exchanged between the two "should your contracts, customers, partners or suppliers demand it" (Source 1, p3); Microsoft's alternatives and the desktop application "not affected" (Source 10); the region rule and the APAC definition (Source 8, p4); the framework managed by Oracle Consulting (Source 5, p77); the P6 EPPM risk link and the XER import of risks (Source 16); Risk inside the Schedule service (Source 2, p8). Whether Oracle offers an Australian data centre for Primavera Cloud, and how it is written on an Australian order. To validate
Check the fit before anyone signs
Tell us how your team schedules today, in Microsoft Project, P6 or spreadsheets, and how big your largest projects are. We will tell you, in writing, whether Primavera Cloud fits, what comes across, what changes and what the move involves. If P6, or staying where you are, fits better, we will say so.
Check the fit first
Sources
Checked against Oracle's documents on 19 October 2026
- Oracle, "Primavera P6 SaaS or Oracle Primavera Cloud" datasheet, version 1.0, 2026, and the Oracle Primavera Cloud product pages with their FAQs, oracle.com/anz/construction-engineering/primavera-cloud-project-management/ and oracle.com/construction-engineering/primavera-cloud-project-management/ (both updated 14 August 2026).
- Oracle, Oracle Construction and Engineering Primavera Service Descriptions and Metrics, effective 10 September 2026.
- Oracle, "Import Microsoft Project Data into Oracle Primavera Cloud", Primavera Cloud help, docs.oracle.com/cd/E80480_01/help/en/user/139509.htm, last published 14 September 2026.
- Oracle, "Export Oracle Primavera Cloud Data to Microsoft Project XML", Primavera Cloud administration guide, docs.oracle.com/cd/E80480_01/English/admin/app_admin_guide/162024.htm, last published 14 September 2026.
- Oracle, P6 EPPM to Primavera Cloud Migration Guide, October 2026 (163 pages).
- Oracle, P6 to Primavera Cloud Import Guide, October 2026.
- Oracle, "Key differences between Oracle P6 and Oracle Primavera Cloud", Primavera Cloud help, oracle.com/ce-help/primavera-cloud/primavera-cloud-getting-started-schedulers/schedule-differences-p6-and-primavera-cloud/ (undated, 2025).
- Oracle, Oracle Cloud Hosting and Delivery Policies, September 2026.
- Oracle Aconex help, "View Primavera Cloud schedule activity in Packages", help.aconex.com/packages/view-primavera-cloud-schedule-activity-in-packages/.
- Microsoft, "Microsoft Project Online is retiring: What you need to know", Microsoft Planner blog, techcommunity.microsoft.com/blog/plannerblog/microsoft-project-online-is-retiring-what-you-need-to-know/4450558 (updated 24 August 2026), and Microsoft 365 message MC1148537, published 5 September 2025.
- Transport for NSW, QA Specification TS 01566, General Requirements (Major Contracts), Edition 5 Revision 26, August 2024, clause 39.3.
- Microsoft Tech Community, "Project Monte Carlo" discussion, accepted answer of 13 July 2023 by a community member, not Microsoft.
- ProjectManager, "Microsoft Project for Construction: Pros & Cons", 12 June 2026, a competing software vendor.
- Oracle, "Third Party Usage Guidelines for Oracle Logos", oracle.com/legal/logos.html (updated 14 May 2024).
- Oracle, Primavera Cloud help on risk, docs.oracle.com/cd/E80480_01/: "Risk Overview", Risk Management User Guide (English/user_guides/risk_management_user_guide/88293.htm, 15 September 2026); "Risk Register Overview" (help/en/user/90778.htm, 21 July 2026); "Develop Risk Assessment Criteria" (help/en/user/88296.htm, 14 September 2026); "Risk Analysis Prerequisites" (help/en/user/93538.htm, 14 September 2026).
- Oracle, Primavera Cloud help, docs.oracle.com/cd/E80480_01/help/en/user/: "Risk Management Integration with P6 EPPM" (91072.htm) and "Send P6 EPPM data to Primavera Cloud for Risks" (100825.htm), both 14 September 2026; "P6 XML/XER Import Objects" (234146.htm, 18 August 2026).
- Oracle, Lifetime Support Policy: Oracle Applications, effective 7 August 2026 (Primavera Risk Analysis 8.7), oracle.com/assets/lifetime-support-applications-069216.pdf, and the Construction and Engineering documentation index, docs.oracle.com/en/industries/construction-engineering/index.html (Archived Applications).
- Oracle, Primavera P6 Cumulative Feature Overview, releases 18.8.1 to 25.12 (printed 19 October 2026), p100: Gateway deprecated in 25.12.