P6 and Microsoft Project
Project Desktop vs Project Online vs Project for the Web
Desktop MPP vs Project Online vs Project for the web
Do not invent cloud field parity. Microsoft does not claim the three products share one field set.
Desktop (Project Standard / Professional / Project Online Desktop Client)
- Native file: MPP. Also opens/saves MSPDI XML for interchange.
- This is the engine MSPDI is written for.
- Project Online Desktop Client is the subscription desktop app; it can connect to Project Online. It still uses MPP locally.
Project Online (PPM / Project Server in Microsoft 365)
- Enterprise PPM service. Desktop client publishes to it.
- Not the same product as Project for the web.
- Do not assume every desktop field is stored or recalculated identically on the server. Microsoft does not publish a field-parity table we can cite here. Unverified: cloud vs desktop calculation of any given field.
Project for the web
- Separate, simpler web tool. Not a complete replacement for desktop (Microsoft).
- Can import an MPP from Project 2016+ into a new web project. The MPP is not altered.
- Microsoft: some desktop features do not migrate. Evaluate before import. Limits are lower than desktop.
- Community/import notes (not a full Microsoft field list): dependencies (FS called out), some constraints (ASAP and finish-no-earlier-than mentioned), up to 10 local custom fields. Treat that list as incomplete.
Files each uses
| Product | Native | Interchange |
|---|---|---|
| Desktop | MPP | MSPDI XML, Excel field export |
| Project Online | Server store + desktop MPP | via desktop / Project Server APIs (not documented here) |
| Project for the web | Its own store | Import MPP; not an MSPDI authoring surface |
We generate MSPDI for desktop Project, not for Project for the web.