Import a project in XML format

1. Choose File, Import.
2. Choose Primavera P6 - (XML). Click Next.
3. Select the file you want to import. Clear the option "Import all project level layouts" if you do not need them to be included with the project. Click Next.
4. Click the Import Action field and use the drop-down menu to choose how the project data is imported.
   
   Select Update Existing Project to add any new or modified data in the XML file to an open project.
   
   Select Create New Project to create a new project without changing existing projects.
   
   Select Ignore this Project to not import the selected projects.
5. Double click the Import To field and specify where to import the project.
6. Double click the Baselines to Import field. In the Baselines to Import dialog box, mark the Import checkbox next to each baseline you want to import. Click OK, then click Next.
7. Choose the data to import by adding or editing a template in the Update Project Options dialog box (if necessary).
   
   In the Update Project Options dialog box, you can search for templates using the Search field. As you type, it will filter only those templates that match the text in this field.
8. Click Edit to launch the Import Options dialog box.
9. On the Basic tab of the Import Options dialog box, modify the selected option by choosing the action to take when the same data exists in the import file and the project being updated. If resource security is enabled, some restrictions apply when importing activity resource assignments.
   
   Select the action to perform during the import process. Mark the Delete checkbox to remove unreferenced data (i.e., data in the project you are updating but is not included in the import file) from the project. (The Delete field applies only to relationships to external projects, thresholds, activities, activity relationships, and activity resource assignments. Global data types are not affected by this setting.)
10. On the Advanced tab of the Import Options dialog box, modify global data, including codes, UDFs, calendars, and resources, as necessary.

    Note: This tab is disabled if multiple projects are being imported. However, if you select the "Ignore this Project" option for all projects but one, this tab is enabled.

11. Click Save to update the existing template or click Save As to create a new template with a unique name. Click Next.
12. Click Finish.
    

Notes

• When connected to a P6 EPPM database, if P6 Professional Applications are set to use remote mode, you can continue to work while your import process completes, unless you are importing a file which contains both projects and layouts.
• Unless you are working on a standalone system connecting to an SQLite database, you must use JRE 7 or higher to import XML files.
• When connected to a P6 EPPM database: If the Use Remote Mode for P6 Professional Update Baseline, Schedule Compare and XML Import option is selected and the Integration API Server URL is set, this process runs as a job service. To see the progress of the job, choose Tools, Job Status.
• When you import a project that contains relationships to external projects that do not exist in your database, the module will preserve the external activity dates when you schedule the project if you select the Ignore Relationships To and From Other Projects option in the Schedule Options dialog box.
• The following applies only when you choose Update Existing as the Resource import action: When you import a shared resource calendar and a personal resource calendar with the same name already exists in the database, the data from the shared calendar updates the personal resource calendar by the same name, but the personal resource calendar remains a personal resource calendar. Likewise, when you import a personal resource calendar and a shared resource calendar with the same name already exists in the database, the data from the personal resource calendar updates the shared resource calendar by the same name, but the shared resource calendar remains a shared resource calendar.
• Subsequent to the import, there may be unassigned personal resource calendars depending on the import action you selected for resources and calendars during the import operation; these calendars can be deleted.
• To import an XML file that contains updates to your personal resource calendar, you must have the Add/Edit/Delete Resource Calendars privilege. Otherwise any updates to your personal resource calendar are not imported.
• When connected to a P6 EPPM database: Risk data from P6 is imported when using XML format.
• When connected to a P6 Professional database: Risk data is imported when using XML format.
• You can import XML files without having access to all resources, but the following restrictions apply:
  • If the XML file contains resources that are in your hierarchy, these will be imported.
  • If the XML file contains new resources, these will be imported as long as the new resources are in your hierarchy.
  • You can choose to not import any new resources by choosing the “Do Not Import” option for Resources. Choosing the “Do Not Import” option for Resources causes the system to import the assignments of any existing resources in your hierarchy. In this case, any new resources in the XML file are ignored by the importer.
  • If the XML file contains resources that are not in your hierarchy, no items are imported. The system cancels the entire import process and issues an error.
  • If the XML file contains resources in your hierarchy that are in conflict with existing resources outside of your hierarchy in the database, no items are imported. The system cancels the entire import process and issues an error.

  When connected to a P6 EPPM database: For more information on defining access to resources, see the P6 EPPM Application Administration Guide.

  When connected to a P6 Professional database: For more information on defining access to resources, see the P6 Professional Installation and Configuration Guide.