Microsoft Product Retirement: How Project Online Compares to Past Office Sunsets

Here is what every Microsoft product retirement has in common. An announcement appears in the M365 Message Center. A date is set. Partners publish migration guides. Customers divide into three groups: those who start planning immediately, those who wait for additional clarity that never comes, and those who process the announcement too late to run a clean migration.

The pattern is more consistent than most PMO directors expect. Microsoft retired Skype for Business Online in 2021 after two years of notice. Microsoft has been sunsetting InfoPath across cloud and on-premises products for over a decade. The mechanics of how Microsoft handles each retirement reveal what Project Online PMOs should actually expect for the remainder of 2026.

The diagram below shows the announcement-to-retirement timelines for three Microsoft product retirements, including Project Online.

The Three-Phase Pattern Behind Every Microsoft Product Retirement

Looking across multiple Microsoft product retirements, a consistent three-phase structure emerges. Understanding it helps PMOs predict what is coming and avoid the mistakes that previous customers made.

Phase 1: Announcement. Microsoft publishes notice through the M365 Message Center and a dedicated "what is changing" page on Microsoft Learn or the Tech Community blog. For products with significant enterprise footprint, this announcement typically comes 18 to 30 months before retirement. The announcement names a hard date and a recommended migration path. The recommended path is usually another Microsoft product.

Phase 2: Migration window. Microsoft publishes migration guidance documentation, sometimes makes migration tooling available (data export tools, compatibility reports), and answers questions through support channels. Partner ecosystems produce their own guides. In some cases (Skype for Business), Microsoft offers assisted migration for customers who have not moved by a threshold date close to retirement. In most cases (InfoPath), there is no assisted migration; customers are on their own.

Phase 3: Hard cutover. On the announced date, the service stops. There is sometimes an informal read-only period, but Microsoft has not contractually guaranteed one for Project Online. The lesson from every prior retirement: plan as if the cutover is hard and the announced date is final.

The pattern has not varied significantly across product generations. Microsoft sets a date and keeps it.

The diagram below shows the three-phase retirement pattern applied to the Project Online timeline.

InfoPath: Microsoft's Longest-Running Sunset

InfoPath Forms Services is the extreme end of the Microsoft retirement spectrum. Microsoft first signaled that InfoPath was not the future of forms in roughly 2014 when it moved away from new InfoPath development. InfoPath 2013 received mainstream support through April 2019 and extended support through April 2023. InfoPath Forms Services in Microsoft 365 will be removed in July 2026: more than 12 years after the product was effectively deprecated.

What this retirement pattern teaches:

Microsoft rarely forces customers off products quickly. Customers who built deep InfoPath workflows in 2012 had over a decade to migrate. Many did not move until forced. That deliberate pace creates a false sense of permanence.

The replacement product matters. Microsoft recommended Power Apps as the InfoPath replacement. Power Apps is a genuinely capable forms and workflow platform that has matured significantly since 2017. Customers who migrated early got a functional replacement and time to rebuild complex forms. Customers who waited until the last months got the same migration scope compressed into a shorter window.

Extended runways breed complacency. The 12-year window for InfoPath produced an unusually high concentration of last-minute migrations. Organizations that had 12 years to migrate spent years 1 through 10 in various stages of "we'll get to it" and years 11 through 12 in emergency migration mode. Project Online has a 26-month window. The compressive effect is already visible in the late-stage migrations happening in 2026.

Skype for Business Online: The 24-Month Migration Done Right

Microsoft announced the retirement of Skype for Business Online in July 2019, with the retirement date of July 31, 2021, giving customers 24 months. The Skype for Business Online retirement page on Microsoft Learn documented the full transition timeline and migration path.

Several things went well with this retirement that are worth understanding:

The destination product was genuinely better. Microsoft Teams replaced Skype for Business Online and extended it significantly: persistent chat, integrated file sharing, video meetings with breakout rooms, phone system capabilities. Organizations that migrated early got measurable improvements in collaboration. The migration had business value beyond compliance.

Microsoft provided assisted migration for laggards. For organizations that had not migrated by the retirement date, Microsoft began automated assisted upgrades to Teams in August 2021, moving remaining Skype for Business Online users to Teams Only mode. The experience was not seamless for everyone, but it meant no customer was permanently stranded.

The Teams admin center provided upgrade reports. IT admins could see at a glance which users had been upgraded and which remained on Skype for Business. The tooling reduced the operational uncertainty of a large tenant migration.

The result: by the July 31, 2021 retirement date, the majority of Microsoft 365 customers had migrated to Teams. Those who had not were handled by the assisted upgrade process.

How the Project Online Retirement Compares to Those Precedents

The Project Online retirement shares the notice period of Skype for Business (approximately 26 months) and exceeds the abruptness of the InfoPath removal. The critical difference lies in the destination product.

For Skype for Business Online, Microsoft Teams was a genuine replacement: same user population, richer feature set, active investment. For Project Online, Microsoft's recommended destination is Project for the Web and Planner Premium. Those products serve a different customer segment: small teams running individual projects without enterprise resource pools, timesheet workflows, portfolio governance, or multi-project OData reporting.

Enterprise PMOs using Project Online for 50 to 500 projects, with enterprise resource pools, custom approval workflows, and Power BI reporting built on OData, are not the primary design audience for Project for the Web. This is not a complaint about Microsoft's product strategy; it is an observation about where the feature gap exists.

This destination gap is the reason the Project Online migration market has a wider variety of third-party platform options than the Skype-to-Teams transition did. When Microsoft builds a strong first-party replacement, most customers use it. When the first-party replacement does not cover the enterprise use case, the market fills the gap.

No Microsoft-assisted migration program comparable to the Skype for Business automatic upgrade has been announced for Project Online. Based on the pattern, the most likely scenario is that Microsoft publishes export tooling and documentation, but organizations that have not migrated by September 30, 2026 will simply lose access, with no automated fallback.

What Microsoft Typically Does for Customers Who Miss the Window

Based on the historical pattern, here is what enterprise customers who miss a Microsoft product retirement deadline can realistically expect:

OData and PWA access stops on the announced date. Microsoft has not deviated from retirement dates once announced. September 30, 2026 is the date.

An informal read-only period may exist. Microsoft's previous SaaS retirements have sometimes included a 60 to 90 day informal window where data remains accessible in a limited read-only state. This is not contractually guaranteed for Project Online. The responsible planning assumption is no read-only window.

Microsoft will not recover data after the informal window closes. Once the formal retirement period has passed, structured project data (tasks, dependencies, resource assignments, custom fields, timesheets) is permanently inaccessible. This is not like a SharePoint site that can be restored from a backup; the Project Online database schema is service-specific and not exported.

Microsoft Support will not accelerate migration work. Support teams can answer questions about data that can still be accessed, but they cannot extend the service beyond the retirement date or recover data that was not exported before cutover.

The organizations that navigate this cleanly are the ones that treated the announcement date as the starting gun, not the retirement date.

What the Pattern Predicts for Project Online's Final Months

Based on the Skype for Business Online and InfoPath retirement sequences, here is what PMOs should plan for in the months leading up to September 30, 2026:

May through July 2026: Microsoft will likely increase the frequency of M365 Message Center notifications reminding administrators of the retirement date. Service health advisories may begin to appear. The partner ecosystem will publish additional migration guides and tooling. Emergency consulting rates will begin rising.

August 2026: Final export window. OData service performance may degrade as large numbers of tenants execute simultaneous data pulls. Any organization that has not completed a clean OData snapshot and .mpp export by August 31 is at meaningful risk of incomplete export coverage.

September 1 to 29, 2026: Final communications and dependency cleanup. Power BI reports, Power Automate flows, and Teams integrations that have not been redirected will begin showing errors in testing. This period should be for confirmation, not export.

September 30, 2026: Hard cutover. PWA stops, OData returns 410, ERP becomes unreachable, timesheets close. This is the same cutover sequence Microsoft has followed for every other retired SaaS product.

The Project Online end-of-life timeline provides a month-by-month breakdown of what that sequence looks like for a typical mid-size PMO.

How to Use This Pattern to Make Your Migration Decision Now

The pattern from prior Microsoft product retirements points to two actionable conclusions.

First, the deadline is real and will not move. The organizations that used the InfoPath runway most effectively committed to a migration platform within the first 6 months of the announcement and used the remaining time for systematic execution. Project Online PMOs who received the July 2024 announcement and have not yet committed to a destination platform are in the same position as InfoPath administrators were in 2020: capable of making a clean move but running out of time to do it without pressure.

Second, evaluate the destination product against your actual use case. Microsoft's first-party recommendation may not cover what your PMO relies on today. Run the inventory of your current Project Online usage before selecting a destination. The features that matter to your PMO are the ones that need to map to the new platform: not the features in a product brochure.

Use the Migration Preview tool to map your current tenant complexity and understand what a migration to different platforms would actually involve. The goal is to have a signed migration contract and a sprint plan in place by June 2026. That leaves three months for execution, which is sufficient for a focused PMO and insufficient for an unprepared one.

For organizations that have not yet run a full Project Online tenant inventory, start there. The retirement is happening on the same schedule whether the planning is done or not.

Run a free Migration Preview Map your Project Online tenant in 10 minutes and get a structured picture of what your migration would involve. No signup required. → Open Migration Preview

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.