This guide details how data is mapped between P6 EPPM and Microsoft Project MPX format. Throughout this guide, the term P6 EPPM includes P6 Professional. Any content that applies to only one of these applications is labeled accordingly.
All users who want to exchange data between various formats should use this document.
Notes:
- When WBS records are exported, the P6 EPPM field WBS Code (the PROJWBS.wbs_short_name column in the database) is exported to the WBS field in the MPX file and the P6 EPPM field WBS (the PROJWBS.wbs_name column in the database) is exported to the Task Name field in the MPX file.
- If the values in the budgeted or planned units field for an assignment were entered manually, they are not exported. For projects that have manually entered budgeted or planned unit values, you should choose a different file format if you want to preserve them in the export file.
If you choose the Replace Existing import action when you import an MPX file, if the P6 EPPM project has manually entered values in the budgeted or planned units field for an assignment, the manually entered values will be deleted and replaced with the data from the MPX file. - Calendars in P6 EPPM have settings for Work Hours Per Month and Work Hours Per Year. MPX Files do not contain equivalent fields. To calculate Work Hours per Month, P6 EPPM multiplies Work Hours Per Week by 4. Using the value derived from this calculation, to calculate Work Hours per Year, P6 EPPM multiplies Work Hours Per Month by 12.
Calendar hours per time period settings in MPX files are only imported into P6 EPPM if the Use assigned calendar to specify the number of work hours for each time period option is selected on the time periods page of application settings in P6 EPPM or the time periods page of admin preferences in P6 Professional .
Caution: Personal information (PI) may be at risk of exposure. Depending on local data protection laws organizations may be responsible for mitigating any risk of exposure.