Preparing to Import
The following items are actions or considerations you should take prior to import to prepare your Primavera Cloud environment.
- Establish Workspace Hierarchy: Ensure that your Primavera Cloud workspace hierarchy has been established. If your P6 EPS/OBS hierarchies were effective, you may choose to recreate that setup. To get started, see "Workspaces Overview" in the Oracle Primavera Cloud Help.
- Confirm Security Permissions: In order to perform a Primavera Cloud P6 XML or XER import, users are required to have either the Application Administrator privilege or all of the following privileges:
- Workspace permissions: Enable Import Project, Add Projects.
- Project permissions: Edit Project.
The Import Project privilege temporarily overrides individual shared data privileges during the import process, enabling users to create the shared data required by the imported projects.
- Create Configured Fields: Called "user defined fields" in P6, configured fields contain data specific to your organization.
- External Project Relationships: All projects selected during import are imported into the same workspace. To ensure that external relationships (also called "inter-project" or "cross-project" relationships) are maintained during import, Oracle recommends that you import all desired projects at the same time. After they have been imported into Primavera Cloud, projects can be moved to their appropriate workspaces.
- Predefined Configuration Elements: When a new Primavera Cloud instance is established, it is prepopulated with a selection of configuration elements to expedite the setup of the application. This includes prepopulated dictionary items like calendars, codes, and roles. It is recommended that you familiarize yourself with these elements prior to import to ensure there will be no potential conflicts between the existing configuration objects and any objects that will be imported. Most preexisting configuration elements are located in the root, Production, and Non-Production workspaces.
- Check the P6 XML File Size: The maximum file size that you can import is 1 GB. If the P6 XML or XER file exceeds this size, the original export may need to be broken down into multiple smaller files.
- Recommended Settings: There is no single set of recommendations that is appropriate for every possible import situation. Each user's environment contains many variables that can affect the outcome of the import process, including the number and size of P6 databases from which the P6 XML or XER data is sourced, the number of P6 instances the user has, the number of matches between P6 data and existing Primavera Cloud data, and whether all P6 projects are imported together or separately. While each scenario is different, the Update Existing import action generally provides the best overall results.
Last Published Monday, September 14, 2026