Requirements to Manually Upgrade from Version 7
You must upgrade your P6 EPPM database so it will work with the new version. The following list summarizes the procedures required to manually upgrade your database from P6 EPPM version 7.0:
Note
- All risk data fields are migrated when upgrading; existing fields are mapped to new fields and others will be mapped to text fields. See Risks Migration for more information.
- Back up your P6 EPPM database before beginning the upgrade process to ensure you will not lose any data due to unexpected problems. You should back up your database before you perform any of the steps in this document since the upgrade is not reversible. If you are unsure how to back up your database, do not proceed with the upgrade. Contact your database administrator or database vendor for assistance with backing up your database before performing the database upgrade.
- Manually run all scripts required to upgrade your existing P6 EPPM database.
- Test the new database to ensure that the upgrade succeeded.
- See Data Not Migrated During P6 EPPM Database Upgrade for details on what information will not migrate.
- Convert your Methodology Management data to projects before you upgrade P6 EPPM. See Converting Methodologies to Projects and Creating a Project Template From Projects for manual migration instructions.
Cautions:
- If you are a current Apache JackRabbit user and want to upgrade to the latest version of P6 EPPM, JackRabbit documents data will not migrate automatically. Refer to My Oracle Support's Knowledge Articles for information on manually migrating JackRabbit documents to Oracle Universal Content Management. Oracle recommends that you migrate the data before upgrading.
- If you are a current jBPM user and want to upgrade P6 EPPM, workflows and reviews data will not be available. You should close all workflows and reviews that are in progress before upgrading. You cannot migrate any of this data to the latest version of P6 EPPM.
Last Published Monday, December 8, 2025