Convert Microsoft Project XML to an MPP File (Steps)
To convert XML to MPP, open the Project XML in Microsoft Project and Save As .mpp. No licence? Keep editing in Onplana Schedule, free. What to check after.
You have a Project XML file and someone wants an .mpp. The conversion is a save, not a converter: open the XML in Microsoft Project, choose File, Save As, and pick the Project (.mpp) format. Microsoft Project is the program that writes .mpp, so that is where the conversion happens.
The short answer. To convert XML to MPP, open the Microsoft Project XML (MSPDI) file in Microsoft Project and save it as a Project (.mpp) file. If you have no Project licence, open the XML in Onplana Schedule, which reads it on your machine, lets you edit it and saves it back as Project XML, but never writes .mpp. Everything in the XML, including dependency lag, calendars and baselines, travels into the .mpp; what is worth checking is the lag, the calendar and the status date.
Open the XML in Onplana Schedule, free Read and edit the plan without a Project licence: the Gantt, the critical path and float come up as soon as the file opens, and a Project XML file never leaves your machine. Open the XML in Onplana Schedule, free
How do you convert XML to MPP in Microsoft Project?
If you only need to read or edit the plan, opening an MPP file without Microsoft Project may be all you need.
The steps are the same on any current desktop version of Microsoft Project:
- Open Microsoft Project and choose File, Open.
- Set the file-type filter to XML Format (or All Project Files) and pick your file.
- Look at the plan before you save. Scroll the Gantt, check the start date and the first few dependencies.
- Choose File, Save As, pick Project (.mpp) as the type, and name the file.
- Close and reopen the .mpp to confirm it loads without a prompt.
The XML is the same schema Microsoft calls MSPDI, the Project Data Interchange format, so nothing is guessed on the way in. The MSPDI XML guide lists every element the file carries, and the decision to convert is rarely about data: it is about who has to open the result. An .mpp suits a colleague on Microsoft Project; the XML suits everyone else, because the schema is public and any tool can read it.
What does the XML carry that the MPP also carries?
The two formats describe the same plan. This table is the checklist for the file in front of you.
| What the plan holds | In the XML | In the .mpp | What to check after the save |
|---|---|---|---|
| Tasks, outline and WBS | Yes | Yes | The indent levels match the original |
| Dependencies (FS, SS, FF, SF) | Yes, one link per predecessor | Yes | The count of links, not just the tasks |
| Lag and lead | Yes, in tenths of a minute | Yes, shown in days or hours | A 2-day lead still reads as a lead |
| Constraints and deadlines | Yes, as numeric codes | Yes | No task is quietly "As soon as possible" |
| Calendars and exceptions | Yes | Yes | Holidays and shifts are on the right calendar |
| Baselines | Yes, numbered | Yes | Baseline 0 and any later baselines |
| Custom fields | Yes, as extended attributes | Yes | Names and types, not anonymous numbers |
Lag is the one that surprises people. Microsoft's LinkLag reference (read 2026-11-19) stores it in tenths of a minute, so a one-day lag on an 8-hour day is 4,800 in the file and "1d" on screen. A converted plan whose lags look wrong by a large factor usually means the unit was misread, so check lag first.
The diagram below shows the route, and the one point where it forks: with a Project licence the save writes the .mpp; without one, the XML stays XML.
What can you do without a Microsoft Project licence?
Keep working in Onplana Schedule, the free desktop app for Windows and Mac. It opens Project XML, shows the Gantt with the critical path and float, lets you edit tasks, links, lag and constraints with undo, and saves the result as Project XML that Microsoft Project opens. A file you opened is never overwritten: the save writes a new file beside it. It does not write the .mpp format, and you should not promise a colleague one from it. The MPP file page explains the binary format itself, and Onplana Schedule on iPhone and Android opens the same files on a phone.
What decides where your file goes is its contents, not its name. If the contents are Microsoft Project XML, the file is read on your machine and nothing is uploaded. Everything else, a binary .mpp and a Primavera P6 or Planner XML export alike, is converted on Onplana's servers, and the uploaded copy is deleted within 3 days and removed from backups 7 days after that. The app tells you which before anything leaves your computer.
What should you check after the conversion?
Three things catch nearly every bad conversion:
- Dependency lag. Pick three tasks with lag in the original and confirm the value and the unit.
- The calendar. Check the project calendar and any resource calendar still carry the holidays; a plan on the wrong calendar finishes on the wrong day.
- Baselines and the status date. Open Baseline 0 and compare a finish date, then confirm the status date did not reset.
For a file you did not build, run the free Schedule Health Check on it first: it reads the schedule and lists dangling tasks, missing links and constraint problems before you commit the file to a colleague. To go the other way, from .mpp to a spreadsheet or PDF, see converting an MPP file to Excel or PDF.
When is the XML the better format to send?
When the reader does not own Microsoft Project, the XML is the safer file. It is plain text, it is a documented schema, and Microsoft Project, Onplana and other tools open it, while an .mpp needs a converter anywhere outside Microsoft's own program. Send the .mpp only when the person on the other end has asked for one by name.
Open the XML in Onplana Schedule, free Check the plan, fix a link or a lag, and save it as Project XML that Microsoft Project reads. Windows and Mac, no account until you publish. Download Onplana Schedule for Windows or Mac
Microsoft Project™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.
Frequently asked questions
How do I convert an XML file to MPP?
Open the Project XML in Microsoft Project with File, Open, then choose File, Save As and pick the Project (.mpp) format. Microsoft Project is the tool that writes the .mpp format, so the conversion happens there.
Can I convert XML to MPP without Microsoft Project?
Not into a real .mpp file. Onplana Schedule opens the XML, lets you edit it and saves it back as Project XML that Microsoft Project reads, but it does not write the .mpp format.
Does converting XML to MPP lose any data?
The XML carries tasks, hierarchy, dependencies with lag, constraints, calendars, resources, baselines and custom fields, so a well-formed export converts without loss. Check the dependency lag, the calendars and the baselines after the save, because those are where a hand-edited or foreign export goes wrong.
Is my file uploaded when I open the XML in Onplana Schedule?
Not if the contents are Microsoft Project XML: the file is read on your machine and nothing is uploaded. A file whose contents are anything else, a Primavera P6 export saved as .xml for example, is converted on Onplana's servers and the uploaded copy is deleted within 3 days.
Why does my XML file from Primavera P6 not open as a Project plan?
A P6 export is XML in a different schema, not Microsoft Project XML. Microsoft Project does not read it directly; convert it through a tool that understands the P6 format first.
How do I convert MPP to XML?
In Microsoft Project, choose File, Save As and pick the XML format. In Onplana Schedule, open the .mpp and save: the app writes Project XML beside the original and never over it.
Ready to make the switch?
Start your free Onplana account and import your existing projects in minutes.