LESSON 1-2: Importing Projects from P6 to Primavera Cloud
This lesson describes how to:
[MUSIC PLAYING]
1. XML and XER import format.
Primavera Cloud offers a simple interface to import projects from P6 and P6 Professional, enabling you to take full advantage of the enhanced features in Primavera Cloud to manage your projects. Two file formats for import are available. P6 uses XML. P6 Professional uses XER or XML. Note that XER does not include baseline data.
2. Import From P6.
Before importing project data, choose which workspace the data will be imported into. On the Projects page, select a workspace. Click Actions, and select Import From P6. Select a file. Note that the file may contain multiple projects which are displayed in the table. For each project, click in the Import Action column to choose from four options.
3. Project Import Actions.
For Create New Project, the import will create a new project in Primavera Cloud in the selected workspace. If the project already exists, a numeric value will be appended to the project ID. The Update Existing Project option only appears if a matching project ID is found. The import will update the existing project data. Use this option if you are using the import to update the status of the project in Primavera Cloud. Do Not Import will ignore the project. For XML files, there is an additional option to update baselines only. Other project data will be ignored.
4. Action to take when matching data is found.
The next step is to choose which action to take when matching data is found, for example if the imported project contains activity codes that already exist in the workspace. These options are listed in the Import Action column. Insert New will create a new activity code and append a numeric value to the ID. Update Existing will update the activity code in the owning workspace with the data from the Import file, and it will assign or promote the activity code to the selected workspace if it does not exist. Keep Existing will not update the activity code data from the Import file, and it will assign or promote the activity code to the selected workspace if it does not exist. Do Not Import will ignore the activity code data in the Import file.
5. Update Existing or Keep Existing workspace data.
When choosing to update existing or keep existing workspace data, the application may attempt to promote data from lower workspaces to a common parent workspace. This may trigger conflicts if multiple matches are found. For example, two lower workspaces may have the same activity code. When attempting to promote the activity code to a common parent workspace, the conflict arises as the application doesn't know which activity code to promote.
6. Resolve conflict during import.
If a conflict should arise, select how the import should resolve it. These options are located in the Conflict Action column. Insert New will create a new activity code and append a numeric value to the ID. Fail Import, the import will stop and no data will be imported. Do Not Import will ignore the matching activity codes and will not import the code.
7. Handle matching project data.
For project data, when matching data is found in both the P6 project and the Primavera Cloud project, select how the import is handled. For example, if matching activities are found, Update Existing will update the project activities based on the information in the Import file. Keep Existing will not change any activity data currently in the Primavera Cloud project. Do Not Import will ignore the matching activity in the Import file.
8. Remove activity, relationship, and resources, and roles from project.
An additional column, Remove From Projects, is listed just for activity, relationship, and resources, and roles. Use this option to delete the object from the Primavera Cloud project if the object does not exist in the XML or XER file. This ensures the project being updated in Primavera Cloud is consistent with the data in the XML or XER file. Select Save Configuration to use these settings again for future imports. After the import completes, review the import log to view data and statistics about the process, as well as any errors encountered that need to be resolved.
[MUSIC PLAYING]
