Microsoft has set a firm retirement date for Project Online: September 30, 2026. After that date, the service will no longer be accessible, and all associated data will be deleted. The company will also stop selling Project Online-only plans to new commercial customers on October 1, 2025, effectively closing the door for new adopters a full year before the final shutdown. For the thousands of enterprises that rely on Project Online for portfolio and project management, the clock is now ticking.

This news marks the end of an era for Microsoft’s dedicated project management SaaS platform. Project Online has been a cornerstone for many PMOs, providing a robust, SharePoint-based environment for managing projects, programs, and portfolios. Now, organizations must chart a course toward a modern alternative—a transition that demands careful planning, technical assessment, and change management.

What Is Project Online and Why Is It Retiring?

Project Online is a cloud-based service that delivers Microsoft’s enterprise project and portfolio management (PPM) capabilities through a dedicated SharePoint site collection. It supports powerful features such as portfolio analysis and optimization, demand management, time and task tracking, and resource management. Built on the Project Server engine, it has offered fine-grained control, custom fields, and enterprise-wide governance for large-scale project portfolios.

Microsoft’s reasoning for the retirement is straightforward: the company is consolidating its work management tools under the Microsoft 365 umbrella, with a focus on simplicity, collaboration, and integration with Microsoft Teams and the Power Platform. The modern successor, Microsoft Project for the web, along with the new Microsoft Planner experience, represents a shift toward lightweight, collaborative task and project management that can scale from individual to-do lists to enterprise portfolio oversight. By retiring Project Online, Microsoft aims to streamline its portfolio and direct customers to these newer solutions.

Timeline and Key Dates

The retirement roadmap gives organizations several years to migrate, but the true window for action is shrinking. Here are the critical milestones:

  • October 1, 2025 – Microsoft stops selling Project Online Professional and Premium plans to new commercial customers. Existing subscribers can still renew or add seats, but no new standalone Project Online tenants can be created. This effectively funnels new demand toward Project for the web and Planner.
  • September 30, 2026 – Project Online reaches end of life. The service becomes unavailable, and all customer data hosted in the platform will be deleted. There is no period of read-only access after this date.

Organizations currently using Project Online must complete their migration well before the September 2026 cutoff—ideally, at least six months earlier to allow for user training, parallel runs, and troubleshooting. Microsoft recommends beginning the planning process immediately.

Impact on Current Project Online Users

For enterprises deeply invested in Project Online, the retirement will have significant operational, technical, and financial implications:

  • Data Access – After September 30, 2026, all projects, schedules, resources, and custom settings will be permanently deleted. You cannot pause or extend the subscription to retain access.
  • Customizations and Integrations – Many Project Online implementations include custom workflows, fields, and integrations with ERP/CRM systems, Power BI dashboards, and third-party add-ons. These will all cease to function without a suitable replacement.
  • User and Skills – Project managers, resource managers, and team members accustomed to the Project Online interface and advanced scheduling features will need retraining on the new tools.
  • Governance and Compliance – PMOs that rely on Project Online for enforcing project methodologies, stage-gate approvals, and portfolio selection must rebuild these processes in the new platform.

The cut-off of new sales in October 2025 also means that organizations planning to expand their PPM footprint will have a limited window to add Project Online seats. If you expect growth in your PMO, you should lock in additional licenses before that date.

Where to Migrate: Understanding the Modern Alternatives

Microsoft’s recommended destination is the modern work management platform, which consists of two primary services—Microsoft Project for the web and the new Microsoft Planner. While both are part of Microsoft 365, they serve different needs and can work together:

Microsoft Project for the web

Project for the web is a web-based, lightweight project management tool that runs on the Microsoft Power Platform. It offers familiar elements like Gantt charts, task dependencies, and scheduling, but with a simpler interface than the classic Project desktop client or Project Online. Key attributes:

  • Built on the Common Data Service (now Dataverse), making it extensible with Power Apps, Power Automate, and Power BI.
  • Provides a Project Home hub that aggregates projects from across the tenant.
  • Supports co-authoring and easy sharing with Microsoft 365 Groups and Teams.
  • Includes roadmaps for visualizing project timelines across initiatives.
  • Scales from small team projects to enterprise-wide portfolios via portfolio dashboards and integration with the Planner suite.

New Microsoft Planner

In early 2024, Microsoft unveiled a unified Planner experience that merges Microsoft To Do, Microsoft Planner, and Project for the web into a single, intelligent app within Teams. The new Planner provides personalized task lists, project boards, and Gantt views, with Copilot AI assistance. For PMOs, the enterprise-grade features are delivered through the Planner Plan 1 and Planner and Project Plan 3/5 licensing, which includes advanced portfolio management capabilities.

The new Planner is the centerpiece of Microsoft’s work management future, offering:
- A single view of all tasks across personal, collaborative, and project work.
- Premium capabilities (formerly Project for the web) such as custom fields, critical path, and resource request forms.
- Deep Teams integration, enabling tasks to be discussed and updated in context.
- Portfolio dashboards and goals alignment for strategic planning.

Other Options

Some organizations may consider other paths:
- Microsoft Project Server – The on-premises counterpart of Project Online. While it receives security updates, it is a legacy product with no innovation trajectory. It may serve as a temporary bridge for those not ready for the cloud, but requires infrastructure and maintenance.
- Third-party PPM solutions – For complex needs that Project for the web/Planner may not meet, dedicated PPM tools like Planisware, ServiceNow Strategic Portfolio Management, or Jira Align can be evaluated. However, this entails a full platform migration and potential increase in cost and complexity.
- Hybrid approach – Some PMOs might use Project for the web for active projects while archiving historical Project Online data on premises or in a static SharePoint site.

Crafting a Migration Strategy: Step by Step

Migrating from Project Online is not a simple lift-and-shift. It requires a phased approach:

1. Discovery and Assessment

Catalog all active projects, workspaces, custom fields, workflows, reports, and integrations. Identify key stakeholders and understand the role that Project Online plays in business processes. Document the current resource pool, timesheet configurations, and security groups.

2. Define Target State

Decide on the target platform (likely Project for the web/Planner). Map required capabilities: Do you need portfolio analysis? Demand management? Timesheets? Check feature parity and gaps. Microsoft provides a feature matrix to help compare Project Online with the modern tools.

3. Pilot and Validation

Run a pilot with a representative set of projects and users. Test critical scenarios such as task creation, scheduling, resource assignment, and reporting. Use this phase to refine the migration approach and gather early feedback.

4. Data Migration

Microsoft offers tools and guidance for exporting Project Online data. You can use the Project Online REST API or PowerShell scripts to extract project details, tasks, assignments, and custom fields. However, due to schema differences, a direct 1:1 import into Project for the web is not always possible. Data may need to be transformed or mapped manually. Commercial migration tools from partners like FluentPro, Project Migrator, or Milestone PPM can accelerate this.

5. Rebuild Governance and Customizations

Recreate essential workflows using Power Automate. Set up Dataverse custom tables for extended data. Configure security roles, portfolio dashboards, and reporting in Power BI. This is usually the most effort-intensive part of a migration.

6. User Training and Adoption

Prepare your PMO and project teams for the new interface and processes. The shift from a heavy procedural tool to a more flexible collaborative platform can be jarring. Invest in training and change management to ease the transition.

7. Decommissioning

Once all projects and data are migrated, plan a comprehensive cleanup of the Project Online environment. Ensure you have full backups before the final shutdown. Coordinate the switch-off date and redirect users to the new tool.

Technical Considerations and Known Challenges

The retirement has surfaced several technical hurdles that PMOs must navigate:

  • Data volume – Large Project Online instances with thousands of projects and terabytes of documents in associated SharePoint sites require careful export and archival planning. SharePoint document libraries linked to projects can stay on SharePoint Online, but their project context will be lost.
  • Timesheets – Timesheet functionality in Project Online is not natively replicated in Project for the web. Organizations may need to adopt third-party time tracking or use custom Power Apps solutions.
  • Demand management – Project Online’s workflow engine for project proposals and stage gates must be rebuilt using Power Automate. This is doable but requires development effort.
  • Portfolio analysis – The built-in portfolio optimization module in Project Online is not available in Project for the web. Microsoft’s guidance points to Power BI for creating custom portfolio dashboards, but this requires data modeling and BI skills.
  • Integration – Project Online often integrates with ERPs like SAP or Oracle for actual hours and cost data. These integrations must be re-established using Dataverse connectors or APIs, potentially requiring middleware.

What PMOs Should Do Now

Given the timeline, the recommendation is to start acting in 2025:

  1. Freeze new Project Online development – Halt any major new customizations or workflows in the legacy platform to avoid wasted effort.
  2. Engage migration specialists – If your organization lacks internal resources, consider hiring experienced consultants who specialize in Project Online-to-modern migrations.
  3. Enable the new Planner experience – Begin rolling out Project for the web and the new Planner to your organization. Let teams experiment with smaller projects to build familiarity.
  4. Review licensing – Understand the transition from Project Online Professional/Premium to Planner and Project Plan licenses. Microsoft has announced that existing Project Online subscribers can transition to equivalent Planner and Project subscriptions at no additional cost until their current subscription term ends, but confirm this with your account team.
  5. Document everything – Create a runbook of all Project Online configurations, custom formulas, views, and security permissions. This will be invaluable during migration.

The Bigger Picture: Microsoft’s Vision for Work Management

This retirement is part of a broader Microsoft strategy to consolidate work management into a unified experience. The new Planner, combined with Viva Goals for OKRs, and Copilot for AI assistance, represents a shift from tool-centric to outcome-centric project management. For PMOs, this can mean less time spent on administration and more on delivering value—provided the migration is handled thoughtfully.

The end of Project Online is not just about technology replacement. It’s an opportunity to rethink how your organization manages work, fosters collaboration, and aligns projects with strategy. The forced migration might be inconvenient, but it can also catalyze a long-overdue modernization of your PMO practices.

Final Words

The September 30, 2026, deadline will arrive faster than it seems. With new sales ceasing in October 2025, the window is narrowing for those still sitting on the fence. Start your discovery now, explore the modern tools, and build a migration roadmap that minimizes business disruption. For many, the journey has already begun—and the PMOs that move early will gain the most from the flexibility and innovation of the new platform.