When exporting, keep in mind that there are many differences between NetPoint and P6. Items like resources, calendars, codes, and constraints, for example, are all handled slightly differently. In addition, some characteristics are not maintained during round-trip import and export. For a full list of supported fields, see the notes at the end of this section.
Before exporting, if any activities or milestones have been scheduled on planned-dates, make sure to follow the instructions in [bookmark postid=”8705″ anchor=”exporting”]Preparing to Export from NetPoint (GPM)[/bookmark]. Once exported, the XER file must be imported into P6 to complete the process.
NOTE: Before attempting to update an existing project in P6, make sure to see the notes in bold in the supported fields table below.
*NOTE: Before attempting to update an existing project, see the notes in bold in the supported fields table below.
|P6 Project ID||The ID once exported to P6. NOTE: If you want to update an existing project in the P6 database, make sure you enter the same P6 Project ID. Before attempting to update, see the notes in bold in the supported fields table below.|
|XER Version||Controls what version of XER to export.|
|Calendars||Controls whether or not calendars will export as global. NOTE: NetPoint global calendars will only export if they have at least one assignment.|
|Project Codes||Controls whether or not codes will be exported. Any codes which allow more than one of their values to be assigned to the same activity will not transfer. To review, click Tools > Open Codes Manager and review their behavior. NOTE: If you want to update an existing project in the P6 database, checking this box will result in duplicate codes and values. For more info, see the notes in bold in the supported fields table below.|
|Project Resources||Controls whether or not resources will be exported and how. NOTE: If you want to update an existing project in the P6 database, checking this box will result in duplicate resources and assignments. For more info, see the notes in bold in the supported fields table below.|
|Working Hours/Day||Specifies the working hours for all calendars once in P6. NOTE: In a day-based schedule, NetPoint does not distinguish between which hours are working and which hours are not. These options allow you to configure how P6 will handle resources and other properties, before it’s even opened in P6.|
The following NetPoint objects and fields are brought into P6. If a field is not listed, then it does NOT transfer. Some examples of fields that do not transfer are identified where relevant.
|This field in NetPoint||Becomes this field in P6 ||Notes|
|Activity, Delay||Task Dependent|
|Milestones and benchmarks (both start and finish)||Start/Finish Milestone||Benchmarks in NetPoint become milestones with Mandatory Start or Mandatory Finish constraints in P6 accordingly.|
|Hammock||Level of Effort||Any unconnected milestones or benchmarks will be connected to the LOE with a start-to-start or finish-to-finish relationship accordingly.|
|Embed, link lag||Lag||If both exist in the same relationship, they will be combined. For example, an SS relationship with a link lag of 5 days and an embed lag of 5 days will transfer as an SS with 10 day lag in P6.|
|Info Object||Documents||Info objects that have been attached to activities, milestones, or benchmarks will be assigned to the appropriate object. Info objects drawn on the canvas will also be exported and associated with the exported project|
|Description||Activity Name||Any description over 120 characters will be truncated.|
|ID||Activity ID||If empty, IDs are created in P6 with prefix “~”.|
|Start Date||Start, Actual Start|
|Finish Date||Finish, Actual Finish|
|Duration||Original Duration, Actual Duration|
|Remaining Duration||Remaining Duration|
|No-earlier-than Constraint||Start On Or After (for activities and start milestones), Finish On Or After (for finish milestones)|
|No-later-than Constraint||Finish On Or Before (activities and finish milestones), Start On Or Before (start milestones)|
|Total Float||Total Float|
|Grid Position||—||This field is exported for round-trip purposes only and isn’t used in P6.|
|Color||—||This field is exported for round-trip purposes only and isn’t used in P6.|
|Shape (milestones/benchmarks)||—||This field is exported for round-trip purposes only and isn’t used in P6.|
|Text Formatting||—||This field is exported for round-trip purposes only and isn’t used in P6. Includes font, color, alignment, style, size, and line breaks.|
|Text Display||—||This field is exported for round-trip purposes only and isn’t used in P6. Includes whether text fields, date fields, float fields, etc. are turned on or off.|
|Calendars||Calendars||If Create Calendars as Global is checked but a calendar created in P6 with the same name already exists in the global record, it will NOT be overwritten or replaced. Instead, another calendar will be created with its own properties and assigned to the corresponding activities. The latest one will always show up last behind any other identically named calendars. NetPoint global calendars will only export if they have at least one assignment. Recurring holidays (“fixed-date” holidays in NetPoint with a repeat factor of 1 year) will transfer individually, with each case being a separate holiday. NOTE: If you plan on importing back into NetPoint, avoid using the default “United States” or “Calendar Days” calendars. After a round trip (NetPoint -> P6 -> NetPoint), a new set of default calendars are created, resulting in duplicates.|
|Codes||Codes||Codes in NetPoint transfer as activity codes in P6. NetPoint cannot export codes as global, meaning all codes will end up at the project level. NOTE: If the schedule was exported from P6 already, and some of your codes were global, either create a new project instead of updating the existing one OR don’t export them at all. Otherwise, you will have duplicate assignments.|
|Name||Activity Code Name||The “Code Value” field in P6 will be filled in with a unique ID generated by NetPoint.|
|Value||Description||In NetPoint, multiple values per code may be assigned to the same activity. In P6, however, only one value per code may be assigned to the same activity. Project codes are not exported if they are set to have multiple values in NetPoint (even if only one value is actually defined for the code or assigned to an activity).|
|Resources||Resources||Limits, Histogram Pattern, Color, and Color Intensity are not exported at this time. NOTE: If the schedule was exported from P6 already, and some of your resources were assigned at the global level in P6 and others at the project level in P6, either create a new project instead of updating the existing one OR don’t export them at all. Otherwise, you will have duplicate resources and assignments. In addition, the primary resource setting is not maintained, which will need to be reset manually after the round trip.|
|Name||Resource ID, Resource Name||The “Resource ID” field is filled in with the name of the resource as well.|
|Cost/Unit||Price/Unit||P6 stores the cost per hour. For example, $1 dollar per day will be transferred to P6 as $0.125/hour.|
|Category||Resource Type||Any category other than material, equipment, and labor is converted to material, equipment, or labor.|
|Rate/Dur, Rate/Day||Budgeted Units & Remaining Units||In NetPoint, an activity may have some resources assigned to it “per day” and other resources assigned to it “per duration”. This is called a mixed assignment. In P6, the resource assignments for a given activity must be all of the same type. If an activity has its resources exported per day, that activity will have its duration type set as “fixed units/day” in P6. If an activity has its resources exported per duration, that activity will have its duration type set as “fixed units” in P6. For more on distribution types, see [bookmark postid=”8356″ anchor=”assignment-options”]Assignment Options[/bookmark]. If the activity is in progress or actualized, resource data will also be mapped to the “Actual Units”.|