Exporting to Primavera P6
To access the export tools, click on the vPlanner icon to open the backstage and click on the Export section. The default is that the content of the Manage view will be visible as a preview. Click on the Filter Tasks item on the side menu to switch to the List View. The list will show the tasks that are visible in the manage view.
You can switch to see the tasks in the entire plan, and you can use the filters in the Task List side to narrow down what will be exported.
The supported export format icons at the bottom of the screen will become active when you switch to the List View. Select the P6 Excel Sheet item to open the guided wizard.
Similar to V4, vPlanner will allow you to pick an optional P6 template mapping file, which is an excel sheet that you create from the P6 project you plan to import into. vPlanner will use the template information to map vPlanner attributes to matching P6 columns. If you do not have a template file, you can still do the mapping manually in Excel by changing the column headers (experienced P6 users will find this format familiar as it is a standard way of getting data into a P6 project).

The next screen provides options to control what will be exported to P6.
The timezone and date format options will control how the date information will be converted and formatted. vPlanner dates are stored in Universal Time, so pick the appropriate setting for how your P6 project is configured.
The P6 Project ID is used by vPlanner during the export to prefix the WBS code so that P6 imports those activities under the proper section of the WBS. If you do not specify a value or if you activities do not have a WBS code, vPlanner will insert text in the WBS column to alert you that you should fix those values manually before importing into P6.
Other Settings:
Use External ID when Possible: vPlanner tasks have two IDs an integer which is the default task id and an External-ID. If your project in vPlanner contains tasks that are previously imported from P6, their External-ID will be the P6 Activity ID. During the export, vPlanner will swap the vPlanner ID and replace it with the External ID so that P6 can update those tasks when they are imported to P6.
Skip Finish-to-Start Logic Ties between Original Imported Tasks: when this option is enabled and the export contains unmodified imported tasks, then the logic between those tasks will be skipped during the import. Leaving this option enabled, will maintain your lags that are defined on those activities in P6. If you have converted those tasks to vPlanner native tasks or created native tasks in vPlanner the logic between those tasks will export as Finish-to-Start logic without lags. Note that imported FF, SS, or SF logic imported from P6 will never export back to P6.
Impose P6 Task Dependent Constraints: When this option is enabled, the vPlanner LF date will convert to a P6 "Finish on or before" constraint and the vPlanner FS date will export to a P6 "Start on or after" constraint. This will force P6 to use the vPlanner FS and LF dates as constraints. If the task has no LF date, then the FS constraint will apply.
Create P6 Milestones from vPlanner Milestones: When this option is enabled, a vPlanner Start Date will convert as a "Start On" constraint and the vPlanner Planning Marker and Milestone tasks will convert to Finish On constraints in P6 if they have zero durations. You will still need to convert those to P6 Start Milestone and Finish Milestone types in P6 manually as for whatever reason, P6 will not properly read those types from the Excel file.