Exporting to P6 via XLSX

 
You can export tasks and logic from vPlanner to Primavera P6 using the Primavera XLSX template files.  The export requires the creation of certain additional settings in P6 for the desired vPlanner attributes. 
 
vPlanner information can be exported to either Activity Code or User Defined Fields in P6.  We recommend setting up P6 as follows:
 
If you had use the Activity Codes defined in the import section, you can extend those by using User Defined fields to host the rest of the vPlanner data.  The following naming convention for P6 User Defined fields is recommended if you want to take advantage of the provided automated mapping process:
 
vPlanner Attribute
P6 User Defined Name
P6 Data Type
Comments
Calendar
vp_calendar
Text
Transfer the calendar name into P6 User defined field (can apply global changes to match to P6 calendars
Category
vp_category
Text
 
Constraint Type
vp_constraint_type
Text
 
Forecast Start (FS)
vp_forecast_start
Start Date
 
Forecast Finish (FF)
vp_forecast_finish
Finish Date
 
Lrm Start (LS)
vp_lrm_start
Start Date
 
Lrm Finish (LF)
vp_lrm_finish
Finish Date
 
Guid
vp_task_guid
Text
The internal Guid of the vPlanner task.
Resources
vp_resources
Integer
 
Task Type
vp_task_type
Text
 
Required Start (RS)
vp_required_start
Start Date
 
Required Finish (RF)
vp_required_finish
Finish Date
 
Username
vp_username
Text
 
Floor
vp_floor
Text
 
Building
vp_component
Text
 
Zone
vp_zone
Text
 
Department
vp_department
Text
 
Team
vp_team
Text
 
Phase
vp_phase
Text
You can use Activity Codes for Phase if you wish to set a standard.
Company
vp_company
Text
You can use Activity Codes for Company if you wish to set a standard.
Elevation
vp_elevation
Text
 
 
 
 
 
 
 
 
 
 
 
Task names, durations, start dates, task status, actual start, actual finish dates and logic will automatically map to the appropriate P6 fields. 
 
This section provides an overview of the necessary steps to configure P6 and how to properly apply the mapping to produce consistent results.