MPP Compatibility Across Project Versions
MPP compatibility depends on the Project release that created a file and the release that opens and saves it. For the file’s purpose and contents, see What Is an MPP File?.
Versions that share a format
Section titled “Versions that share a format”Project 2010, Project 2013, and Project 2016 use the same file format, so files can be opened across those releases without first converting them.1
The risk of saving in an older release
Section titled “The risk of saving in an older release”Opening a newer file in an earlier Project release is not automatically a lossless conversion. Saving it from the earlier release can remove information that the older release does not understand, including:
- newer or custom fields;
- formulas that depend on newer fields; and
- newer project or resource calendar exceptions.
The file may open successfully while still losing data when saved. Check the guidance for the specific version pair rather than assuming a successful open means a lossless conversion.1 See supported file formats for distinctions between MPP and exchange formats.
Project Plan 365 is another tool for opening MPP files created with Project 2010, 2013, 2016, 2019, 2021, and 2024, and its saved MPP files are compatible with Project 2010 and later. Its compatibility guidance lists the supported versions. For an important handoff, try the file in the target application and keep the original as a backup.
A practical handoff checklist
Section titled “A practical handoff checklist”- Identify the release that created the MPP and the release that will save it.
- Keep an untouched copy of the original file.
- After saving from an older release, check custom fields, formulas, and calendar exceptions.
- If preserving the full plan is essential, avoid overwriting the original until the recipient confirms the result.
For a separate backup copy or file-password options, see Save and Protect Microsoft Project Files.