Import Objects
P6 XML and XER files exported from a P6 application contain P6 projects and their associated data. Only objects, values, and definitions that are explicitly assigned to projects or their activities are included in the P6 XML or XER file. This includes the parent hierarchy of applicable objects, such as resources or roles. If data in P6 is not assigned to or associated with an exported project, it will not be included in the P6 XML or XER file. You cannot use the import method to transfer entire P6 dictionaries such as resources, roles, risk matrices, and risk thresholds.
Note: XER refers to Oracle Primavera Proprietary Exchange Format (XER). It is a proprietary file format used by the P6 EPPM application.
The sections below list the P6 data objects that are importable or nonimportable by the P6 XML and XER import functionality in Primavera Cloud.
Importable Data
Importable data is separated into Workspace-level Data and Project-level Data lists, which identify where each object is stored in Primavera Cloud. Workspace-level data that is assigned to an exported 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. In general, importable workspace-level data consists of P6 Enterprise Data such as calendars, codes, and UDFs, which can be assigned to child workspaces and projects within a workspace. Importable project-level data contains project-specific objects such as activities, resource assignments, risks, and the WBS. When an object is imported, its associated data is also included. For example, each activity that is imported includes its dates, durations, units, costs, types, code values, configured field values, and resource assignments.
The names and storage locations of data objects in Primavera Cloud may be different than in P6. For example, user defined fields (UDFs) in P6 are called "configured fields" in Primavera Cloud. P6 Enterprise Data like Project activity codes types and project calendars are imported and stored at the project level. These types of differences are included below.
You can set individual import actions for each project in the XML or XER file and most of the data objects listed below. Not all of the items below are listed in the application's import tool. Unless otherwise stated, subordinate items that are not listed in the application take the import action of their parent.
Importable Workspace-level Data
Object | Type | Notes |
|---|---|---|
Calendars | Global Calendars Resource Calendars |
|
Codes (and Code Values) | Activity Project Resource | Codes marked as Secure in P6 are importable, but there is no such designation in Primavera Cloud. EPS and Global activity codes are imported to the workspace level. Project activity codes are imported to the project level. The import action for codes does not only apply to the workspace in which the projects are imported. Using the Update Existing import action on codes has the potential to update existing defined values as high as the root workspace. In P6, codes are exclusive to their respective object types. In Primavera Cloud, a code can be applied across multipleobject types. |
Configured Fields (called "user defined fields" (UDFs) in P6) | Activity Configured Fields Assignment Configured Fields Project Configured Fields Risk Configured Fields WBS Configured Fields | You can only import Project configured fields with a Type of Manual. Imported configured field names must begin with a letter. Names cannot contain spaces, reserved words, multi-byte characters, or special characters except for an underscore. |
Curves (called "Resource Curves" in P6) |
|
|
Resources and Roles | Resource and Role Availability Resource and Role Rates Resource Code Assignments Resource/Role Associations | 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. Each resource or role's parent hierarchy is also imported and stored in the project's parent workspace so that their hierarchical structure is maintained. Roles in Primavera Cloud must have unique IDs. To successfully import roles into Primavera Cloud, ensure that the role IDs being imported from P6 are all unique.
|
Risk Threshold and Matrix Templates | Risk Threshold Levels Risk Thresholds Risk Matrix Risk Matrix Scores Risk Matrix Thresholds | The cost threshold, schedule threshold, and probability threshold associated with a risk matrix template must be included in the XML import in order for the risk matrix template to import successfully. P6 Professional does not support risk matrix, so risk threshold and matrix templates are not imported with an XER file import. |
Units of Measure |
|
|
Importable Project-level Data
Object | Type | Notes |
|---|---|---|
Activities | Activity Details Calendar Assignments Code Assignments Configured Field Assignments Notebook Topics WBS Summary Activities | EPS and Global activity codes are imported to the workspace level. Project activity codes are imported to the project level. |
Project | Baselines Scenarios Code Assignments Configured Field Assignments Project Default Calendar Assignment Project Settings Scheduler Settings
| Baselines and scenarios are selected when setting import actions for the projects in the XML file. You can import up to three baselines or scenarios per project. You can also choose to import only baselines or scenarios and no other project data for existing projects in the application, or you can choose to import only baselines or scenarios as new projects. Baseline types (baseline categories in Primavera Cloud) are also imported as part of baseline data if assigned to baselines and selected for import. Baselines are excluded while importing a P6 XER file as the XER format does not support baselines or baseline types. Baselines and baseline types can only be imported with the P6 XML import. Project code and configured field assignments follow the import actions for project codes and project fields in Workspace-level Data. Project settings, scheduler settings, and a project's default calendar assignment are automatically included with each imported project. If the calendar in the XML file is not found in Primavera Cloud and is not added to Primavera Cloud as part of the import process, the workspace default calendar will be set as the project default calendar.
|
Project Calendars |
|
|
Relationships |
|
|
Resources and Roles | Activity Assignments Assignment Calendars Assignment Configured Field Assignments Assignment Costs and Units Assignment Rates | Primavera Cloud lists "Resources and Roles" as an importable item at the project level. This item 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. Each resource or role's parent hierarchy is also imported and stored in the project's parent workspace so that their hierarchical structure is maintained. If you frequently export and import data, either to Primavera Cloud or P6 EPPM, a resource or role's availability and rate values should be identical at the workspace and project levels. Resource and role values are imported at the workspace level only. If a project-level resource or role is created as part of the import, it will use the values that exist at the workspace level. Existing project-level availability and rate values will not be overwritten. If you want to update project-level availability and rate values, you should do so manually. Before importing an XER file into Primavera Cloud, ensure the decimal symbol setting for currency values in P6 is set to dot(.) instead of comma(,). If the base currency of an XER file differs from Primavera Cloud's base currency during import, then Primavera Cloud will convert the currency type while preserving the same relative value. For example, 100€ in P6 will be displayed as $100 in Primavera Cloud. You can view the currency differences in the Import Log on the Manage Services page. |
Risks | Activity Assignments Configured Field Assignments Probabilities and Impacts Matrix Scores Response Actions Response Action Impacts Response Plans Risk Matrix and Thresholds Project Assignment | Primavera Cloud supports a single response plan for each risk. Only response actions under an active response plan will be included in the XML or XER file. The lowest response action impact values under each active response plan will be imported and stored as post-response values at the risk level. |
Work Breakdown Structures (WBS) | Configured Field Assignments |
|
Nonimportable Data
The data that cannot be imported into Primavera Cloud is divided into two categories:
- Nonimportable but supported in Primavera Cloud: This is the data that cannot be imported into Primavera Cloud but the functionality is supported.
- Nonimportable and not supported in Primavera Cloud: This is the data that cannot be imported into Primavera Cloud and the functionality is also not supported.
Nonimportable Data Supported in Primavera Cloud
The P6 data listed below cannot be imported into Primavera Cloud, 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.
Object | Type | Notes |
|---|---|---|
Application Settings |
|
|
Budget Approval Details |
|
|
Budget Approvals |
|
|
Budget Change Details |
|
|
Budget Changes |
|
|
Budget Transfer Details |
|
|
Budget Transfers |
|
|
Cost Breakdown Structure (CBS) |
|
|
Currencies |
|
|
Dashboards |
|
|
Discussions |
|
|
Documents |
|
|
Filters |
|
|
Financial Periods |
|
|
Funding Sources |
|
|
Layouts (unique to P6 Pro) |
| Views in Primavera Cloud provide much of the same functionality as layouts, although they are not functionally equivale
|
Discussions |
|
|
Documents |
|
|
Filters |
|
|
Financial Periods |
|
|
Funding Sources |
|
|
Layouts (unique to P6 Pro) |
| Views in Primavera Cloud provide much of the same functionality as layouts, although they are not functionally equivale
|
Locations |
| Locations can be added manually or transferred to Primavera Cloud using an integration method.
|
Owner |
| The Owner field exists in Primavera Cloud, but ownership of imported objects is automatically assigned to the user who imported the objects. |
Portfolios |
|
|
Primary Role Designation |
|
|
Project Budget Change Logs |
|
|
Project Funding |
|
|
Project Resource Allocations |
|
|
Reports |
|
|
Resource and Role Rate Types |
|
|
Scheduled Services |
| You can manually run Import, Export, Level, and Schedule jobs in Primavera Cloud.
|
Stored Images |
| Primavera Cloud enables users to upload photos and associate them with workspaces, projects, and other objects. |
Tasks |
| Tasks can only be transferred from Primavera Cloud to P6.
|
Timesheet Data |
|
|
Timesheet Periods |
|
|
User Interface Views |
|
|
User Preferences |
|
|
Users |
|
|
Views |
|
|
WBS Spreads |
| WBS spread data can be added manually or transferred to Primavera Cloud using an integration method. |
Nonimportable Data Not Supported in Primavera Cloud
The P6 functionality and data listed below cannot be imported, and there is no functional alternative supported by Primavera Cloud.
Object | Type | Notes |
|---|---|---|
CBS Duration Summaries |
|
|
CBS Expense Spreads |
|
|
CBS Resource Spreads |
|
|
Cost Accounts |
|
|
Data Limits |
|
|
Document Categories |
|
|
Document Status |
|
|
Enterprise Project Structure (EPS) |
|
|
Expense Categories |
|
|
Expenses |
|
|
External Applications |
|
|
Global Security Profiles |
|
|
Issues |
|
|
Organizational Breakdown Structure (OBS) |
|
|
Overhead Codes |
|
|
Performance Thresholds |
|
|
Project Planning Resources |
|
|
Project Security Profiles |
|
|
Project Spending Plans |
|
|
Publication Services |
|
|
Reflections |
|
|
Resource and Role Teams |
|
|
Resource Notes |
|
|
Resource Shifts |
|
|
Risk Categories |
|
|
Step Templates |
|
|
Steps |
|
|
Summarization |
|
|
Thresholds (unique to P6 Pro) |
|
|
Tracking layouts |
|
|
UDF (Configured Field) Types | Documents Expenses Issues Resources Steps Project UDFs with a UDF Type of Formula UDFs with a Data Type of Indicator |
|
Visualizer |
|
|
WBS Categories |
|
|
WBS Expense Spreads |
|
|
WBS Milestones |
|
|
WBS Resource Spreads |
|
|
Object Matching
During the import, Primavera Cloud checks each imported object to see if it shares an ID with any related objects already present in the database. The following fields are used to identify matches, per object:
Object | Fields used to determine match |
|---|---|
Activity | Activity ID |
Calendar | Calendar ID |
Code | Code ID |
Curve | Curve Name |
Relationship (single-project) | Predecessor Activity ID, Successor Activity ID, Relationship Type |
Relationship (multi-project) | Predecessor Project ID, Predecessor Activity ID, Successor Project ID, Successor Activity ID, Relationship Type |
Resource Assignment | Activity ID, Assignment ID, Resource ID, Role ID |
Risk | Risk ID |
Risk Matrix | Risk Matrix Name |
Risk Threshold | Risk Threshold Name, Risk Threshold Type |
Resource | Resource ID |
Role | Role ID |
UDFs (matched to Configured Fields) | Column Label, Data Type |
WBS | WBS Code |
Last Published Tuesday, May 21, 2024