Migration Methods
Primavera Cloud supports various methods for migrating your data from P6. These include:
- Import
- P6 XML or XER Import
- Integration
- Direct Integration with P6
- Integration using Primavera Gateway
- Project Integration Framework (PIF)
- P6 Web Services and Primavera Cloud API
All migration methods are described below. Review their use cases to decide which will work best for you. Use the links provided to access the documentation material for each method.
Each of the migration methods listed below supports the transfer of a different set of data from P6 to Primavera Cloud. Depending on the data you want to migrate, certain methods might be better suited to meet your needs. For more information on the data objects that are supported by each method, see Transferable and Nontransferable Data.
Import
Importing is a manual, one-way movement of projects and project data from an external file to a specific Primavera Cloud workspace. You can use P6 XML or XER import method to migrate your data from P6 to Primavera Cloud:
- P6 XML or XER Import: You can import projects and project data using P6 XML or XER fomats. First, prepare your data for export from your P6 application. Multiple projects can be included in the XML or XER export file. After the XML or XER file is created, you can import it into Primavera Cloud and choose which projects to add, update, or ignore. If existing project data will be affected, you can decide which objects should be updated, kept the same, or ignored.
The import method is performed from within Primavera Cloud. This method requires the least amount of setup, but must be manually run each time. It cannot be scheduled. Import only brings in data that is associated with the projects in the file. It cannot transfer full object dictionaries.
The P6 EPPM and P6 Professional Import Guide covers all of the steps in the P6 XML or XER import process, including how to prepare your P6 environment for export, prepare your Primavera Cloud application for import, and validate your data after the import is complete.
Integration
Integration is a bi-directional movement of data between P6 and Primavera Cloud. During integration, business objects and their data fields are transferred between applications. Field mapping templates list the objects and fields to be transferred and how they should be mapped from fields in the source application to fields in the destination application. A business flow is a specific set of field mapping templates and parameters that fulfill a particular data requirement. A single business flow might define the transfer of all resources, project activities, or project risks from P6 to Primavera Cloud or from Primavera Cloud to P6. The data contained in a business flow is transferred by adding the business flow to a synchronization job, specifying its parameters, and then running the synchronization. You can run synchronizations on demand or schedule them to run at regular intervals.
You can use integration to migrate a select number of dictionaries from P6 to Primavera Cloud, including calendars, resources, and roles. You can also migrate project-level data from a P6 project to a corresponding project in Primavera Cloud.
There are two integration methods that you can use to migrate your data from P6 to Primavera Cloud:
- Direct Integration with P6: The direct integration method requires minimal configuration to set up and provides default business flows and synchronizations to support the most common data migration requirements. Use this method if your organization does not require additional customization. Direct integration is performed from within Primavera Cloud.
Establish a direct connection between your chosen Primavera Cloud and P6 deployments. Multiple connections can be made if you want to integrate with different P6 deployments. Each connection must contain at least one workspace to which the P6 data will be transferred. The default business flows are automatically available to the connected workspaces and the projects within the workspace. You can add your own field mappings, codes, UDFs, and notes to the provided business flows, but you cannot modify existing mappings. You cannot add or delete business flows or synchronizations using this method. If you require a more customized setup, you should use the Integration using Primavera Gateway method.
The P6 EPPM Integration section of the Primavera Cloud Help explains how to add a connection from Primavera Cloud to P6, modify integration settings, and modify the default business flows. When you are ready to migrate data, follow the steps to run synchronizations at the workspace or project levels. You can monitor the status of synchronization jobs and view their business flow details.
Note: You can use the Migrate Project Data from P6 to Primavera Cloud business flow if you want to bulk-migrate project data from P6 to Primavera Cloud. For more information on using this business flow, refer to the Modify the Migrate Project Data from P6 to Primavera Cloud Business Flow topic of Oracle Primavera Cloud Help.
- Integration using Primavera Gateway: Use this method if your organization requires customized solutions beyond the default options provided by Primavera Cloud. Primavera Gateway provides more default business flows than the direct integration method, but you can also create new business flows if these don't fit your needs. Primavera Gateway is required to add or modify field mapping templates, business flows, or synchronizations. You must also use Primavera Gateway to create connections to P6 and Primavera Cloud. After these connections are established, you can run synchronizations from Primavera Gateway. You can also add the synchronizations from Primavera Gateway to your Primavera Cloud deployment and run the synchronizations from Primavera Cloud.
Consult the Primavera Gateway documentation for a comprehensive selection of Gateway information including user administration, end user help documentation, custom business flow and synchronization configurations, connecting P6 and Primavera Cloud applications, and transferring data between P6 and Primavera Cloud. The use of Gateway requires a Gateway license.
After your Gateway deployment is connected to P6 and Primavera Cloud and you have created the necessary business flows and synchronizations, you can add and run the synchronizations from Primavera Cloud. See the Integrate Gateway section of the Primavera Cloud Help for more information.
Project Integration Framework
Project Integration Framework (PIF) is a data migration tool that can be used when you need to migrate a lot of projects from P6 to Primavera Cloud. PIF consists of configurable pre-built interfaces that can automate data migration and significantly reduce your migration timeline. The PIF migration utility leverages P6 XML import to migrate project data and can be extended to transfer data that is not supported by P6 XML import.
Note: Data migration using PIF is entirely managed by Oracle Consulting Services.
To migrate data using PIF, you first need to identify the P6 projects you want to transfer and assign them a code. The PIF tool then exports the identified projects to P6 XML format and imports them in Primavera Cloud in the appropriate workspace.
Migration using PIF is done in two phases - test and final. In the test migration phase, the projects are transferred to the non-production workspace so you can test and validate the data. After data validation, the projects are moved to the production workspace during the final migration. It is recommended that you set up the workspace hierarchy before moving the projects to the production workspace so they can be placed in their appropriate workspaces.
Based on your organization's needs, you can choose between two types of migration options using PIF - Base and Advanced.
- Base Option: The Base option is an out-of-the-box solution with a fixed scope. With this option, Oracle Consulting Services will help you migrate up to 100 active project schedules with global data and up to three most recent baselines for each project schedule. They can also create a backup of your inactive projects by exporting them into P6 XML format. Additionally, they will also do the following configurations in Primavera Cloud to support your data migration:
- Create six workspaces with their associated settings for activities, projects, and programs
- Configure up to five user groups and five root workspace permission sets for projects, portfolios, and programs
- Assign up to 25 users to workspaces, projects, user groups, and permission sets
- Configure global application settings
Note: The Base migration option cannot be used to transfer BI reports, dashboards, integrations, documents, MS SQL to Oracle conversion, P6 database consolidation, and training.
- Advanced Option: The Advanced option is highly configurable and can accommodate your organization's specific data migration requirements. You can use the Advanced option to transfer all data that is included in the Base option, plus your specific requirements from the following:
- Activity Codes
- BI reports
- Calendars
- Global Data
- Integrations
- Layouts
- Project Codes
- Project Schedules
- Resource Assignments
- Resource Codes
- Resources
- Role Assignments
- Roles
- UDFs (called Configured Fields in Primavera Cloud)
- Units of Measure
Note: Contact your Oracle sales representative if you would like to explore the PIF method to transfer your P6 data to Primavera Cloud.
P6 EPPM Web Services and the Oracle Primavera Cloud API
P6 EPPM Web Services is a toolset that enables developers to integrate external applications with P6 EPPM. It can be used to create custom solutions that combine P6 data with other technologies. The Oracle Primavera Cloud API provides a more flexible environment for configuring your Primavera Cloud data.
There is one method incorporating the P6 EPPM Web Services and Oracle Primavera Cloud API technologies that you can use to migrate your data from P6 to Primavera Cloud:
- P6 EPPM Web Services and the Oracle Primavera Cloud API: Use this method to retrieve supported data from your P6 deployments and create corresponding data in Primavera Cloud. P6 EPPM Web Services supports both cloud and on-premises P6 deployments. This solution offers greater flexibility and customization than the import or integration methods, but it is also more complex to configure.
The Integrating section of the P6 EPPM User and Integration Documentation contains links to the P6 EPPM Web Services Programming Guide and the P6 EPPM Web Services Reference Guide. Consult the Oracle Primavera Cloud REST API documentation for comprehensive operating information for the Primavera Cloud API.
Related Topics
Transferable and Nontransferable Data
Last Published Tuesday, May 21, 2024