MS Project XML Importer & Fixer for Primavera P6
Import a Microsoft Project .xml file (MSPDI, the format P6’s “Microsoft Project XML” import reads) to view and repair it. This tool finds the known defects that make P6’s import fail or corrupt the schedule, shows you each one, and returns a fixed XML, an experimental XER you can open in the XER Viewer, and a PDF change report.
Findings (dry-run, nothing changed yet)
Done
- Import the fixed file into P6 and check the import log.
- Send a copy of the PDF report back to the contractor or client who owns the programme, asking them to confirm the changes are right.
FAQ
Is my file uploaded anywhere?
No, it’s parsed and fixed in your browser. There is no server to receive it.
Some P6 import failures aren’t in the file, what about those?
Correct, and being straight about this matters. Some failures are P6-side, not file-side: e.g. the P6 18.8-era XML importer failing when the Windows username contains a space (fixed in later patches, update to a current P6). And P6-vs-MSP mapping limits: deadlines, task types (fixed-work etc.), and levelling data don’t transfer. This tool repairs known file defects; a clean import still depends on your P6 version and settings, always trial-import and read the import log.
What’s the difference between the fixed XML and the XER?
The fixed XML is the safer output, minimal changes to the same MSPDI file. The XER is an experimental conversion for recipients who’d rather import a native XER than fight P6’s MSP-XML importer; verify it in the XER Viewer first.
MSPDI reference
Durations are PT8H0M0S-style; LinkLag is in tenths of a minute; LagFormat percent variants have no P6 equivalent; UID is the stable key, ID is display order.