How To Import P3 Projects Into P6 Professional
A common question we’ve had from our P3 / P6 user community
How to Import P3 Projects into P6 Professional?
The option for Import P3 is greyed out in the Import screen in P6 Professional.
How can P3 Projects be Imported?
In 8.0 and later, you are unable to directly Import P3 Project files directly into P6 Professional. You must first convert the P3 file into an XER file and then you must Import the XER file into P6 Professional.
Note: This requires P3 to be installed or Btrieve files for the utility to work.
To Import a P3 file into P6 Professional, do the following:
- Navigate to the Converter folder at the P6 Professional installation home. The default location is C:\Program Files\Oracle\Primavera P6\P6 Professional\Converter.
- Run P330XERConvert.exe.
- On the Project Conversion screen, select P3 3.x and then click Next.
- On the P3 3.x Project Name screen, click Browse to select the P3 file that you want to convert and then click
- On the P3 3.x SubProject Name(s) screen, select the subprojects that you want to convert and then click Next.
- On the XER File Name screen, complete the following:
- Click Browse.
- Enter a name and location for the XER file.
- Click Next.
- On the Cost Calculation screen, determine if you want the conversion to calculate Costs from Unit Prices and Resource Quantities and then click Next.
- Click Finish.
- Log in to P6 Professional and Import the XER file.
To Import an XER file into P6 Professional, do the following:
- Choose File, Import.
- Choose Primavera PM (XER). Click Next.
- Choose Project.
- Select the file you want to Import.
- Double click the Import Action field to select how the Project data is Imported, then specify where to Import the Projects in the Import To field.
- Select Update Existing Project to add any new/modified data in the XER file to an existing project.
- Selected Create New Project to create a new project while the existing project’s data remains the same.
- Select Replace Existing Project to delete the existing project and replace is will the project imported from the XER file.
- Choose the data to Import by modifying the Layout Configuration in the Update Project Options dialog box (if necessary).
- In the Modify Import Configuration dialog box, select the data you want to modify. 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.)
- Select the Currency in which to Import Cost fields. (This dialog box only displays if the Import file does not specify a Currency, or if the Currency does not match a Currency defined in P6 Professional when P6 Professional is connected to a P6 Professional database and using P6 when connected to a P6 EPPM database.)
- Click Finish.
- Click Close.
- When you Import an XER Project file that contains Financial Periods, the Financial Periods in the XER file must exactly match the Financial Periods in the Financial Periods dictionary. If they do not match, no Past Period Actual data will be Imported.
- When selecting the Import action, you must select the Create New Project option if you want P6 Professional to Import Past Period Actual data. If you choose any other option, Past Period Actual Values are not Imported.
- For Projects containing WBS Summary Tasks, you should not choose to delete unreferenced data (Step 6 above). If you choose to delete unreferenced data, all WBS Summary Tasks will be deleted.
- 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.
- If you manually plan Future Period distribution for Resource/Role Assignments to Activities, be sure to select the appropriate Import action when Importing data; otherwise, Manual Future Period Assignment Values may be assigned. For example, if you are updating an existing Project with Imported data and you choose to Import Activity Resource Assignments, Future Period Assignment Values that exist in the Project you are Importing will overwrite Future Period Assignment Values in the Project you are updating. Therefore, if the Project you are Importing does not contain Manual Future Period Assignment Values and the Project you are updating does contain Manual Future Period Assignment Values, the Manual Future Period Values will be lost when the same Assignment exists in both Projects.
- 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 when 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 when 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.
- The following applies when you choose Keep Existing as the Resource Import action: Subsequent to the Import, there may be unassigned Personal Resource Calendars; these Calendars can be deleted.
- When connected to a P6 EPPM database: No Risk data is Imported when using XER format.
- When connected to a P6 EPPM database: The following applies only when you Import an XER to an R8.0 application (or earlier) from an R8.1 application: If more than one Issue has the same name and is assigned to different Activities within the same WBS, the Import occurs without error and the Issue names are kept the same. However, the rule applicable to version R8.0 and earlier that Issue names must be unique for Issues assigned to Activities within a WBS would subsequently apply. This means, for example, that you would not be allowed to change the name of one of the Issues and then change it back to its original name. Doing so would cause the application to issue a message that the Issue name must be unique.
Download this document here
Sorry, the comment form is closed at this time.