Microsoft Project Online shuts down September 30, 2026. Organizations still running portfolios on the SaaS platform must choose a replacement or risk losing access to schedules, baselines, and resource data. ProjectLibre is positioning itself as a direct replacement, promising to open existing .mpp files and preserve critical path, dependencies, and resource assignments without rebuilding from scratch. The deadline is real, but the migration path is more straightforward than many assume.
Key facts
- Microsoft Project Online retires on September 30, 2026
- ProjectLibre opens .mpp, .xer, and .mpx files directly
- Reports 8.7M+ users across 193 countries and 54 languages
- Cloud features include resource leveling, Monte Carlo risk analysis, project audits, real-time collaboration, and an AI co-pilot
- Portfolio management, role-based access, and shared resource pools available
- Migration paths target teams moving from MS Project, Project Online, or Primavera P6
Who should care
PMOs and program managers** running formal schedules with CPM, baselines, and earned value data need a tool that preserves scheduling discipline. A broken baseline or recalculated critical path means rework for finance partners and steering committees.
Engineering and construction teams** managing complex portfolios with hard dependencies are the hardest hit. These groups cannot afford a tool that requires rebuilding task hierarchies from spreadsheets.
IT and finance leaders** who share resource pools across business units or depend on earned value metrics will feel the downstream effects if the new platform handles cost management differently.
Hybrid delivery leads** running Scrum alongside formal release plans still need reliable scheduling for capacity modeling and stakeholder reporting, even if their day-to-day work lives in agile tools.
Agile-only teams using purely Scrum or Kanban workflows have the least exposure, but they should confirm whether any of their reporting dependencies pull from formal project schedules.
What the platform offers
ProjectLibre's core pitch is file compatibility. Teams can open .mpp, .xer, and .mpx files directly, preserving tasks, dependencies, resources, baselines, and critical path math. According to its feature list, the platform includes resource leveling, Monte Carlo risk analysis, project audits aligned with DCMA standards, real-time collaboration, and an AI co-pilot built on a real CPM scheduling engine rather than a lightweight task board.
The practical implication: a program manager sitting on hundreds of legacy files can test the cutover without converting anything manually. That removes the most common barrier to switching.
What to watch before you commit
File compatibility alone does not guarantee a clean migration. Run a structured pilot with these three checks:
- Critical path integrity.** Load a representative project and confirm the calculated critical path matches your current output exactly. Any drift signals a CPM engine difference that will compound across large portfolios.
- Baseline behavior.** Check whether your baseline bars, variance calculations, and earned value metrics hold their shape. Finance partners tracking SPI and CPI depend on this data remaining consistent.
- Resource leveling logic.** Test how the tool resolves over-allocated resources. The default algorithms vary between platforms and can reshape your schedule unexpectedly.
If all three checks pass, you have a credible migration story for your steering committee. If any fail, you have time to negotiate requirements with the vendor or evaluate alternatives.
Our analysis
The September 2026 deadline creates a forced migration window that favors vendors offering a genuine lift-and-shift path over those requiring re-platforming work. For organizations with large .mpp libraries, the file-compatibility claim is the only thing that matters right now. Everything else is secondary.
The trade-off is familiar: open file formats and scheduling parity versus integration with the broader Microsoft 365 stack. Teams deeply embedded in Teams, Power Automate, or SharePoint will feel the friction of moving outside that ecosystem. Those running scheduling-agnostic stacks have more freedom to choose based on capability rather than ecosystem lock-in.
What to watch next: whether any major PMO publishes a reference architecture for the cutover, how ProjectLibre's AI co-pilot handles schedule evolution on real CPM projects, and whether Microsoft signals any bridge support before the deadline closes.
Key takeaways
- Treat September 30, 2026 as a firm planning deadline, not a soft suggestion
- Run a pilot with real project files before committing to a replacement platform
- Verify that baselines, critical path, and resource leveling survive the migration intact
- Balance file-format portability against integration with your wider delivery stack
Frequently asked questions
When is Microsoft Project Online being retired?
Microsoft Project Online is scheduled to retire on September 30, 2026.
Can teams keep their existing .mpp files when they migrate?
ProjectLibre says users can open existing .mpp, .xer, and .mpx files directly and preserve tasks, dependencies, resources, and schedules without rebuilding from scratch.
Who is most affected by the retirement?
PMOs, engineering groups, and portfolios that rely on Project Online for CPM scheduling, baselines, and resource management will feel the change first.
Does this affect agile teams using Scrum or Kanban?
Agile-only teams are less exposed, but hybrid programs that mix agile delivery with formal schedules still depend on these scheduling tools for release planning and capacity modeling.
What should a PMO do first?
Inventory existing files, identify the projects that rely on critical path and baselines, and run a small pilot migration before committing to a platform-wide switch.