--- title: P6 upgrades and migrations, done on evidence | Skyhigh PMO description: New installations, version upgrades, re-platforming and configuration overhauls for Primavera P6, with a defined scope. Usually the step after a diagnostic. image: https://skyhighpmo.com.au/hubfs/website/share-transformation.png --- [![Skyhigh PMO, Project Controls Solutions](https://skyhighpmo.com.au/hubfs/raw_assets/public/skyhigh-theme/images/skyhigh-logo-reverse.svg)](https://skyhighpmo.com.au/?hsLang=en-au) - Problems we solve Getting started with P6 - [**Transformation**New installs, upgrades and consolidation](https://skyhighpmo.com.au/transformation?hsLang=en-au) - [**Cloud**Cloud options, costs and the move](https://skyhighpmo.com.au/cloud?hsLang=en-au) Looking after P6 - [**Primavera Optimisation**Diagnostics, future state design and configuration reviews](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) - [**Primavera Support**From roadside help to a race-day pit crew. Choose your crew.](https://skyhighpmo.com.au/primavera-support?hsLang=en-au) - [**Project people**Planners and schedulers, for weeks rather than years](https://skyhighpmo.com.au/project-people?hsLang=en-au) Phase 2 Tools and licences - [**Licensing & Procurement**Licence advice, renewals and new licences](https://skyhighpmo.com.au/licensing-procurement?hsLang=en-au) - [**Oracle products**Learn more about each product](https://skyhighpmo.com.au/licensing-procurement#other-products) - [**Primavera P6**](https://skyhighpmo.com.au/licensing-procurement/primavera-p6?hsLang=en-au) - [**Oracle Primavera Cloud**](https://skyhighpmo.com.au/licensing-procurement/primavera-cloud?hsLang=en-au) - [**Primavera Unifier**](https://skyhighpmo.com.au/licensing-procurement/primavera-unifier?hsLang=en-au) Hidden at launch - [**Oracle Aconex**](https://skyhighpmo.com.au/licensing-procurement/oracle-aconex?hsLang=en-au) Hidden at launch - **Australian innovators' tools**Tools from Australian problem solvers Hidden: no agreement yet Reporting and P6 data - [**Reporting & Integration**Portfolio reporting, and P6 in your data warehouse](https://skyhighpmo.com.au/reporting-integration?hsLang=en-au) - [Insights Hidden at launch](https://skyhighpmo.com.au/insights?hsLang=en-au) - [About](https://skyhighpmo.com.au/about?hsLang=en-au) - [Contact](https://skyhighpmo.com.au/about#contact) [Test us on your issueTest us](https://skyhighpmo.com.au/test-us?hsLang=en-au) Menu Problems we solve Getting started with P6 - [**Transformation**New installs, upgrades and consolidation](https://skyhighpmo.com.au/transformation?hsLang=en-au) - [**Cloud**Cloud options, costs and the move](https://skyhighpmo.com.au/cloud?hsLang=en-au) Looking after P6 - [**Primavera Optimisation**Diagnostics, future state design and configuration reviews](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) - [**Primavera Support**From roadside help to a race-day pit crew. Choose your crew.](https://skyhighpmo.com.au/primavera-support?hsLang=en-au) - [**Project people**Planners and schedulers, for weeks rather than years](https://skyhighpmo.com.au/project-people?hsLang=en-au) Phase 2 Tools and licences - [**Licensing & Procurement**Licence advice, renewals and new licences](https://skyhighpmo.com.au/licensing-procurement?hsLang=en-au) - [**Oracle products**Learn more about each product](https://skyhighpmo.com.au/licensing-procurement#other-products) - [**Primavera P6**](https://skyhighpmo.com.au/licensing-procurement/primavera-p6?hsLang=en-au) - [**Oracle Primavera Cloud**](https://skyhighpmo.com.au/licensing-procurement/primavera-cloud?hsLang=en-au) - [**Primavera Unifier**](https://skyhighpmo.com.au/licensing-procurement/primavera-unifier?hsLang=en-au) Hidden at launch - [**Oracle Aconex**](https://skyhighpmo.com.au/licensing-procurement/oracle-aconex?hsLang=en-au) Hidden at launch - **Australian innovators' tools**Tools from Australian problem solvers Hidden: no agreement yet Reporting and P6 data - [**Reporting & Integration**Portfolio reporting, and P6 in your data warehouse](https://skyhighpmo.com.au/reporting-integration?hsLang=en-au) [Insights Hidden at launch](https://skyhighpmo.com.au/insights?hsLang=en-au) [About](https://skyhighpmo.com.au/about?hsLang=en-au) [Contact](https://skyhighpmo.com.au/about#contact) [Test us on your issue](https://skyhighpmo.com.au/test-us?hsLang=en-au) Transformation # Your projects depend on P6. Don't leave it to trial and error. New installations, upgrades, migrations and configuration rebuilds for Primavera P6, planned, scoped and done by people who have done them many times before. P6 is too important to your projects to learn on the job. The work usually starts from a diagnostic, so the scope rests on evidence. Your IT keeps the infrastructure, and we do the P6. [Take the first step](https://skyhighpmo.com.au/transformation#enquire) ## Pick the question that's on your mind. ← All questions Replay Each question opens its own hub. You'll see the problems behind it turn into outcomes, and the work that solves each one. - Is our P6 version out of date? - Working on old version, becomes: Upgraded to a supported release. Solved by Version upgrade. - Support date coming up, becomes: Upgraded before the date. Solved by Version upgrade. - Last upgrade was painful, becomes: Scope fixed on evidence first. Solved by Version upgrade. - Afraid to break the schedule, becomes: Tested by your planners before cut-over. Solved by Version upgrade. - New data centre or operating system, becomes: P6 moved in an agreed window. Solved by Re-platforming. - We need P6. Where do we start? - Won a project that needs P6, becomes: P6 ready before the project starts. Solved by New installation. - P6 schedules required in client format, becomes: Set up to the client's requirements. Solved by New installation. - Outgrown our current tool, becomes: Projects migrated into P6 cleanly. Solved by New installation. - Worried we'll set it up wrong, becomes: Standards and guardrails from day one. Solved by New installation. - No one here knows P6, becomes: Planners up to speed, fast. Solved by New installation. - We have the diagnostic. Who does the work? - Roadmap stalled after the diagnostic, becomes: Roadmap delivered to a defined scope. Solved by Roadmap delivery. - Planners too busy for the fixes, becomes: Fixes done alongside your people. Solved by Roadmap delivery. - IT has database skills, not P6 skills, becomes: P6 specialists on the P6 work. Solved by Roadmap delivery. - Does P6 still fit how we work? - Multiple P6 instances that should be one, becomes: One P6, cleanly consolidated. Solved by Consolidation. - Merger or restructure not in P6, becomes: Structure rebuilt for how you work now. Solved by Configuration overhaul. - Planners working around the setup, becomes: One standard core for everyone. Solved by Configuration overhaul. - Portfolio reports don't add up, becomes: Reporting that adds up across projects. Solved by Configuration overhaul. ## Diagnostic done. What's next? Upgrades, migrations and rebuilds most often go wrong because the scope was guessed. We start from a diagnostic, ours or one you already have, so the scope rests on what is actually in your environment. Our diagnostic shows you what your P6 holds and what to fix first, including the versions, the integrations, the customisations and the data to clean up before anything is carried across, and our [Primavera Optimisation page](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) explains how it works. Then the work is done to a defined scope, as a fixed fee or on time and materials, whichever suits your project. Starting from scratch? A new install starts from your requirements and your clients' requirements instead, such as how you plan, how you report and who needs access. ![A health check report stamped complete, beside a to-do list with nothing ticked yet](https://skyhighpmo.com.au/hubfs/website/illus-transformation-health-done.png) ### What Skyhigh does - We do the P6 work. That means installing and configuring the application, upgrading the database and the application, moving P6 between environments and rebuilding the configuration. - We test with your planners before cut-over, and then we run the cut-over. - We write down what changed, so the next upgrade is easier. ### What your IT keeps - Your IT keeps the infrastructure, which covers the servers, storage, network, backups, database platform, access and security. - Your IT also keeps the change windows and the approvals. - We need two things from you. Your IT people need to be available while the work is on, and any configuration change needs an executive sponsor. [Start with the scope](https://skyhighpmo.com.au/transformation#enquire) Where it usually hurts ## Five problems we see most Pick the one that sounds like yours, or keep scrolling. 1. The report says what to do. Now someone has to do it. 2. A new P6 to install 3. Upgrade or migration due 4. The organisation changed. P6 didn't. 5. Multiple P6 instances that should be one 1 of 5 ### The report says what to do. Now someone has to do it. An Optimisation diagnostic ends with a prioritised roadmap and the critical fixes already done. The rest of the roadmap is where many teams stall. The planners are too busy, IT has database skills rather than P6 skills, and each item needs someone who has done it before. We take the roadmap, or your own list, and deliver it as a defined scope in an agreed order, with your people alongside. That can include database and middleware changes, the configuration clean-up, reporting fixes and training. The findings stay yours, and we do the work you don't have the hands for. [See how the work runs](https://skyhighpmo.com.au/transformation#how-it-works) ![A diagnostic report with ticks down its list](https://skyhighpmo.com.au/hubfs/website/illus-transformation-after-diagnostic.png) ### A new P6 to install You have bought P6, and now it has to be set up like the business application it is. That means a server with database backups, and P6 Professional delivered to the planners' machines securely and efficiently. Above all, you need a configuration that fits how you plan, not the defaults out of the box. Done well, the first install sets the standard core that everything else is built on. Done in a hurry, it becomes the messy configuration somebody diagnoses in three years. We [install and configure](https://skyhighpmo.com.au/transformation#install-upgrade) P6 EPPM and P6 Professional on your chosen platform, with a governance framework and a core configuration agreed with you first, and your planners shown how to work in it. [See how we install P6](https://skyhighpmo.com.au/transformation#install-upgrade) ![A technical person at a desk, head in hand, an error on the screen and install guides piled around them](https://skyhighpmo.com.au/hubfs/website/illus-transformation-lost-in-guides.png) ### Upgrade or migration due Oracle's Premier Support for each P6 release runs for about five years from its release. A new release comes out every year, and an environment that isn't patched or upgraded can become a cyber risk for your business. Patches and upgrades also need planning, so your project teams aren't disrupted. A move to the cloud, a new data centre or a new operating system version forces the same decision. We plan the upgrade or migration from a solid understanding of your environment, clean up the data that shouldn't carry over, test with your planners, and cut over within an agreed window. [When does Premier Support end for your version?](https://skyhighpmo.com.au/transformation#premier-support-dates) [See how we upgrade P6](https://skyhighpmo.com.au/transformation#install-upgrade) ![A race car marked P6 pulling into its pit box, the crew ready with a fresh tyre, wheel guns and a board reading Upgrade](https://skyhighpmo.com.au/hubfs/website/illus-transformation-pitstop.png) ### The organisation changed. P6 didn't. A merger, a new PMO, a different delivery model, or simply ten years of projects: the enterprise structure, the codes, the calendars and the security model were built for an organisation that no longer exists. Working around it costs every planner time, and reporting across the portfolio stops meaning anything. A governance framework review and a [configuration overhaul](https://skyhighpmo.com.au/transformation#p6-configuration) rebuild the standard core to fit how you work now: what the structure is, who owns what, what is standard and what is allowed to vary. It changes how people work, which is why executive support is one of the two things we ask for before we start. [See how we rebuild it](https://skyhighpmo.com.au/transformation#p6-configuration) ![An organisation chart redrawn over a Gantt](https://skyhighpmo.com.au/hubfs/website/illus-transformation-configuration.png) ### Multiple P6 instances that should be one Business units, mergers or new leadership can leave an organisation running several P6 environments, each with its own codes, calendars, users and support to pay for. Planners move between them, and nobody can report across the portfolio. We bring them into one P6. We document each environment and agree one standard core with you first. Then we migrate the projects, your planners check them, and the old environments are retired. Often the first step is a [configuration review](https://skyhighpmo.com.au/primavera-optimisation#configuration-review), which shows how far each P6 has drifted and designs the one standard they all move into. [See how we bring them together](https://skyhighpmo.com.au/transformation#p6-configuration) ![Four different project structures, each in its own P6, joined to one company in the centre](https://skyhighpmo.com.au/hubfs/website/illus-transformation-consolidation.png) What we do ## Installs and upgrades We do the P6 work, and your IT keeps the infrastructure it already runs. - **New installation.** We install and configure P6 EPPM and P6 Professional on your servers or your chosen cloud. That covers the database, the application tier, the planners' machines, integrations and security, and the first configuration is agreed with you before anyone logs in. - **Version upgrade.** We start from a clear picture of your environment, including its versions, integrations and customisations, and the data to clean up before it moves. We build and test the upgrade in a test environment, your planners check it, and then we cut over in an agreed window. - **Moving P6.** We move P6 to a new data centre, a new operating system or the cloud, with the same groundwork and testing. Our [Cloud page](https://skyhighpmo.com.au/cloud?hsLang=en-au) helps you compare the cloud options and make an informed choice. - **Moving from another tool?** We bring your current projects across from Microsoft Project, spreadsheets or another scheduler, so the work already under way runs in the new P6 from day one. Every job ends with a written record of what changed, so the next upgrade starts from facts. [Plan your install or upgrade](https://skyhighpmo.com.au/transformation#enquire) ![A download package, an arrow, and what it becomes once installed: a server tagged P6, a database and a firewall with a shield](https://skyhighpmo.com.au/hubfs/website/illus-transformation-installs.png) What we do ## Primavera configuration Every P6 needs a configuration that fits how the organisation plans and reports, and someone who owns it. New starters need one from day one, and a P6 that has been running for years usually needs one rebuilt. - **The standard core.** We design the EPS and OBS, activity codes, calendars, resources, layouts, reports and user security with you, so your schedules come out in the format your clients ask for. Everything is documented. - **The rules that keep it right.** We agree who owns what, what is standard and what may vary, and we set up a change process that decides what gets added. - **Three starting points.** We build a first configuration for a new install, rebuild one after a merger or restructure, or design one configuration for several P6s being brought together. Not sure how far yours has drifted? Our [configuration review](https://skyhighpmo.com.au/primavera-optimisation#configuration-review) measures the drift and designs the fix, and this is where the fix gets built. [Talk about your configuration](https://skyhighpmo.com.au/transformation#enquire) ![A project structure tree with its standard core outlined in orange, beside a calendar, a code tag and a padlock](https://skyhighpmo.com.au/hubfs/website/illus-transformation-p6-configuration.png) How it works ## From the first step to cut-over There are five steps, and the evidence comes first. The scope is agreed before anything is touched, as a fixed fee or on time and materials. 1. 1 ### Take the first step Fill in the form at the bottom of this page. We read every enquiry and aim to be in touch within one business day. 2. 2 ### Evidence We start from an Optimisation diagnostic if you haven't had one. If you have, or your team already knows its environment well, we start from what you know. 3. 3 ### Scope and price We agree what is in and what is out, what your IT keeps and what we need from you. We also agree whether it is a fixed fee or time and materials, and nothing starts until the scope is agreed. 4. 4 ### The work Before the work starts, your IT team provisions the servers and sets up our access. We give them the list at the scoping step, because waiting for access is where projects most often lose time. Then we build, migrate or rebuild in a test environment first, and your planners test it before anything goes live. 5. 5 ### Cut-over, and the record We cut over in an agreed window and give you a written record of what changed. If you want it kept that way, Primavera Support can look after it from there. [Take the first step](https://skyhighpmo.com.au/transformation#enquire) Common questions ## Questions people ask Is Oracle's support for our version really ending? Premier Support for a P6 release runs for five years from its release. After that, Sustaining Support continues for as long as you keep paying for support, but no new fixes, security patches or certifications are created for that release. The dates for each release are below, with the source. | Primavera P6 EPPM and P6 Professional release | Premier Support ended or ends | | --- | --- | | 18.x | August 2023 | | 19.x | December 2024 | | 20.x | December 2025 | | 21.x | December 2026 | | 22.x | December 2027 | | 23.x | December 2028 | | 24.x | December 2029 | | 25.x | December 2030 | Source: [Oracle Lifetime Support Policy for Oracle Applications](https://www.oracle.com/us/assets/lifetime-support-applications-069216.pdf). Do we have to move to the cloud? No. An upgrade works as well on your own servers as in the cloud. Moving to the cloud does bring advantages, and our [Cloud page](https://skyhighpmo.com.au/cloud?hsLang=en-au) helps you compare the options and see what to expect before you decide. Fixed fee or time and materials? Whichever suits how your organisation funds the work. Our preference doesn't drive the recommendation, because every organisation funds its projects differently. A fixed fee suits a scope that a diagnostic has fully defined. Time and materials suits work that can't be fully known up front, and we agree a cap at the start. What do you need from our IT? We need the infrastructure available, our access set up in advance, someone who can open change windows, and a test environment. We write the list at the scoping step, so nobody is surprised. How long does an upgrade take? It depends on the versions, the integrations and the state of the data. We give a duration at the scoping step, not before. Can you do it without a diagnostic first? Yes, if you already know your environment well, with its versions, integrations and customisations written down. If not, the diagnostic is the cheaper way to find out what the upgrade will hit. What happens to our customisations and integrations? We record each one before the work starts and test it in the new version. Then we carry it across, replace it or retire it, with your agreement. Nothing is dropped quietly. Will our planners need retraining? Not for an upgrade from one release to the next. A short session on what's new in the version is usually enough. [Ask a question we have not answered](https://skyhighpmo.com.au/transformation#enquire) ## Not sure it is an upgrade you need? Start with the diagnostic. The Optimisation diagnostic gives you the clear picture of your environment that an upgrade needs, and the critical fixes get done along the way. [See what the diagnostic covers](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) [Take the first step](https://skyhighpmo.com.au/transformation#enquire) Enquiry ## Take the first step Tell us what is in front of you, such as the version you are on, what is forcing the decision and when it has to be done by. We read every enquiry and aim to be in touch within one business day. ### What happens next - We read every enquiry and aim to be in touch within one business day. - If a call would help, we offer times. [![Skyhigh PMO](https://skyhighpmo.com.au/hubfs/raw_assets/public/skyhigh-theme/images/skyhigh-logo-reverse.svg)](https://skyhighpmo.com.au/?hsLang=en-au) Experienced Primavera P6 and Project Controls specialists, working with organisations that deliver Major Projects in Australia © 2026 Skyhigh PMO Pty Ltd · ABN 80 653 189 881 · ACN 653 189 881 [Contact](https://skyhighpmo.com.au/about#contact) · [Privacy policy](https://skyhighpmo.com.au/legal/privacy-policy?hsLang=en-au) · [Terms](https://skyhighpmo.com.au/legal?hsLang=en-au) · [Partner with us](https://skyhighpmo.com.au/partner-with-us?hsLang=en-au)Hidden until the page is built · Cookie settings Oracle and Primavera are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.