For years, Project Online, Microsoft’s cloud-hosted project and portfolio management (PPM) solution, built on SharePoint Online has played a central role in enterprise environments, supporting everything from detailed scheduling to portfolio governance and reporting. However, Microsoft has officially announced the Project Online retirement without a direct migration path, leaving organizations to chart their own course forward.
Microsoft’s Project Online retirement date is September 30, 2026. After this date, the service will no longer be accessible, and any data (including projects and schedules) stored within Project Online will no longer be available. This retirement applies only to Project Online itself; luckily, Project Desktop, Planner, Project Server Subscription Edition, and Dynamics 365 Project Operations are not impacted.
The approaching Project Online retirement makes it critical for customers to export, migrate, or replace Project Online before data is lost before their data is completely lost at the end of September. Success is laid out in the small steps forward. Planning migration early helps avoid rushed decisions near the retirement date. Challenges of all kinds may surface during migration, such as needing to replace custom SharePoint workflows, rebuilding Power BI reports tied to Project Online data, and migrating historical schedules and baselines. Your organization could also greatly benefit from carefully managing this change by retraining project managers on and aligning PMO governance to your selected replacement tool, as well as avoiding parallel systems during the transition.
What Should Businesses Do Before Project Online Retirement?
Inventory how Project Online is used today (whether it’s used for scheduling, reporting, workflows, financials, and more). Then identify critical reports, integrations, and dependencies (such as Power BI, SharePoint, Finance, HR, or other custom APIs). You’ll want to select a target platform based on the best fit to your business model, not your current habits, by defining target platform and success criteria. This is your chance to not just replace but also modernize your project and portfolio management system to better suit your company tomorrow and not your company yesterday.
Common Project Online Dependencies Organizations Forget
- Power BI dashboards connected to Project Online data
- SharePoint workflows tied to project approvals
- Custom APIs
- Resource planning integrations
- Financial reporting dependencies
- Historical project baselines
- PMO governance workflows
What Happens After September 30, 2026?
BCS can support customers through the Project Online retirement by performing a technical and functional assessment of how Project Online is currently used, including scheduling patterns, governance constructs, reporting dependencies, and downstream integrations. Based on this assessment, BCS can help customers determine whether Planner Premium or Dynamics 365 Project Operations is the most appropriate replacement, aligned to their delivery and financial operating model.
For customers adopting either solution, BCS can design and implement custom integrations with Dynamics 365 Business Central, addressing a gap where no native Microsoft integration exists. This includes solutions that automatically synchronize jobs and job tasks in Business Central with project plans, ensuring alignment between operational execution and financial tracking while minimizing manual maintenance.
Navigating Project Online Retirement
Below are Microsoft alternatives organizations commonly evaluate during Project Online retirement planning:
- If usage was minimal → Planner (Basic)
- Microsoft does not recommend Planner (Basic) as a PPM replacement
- If Project Online was mainly used for task scheduling → Planner Premium
- If it supported delivery → Project Operations
- If strict parity and control are required → Project Server SE
Microsoft Project Online Alternatives & Comparison
Planner (Basic)
- Best fit
- Small teams
- Internal initiatives
- Lightweight task coordination
- Characteristics
- Simple task boards and collaboration
- No portfolio governance, financials, or advanced resourcing
- Included with many Microsoft 365 plans
- Industries / use cases
- IT teams, marketing, operations, product teams
- Departments that never used Project Online for PPM rigor
- Microsoft positions Planner (Basic) as task management, not PPM.
Planner Premium (Planner + Project for the web)
- Best fit
- Organizations replacing Project Online for modern scheduling
- Teams that need dependencies, timelines, and basic portfolio views
- Characteristics
- Gantt charts, dependencies, baselines
- Built on Power Platform and Dataverse
- Integrated with Teams and Microsoft 365
- Strategic investment area for Microsoft
- Industries / use cases
- IT PMOs
- Digital transformation initiatives
- Internal enterprise project delivery
Dynamics 365 Project Operations
- Best fit
- Project‑based businesses
- Organizations where delivery, finance, and resourcing are tightly coupled
- Characteristics
- Project planning + resource management
- Time, expense, cost tracking, billing
- Built on Dataverse and Power Platform
- Uses the Planner Premium scheduling engine
- Explicitly positioned by Microsoft as a Project Online migration path
- Industries / use cases
- Professional services
- Consulting
- Engineering services
- Construction services (non‑CPM heavy)
- Managed services
Project Server Subscription Edition (SE)
- Best fit
- Organizations needing near‑parity with Project Online
- Regulated or highly controlled PMOs
- Characteristics
- On‑premises or hosted
- Similar architecture and concepts to Project Online
- Less innovation velocity than Planner / Project Ops
- Similar architecture and concepts to Project Online
- On‑premises or hosted
- Industries / use cases
- Government
- Defense
- Heavily regulated enterprises
- PMOs with deep PWA customizations
The Project Online retirement is more than a platform change. For many organizations, it is an opportunity to modernize project delivery, reporting, governance, and operational alignment across Microsoft business applications.