Project planning and proper project management are fundamental aspects in any organisation. Two of the most popular tools for project planning are Primavera P6 and Microsoft Project. Sometimes it may be necessary to convert a schedule created in Primavera P6 to MS Project because of specific project requirements or the preference of certain work teams.
File formats
To convert a schedule from Primavera P6 to MS Project, it is essential to understand the compatible file formats that make this data transfer possible.
Primavera P6 formats
- XER: This is the native Primavera P6 format. It is a text file that contains project data and is used to export and import projects within Primavera P6.
- XML: Primavera P6 can also export files in XML format, which is a more universal format and can be used to exchange data with other systems.
MS Project formats
- MPP: This is the native MS Project format. It is a proprietary Microsoft format that contains all project data.
- XML: MS Project also supports XML files, allowing project data to be imported and exported.
Conversion options
Direct conversion using XML
The simplest way to convert primavera p6 to ms project in 5 steps a Primavera P6 project to MS Project is to use the XML format, because both programmes support it.
Using third-party tools
There are several third-party tools that make conversion between Primavera P6 and MS Project easier.
Manual conversion
In some cases, a manual conversion may be required, especially if the projects are very complex or if the automatic formats do not preserve all the characteristics of the original project. This process involves exporting the project from Primavera P6 to Excel and then importing the Excel file into MS Project, mapping the corresponding data fields to ensure that the project structure remains intact.
Additional considerations
Initial review in P6
- One of the main errors caused by exporting the schedule to MSP is constraint dates. We should avoid using the Mandatory start and As late as possible constraints. If a constraint is necessary, it should be replaced with Start on.
- In the Schedule menu, we must ensure that the calendar used to calculate relationship delays between activities is the successor activity calendar.
- Microsoft Project calculates the durations of completed activities differently. To avoid duration mismatches when exporting the schedule, we must create a global change so that when Remaining Labor Units are equal to zero, Remaining Units / Time are set to zero.
Subsequent review in MSP
- Data verification: After conversion, it is essential to review and verify that all data has been transferred correctly. This includes task durations, dependencies, assigned resources and start and finish dates.
- Calendar consistency: It is necessary to ensure that working calendars and working-hour settings are consistent between both systems in order to avoid discrepancies.
- Field customisation: Some Primavera P6 custom fields may not be transferred automatically to MS Project. These fields may need to be recreated manually in MS Project.
