Transferable and Nontransferable Data

Each migration method supports the transfer of different sets of data objects from P6 to Primavera Cloud. An object that is transferable using one method may not be transferable using another method. Use the information below to review how the import, integration, Project Integration Framework (PIF), and P6 EPPM Web Services methods transfer data, including the data that is transferable using any of the methods and the data that cannot be transferred using any of the methods. For more information on each method, see Migration Methods.

Transferable vs. Nontransferable Data

The Transferable Data section contains the P6 data objects that are transferable by at least one of the migration methods. Transferable Data is separated into Workspace-level Data and Project-level Data tables. These tables identify where each object is stored in Primavera Cloud, which may be different than the object's location in P6. In general, transferable workspace-level data consists of dictionary objects such as calendars, codes, locations, and UDFs, which can all be assigned to child workspaces and projects within a workspace. Transferable project-level data contains project-specific dictionaries such as calendars and codes, and project-specific objects such as activities, resource assignments, risks, and the WBS. While workspaces store workspace-level codes, code values, UDFs, and UDF values, and projects store project-level codes and code values, the assignment of these values to project objects is stored with the project. When a transferable object is moved between applications, its associated data is also included. For example, each activity that is transferred includes its dates, durations, units, costs, types, code and UDF assignments, and resource assignments.

Data that is not transferable using any of the migration methods is listed in the Nontransferable Data section. This section is separated into two lists. The first lists P6 data that cannot be transferred but is supported in some form by Primavera Cloud. The second lists P6 data that cannot be transferred, is not supported by Primavera Cloud, and has no functional equivalent.

Import

The P6 Import migration method transfers projects and their associated data into Primavera Cloud using an XML or XER file. Any workspace-level data that is assigned to the project is stored in Primavera Cloud at the project's parent workspace level and assigned to corresponding project-level objects. Project-level data is stored with the project. P6 data that is not associated with the projects in the XML or XER file is not included in the file. You cannot use the import method to transfer entire P6 dictionaries such as resources, roles, risk matrixes, and risk thresholds.

Note: Primavera Cloud supports baselines and scenarios exported as part of their current schedule or individual projects in XML format. Baselines and scenarios can only be exported from Primavera Cloud as individual projects in XER format.

Integration

The Direct Integration with P6 and Integration using Primavera Gateway methods support two business flow types: Global and Project. Global business flows (called "Master" business flows if running integrations from Primavera Gateway) include workspace-level data objects that influence all subsequent transfers from P6 to Primavera Cloud. You can run global business flows to transfer entire P6 dictionaries for the following objects: Calendars, Enterprise Project Structure (transferred as "EPS" codes to Primavera Cloud), Locations, Resources, Roles, and User Defined Fields (UDFs). The Location and UDF global business objects are only supported using the Integration using Primavera Gateway method. Global business objects are stored by the workspace where the integration was run or, if run from Primavera Gateway, the workspace destination specified. Global business flows are an efficient method to migrate entire object dictionaries from P6 to Primavera Cloud, but there are some alternative options if you want to limit what is transferred. Use project business flows, described below, to only transfer objects associated with a project. Project business flows do not transfer entire dictionaries. You can also use the Integration using Primavera Gateway method to set up global data filters, which limit the global objects that are sent to Primavera Cloud. For example, if you only want to transfer a subset of your P6 Resource dictionary, use filters to specify the resources that are transferred.

Project business flows include workspace-level and project-level data objects that are associated with a particular project. Project-level data is stored with the project where the integration was run. Workspace-level data assigned to the project is stored in the project's parent workspace. P6 data that is not associated with the project is not included in a project business flow. Some of the objects supported in global business flows (calendars, resources, roles, UDFs) are also supported in project business flows, but only for data assigned to the project. For example, the only resources that will be transferred from P6 to Primavera Cloud in a project business flow are the resources assigned to activities in the project. These resources will be stored in Primavera Cloud at the workspace level, made available to the project-level resource dictionary, and assigned to applicable activities in the project. If you want to transfer an entire P6 dictionary to Primavera Cloud, run a global business flow for an object that supports it.

Both integration methods offer default solutions to help you get started. Because the Direct Integration with P6 method is intended to handle the most common migration requirements, fewer business objects are supported than the Integration using Primavera Gateway method. Use the Integration using Primavera Gateway method if you need to migrate the additional data objects it supports or if you require additional customizable integration options.

Project Integration Framework

The PIF tool provides a data migration solution that is entirely managed by the Oracle Consulting Services and can be configured and customized to suit your organization's needs. You can use the Base migration option to migrate up to 100 active project schedules with limited global data, migrate up to three most recent baselines for each project schedule, and create a backup of inactive projects by exporting them into P6 XML format. Or, you can opt for the Advanced option to transfer all global data, BI reports, layouts, integrations, and project schedules. The Advanced option can be customized to accommodate your organization's specific data migration requirements, which are not covered in the Base option.

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. Before migrating, you must ensure there are no duplicate role IDs in P6 as it can cause the XML import to fail. It is also recommended that you delete any unused codes, global and resource calendars, roles and resources, UDFs, resource curves, and units of measures before migrating.

The PIF utility supports migrating all data that P6 XML import supports. It can also optionally be extended to migrate global data that is not referenced by the projects you want to migrate.

P6 EPPM Web Services and Oracle Primavera Cloud API

The P6 EPPM Web Services and Oracle Primavera Cloud API method is completely customizable, enabling you to read P6 data and recreate it in Primavera Cloud. There are fewer limitations inherent in this method than import or integration. The data extracted from P6 using P6 EPPM Web Services must be supported by a Primavera Cloud API endpoint, and the type of data must be compatible between the two tools. Due to the less restricted nature of web services and APIs, it may be possible to move data between two different and dissimilar objects as long as both support the type of data being moved. This includes data that is supported in Primavera Cloud but is nontransferable using any of the other methods. For this reason, an explicit list of transferable and nontransferable data has not been provided for this method. If you want to learn more about the business objects supported by P6 EPPM Web Services and the Primavera Cloud API, consult their respective documentation libraries, found in Migration Methods.

Transferable Data

Transferable Workspace-level Data

Data Objects

P6 XML/XER Import

Direct Integration with P6

Integration using Primavera Gateway

Project Integration Framework

Calendars

  • Global
  • Resource
  • Project

Note: P6 XML or XER Import transfers Project calendars to the project level, while the integration methods transfer Project calendars to the workspace level. In all methods, Global and Resource calendars are transferred to the workspace level.

Y

Y

Y

Y

Codes & Code Values

  • Activity
  • Resource
  • Project

Notes:

  • Codes marked as Secure in P6 are transferable, but there is no such designation in Primavera Cloud.
  • EPS and Global activity code types are transferred to the workspace level. Project activity code types are transferred to the project level.

Y

Y

Y

Y

EPS Codes

Note: The EPS in P6 is sent to Primavera Cloud as a hierarchical structure of project code values representing the P6 EPS. Using these codes is only necessary if you plan to transfer data from Primavera Cloud to P6. Assign a P6 EPS code value to a Primavera Cloud project to ensure the project data is sent to the correct EPS node in P6 when you run the appropriate Primavera Cloud to P6 integration.

 

Y

Y

 

Locations

 

 

Y

 

Resource and Role Availability

Y

 

 

Y

Resource and Role Rates

Y

Y

Y

Y

Resource Code Assignments

Y

Y

Y

Y

Resource Curves

Y

 

 

Y

Resources and Roles (and hierarchical parents)

Notes:

  • P6 XML or XER Import only includes resources and roles that are assigned to activities in the projects being imported. These resources and roles are stored in their project's parent workspace, made available in the project-level resource and role dictionaries, and assigned to applicable activities.
  • Integrations run with global business flows that include resource or role business objects will transfer the entire P6 resource or role dictionaries into Primavera Cloud. If you run the integration from Primavera Gateway, you can include resource and role filters to limit what is transferred. If you only want to transfer resources or roles that are assigned to specific projects, run project business flows that include resources or roles. Transferred resources and roles are stored at the workspace level.

Y

Y

Y

Y

Resource/Role Associations

Y

 

Y

Y

Risk Threshold Levels

Y

Y

Y

Y

Risk Thresholds

Y

Y

Y

Y

Risk Matrix Scores

Y

Y

Y

Y

Risk Matrix Thresholds

Y

Y

Y

Y

Risk Matrices

Note: P6 XML or XER Import only includes the single risk matrix assigned to each project being imported.

Y

Y

Y

Y

Units of Measure

Y

 

Y

Y

User Defined Fields (UDFs)

  • Activity
  • Project

Notes:

You can only transfer Project UDFs with a UDF Type of "Manual."

  1. Resource Assignment
  2. Risk Fields
  3. WBS Fields

Y

Y

Y

Y

Transferable Project-level Data

Data Objects

P6 XML/ XER Import

Direct Integration with P6

Integration using Primavera Gateway

Project Integration Framework

Activities

Y

Y

Y

Y

Activity Codes and Code Values (Project-level)

Y

Y

Y

Y

Activity Notebook Topics

Y

N

N

N

Activity Relationships

Y

Y

Y

Y

Activity Risk Assignments

Y

Y

Y

Y

Baselines

Notes:

  • You can transfer any three baselines in the import file using P6 XML Import and you can transfer the three most recent baselines per import using PIF.
  • Baseline types can only be imported (as baseline categories in Primavera Cloud) using P6 XML Import if assigned to baselines and selected for import.
  • P6 XER format does not support baselines; therefore, projects are exported without baselines in XER format.

Y

Y

Y

Y

 

 

Calendar Assignments

  • Activities
  • Projects
  • Resource Assignments

Y

Y

Y

Y

Code Assignments

  • Activity
  • Project

Y

Y

Y

Y

Project Calendars

Note: P6 XML or XER Import transfers Project calendars to the project level, while the integration methods transfer project calendars to the workspace level.

Y

Y

Y

Y

Project Default Calendar

Y

 

 

Y

Project Settings

Y

 

 

Y

Projects

Note: The integration methods support the transfer of project data, but not the projects themselves.

Y

 

 

Y

Resource and Role Assignment Costs

Y

 

 

Y

Resource and Role Assignment Units

Y

Y

Y

Y

Resource and Role Assignments

Notes:

  • P6 XML or XER Import only includes resources and roles that are assigned to activities in the projects being imported.
  • Project business flows that include resource or role business objects will only transfer resources or roles assigned to the project where the integration was run. Run global business flows that include resources and roles if you want to transfer your entire P6 resource or role dictionaries.
  • Resources and roles that are imported or transferred using a project business flow are stored in their project's parent workspace, made available in the project-level resource and role dictionaries, and assigned to applicable activities.

Y

Y

Y

Y

Resource and Role Rates

Y

 

Y

Y

Risk Impacts

Y

Y

Y

Y

Risk Matrix and Threshold Assignments

Y

Y

Y

Y

Risk Matrix Scores

Y

Y

Y

Y

Risk Response Actions

Note: Primavera Cloud supports a single response plan for each risk. Only response actions under an active response plan will be transferred.

Y

Y

Y

Y

Risk Response Action Impacts

Note: The lowest response action impact values under each active response plan will be transferred and stored as post-response values at the risk level.

Y

Y

Y

Y

Risk Response Plans

Note: Primavera Cloud supports a single response plan for each risk. Only response actions under an active response plan will be transferred.

Y

Y

Y

Y

Risks

Y

Y

Y

Y

Scheduler Settings

Y

Y

Y

Y

UDF Assignments

  • Activity
  • Project
  • Resource Assignment
  • Risk
  • WBS

Y

Y

Y

Y

WBS Spreads

 

Y

Y

 

Work Breakdown Structure (WBS)

Y

Y

Y

Y

WBS Summary Activities

Y

Y

Y

Y

Nontransferable Data

Nontransferable Data Supported in Primavera Cloud

The P6 data listed below cannot be transferred using any of the migration methods, but the functionality is supported in Primavera Cloud. You must manually create data for these objects in Primavera Cloud if you still want to use them. Many pages in Primavera Cloud support downloadable spreadsheet templates, which enable you to quickly create large amounts of object-specific data and import it into Primavera Cloud. Some of the objects listed may have been renamed in Primavera Cloud, or there may be differences in functionality. See Terminology Differences and Functional Differences for more information.

Nontransferable Data Not Supported in Primavera Cloud

The P6 functionality and data listed below cannot be transferred using any of the migration methods, and there is no functional alternative supported by Primavera Cloud.


Last Published Tuesday, May 21, 2024