New BrightWork 365 Upgrade Aims to Ease PMO Migration Ahead of Project Online’s 2026 Sunset

Microsoft’s decision to retire Project Online on September 30, 2026, is forcing thousands of project management offices to rethink their tool stacks right now—and BrightWork’s June 17 release of its latest BrightWork 365 platform is timed to capitalize on that urgency. The Redmond giant quietly updated its support lifecycle page early this year, confirming that commercial customers will lose access to the dedicated Project Online environment after the 2026 date, with no option for extended support. For PMOs built around SharePoint-based project sites, structured portfolio dashboards, and complex resource models, the migration isn’t just a software swap—it’s a governance overhaul.

BrightWork 365 has been marketed as a low-code alternative on the Microsoft Power Platform since 2021, but the new release adds specific migration wizards, a revamped portfolio dashboard, and direct parity reports that compare Project Online configurations to what the 365 edition can replicate. The company disclosed that it’s already handling pilot migrations for three Fortune 500 firms, each with over 5,000 active project plans. The announcement landed in a blog post on June 17, just days after Microsoft’s own PMI Global Congress session where the retirement roadmap was dissected in a packed room of project professionals.

The Project Online Retirement: What Stops Working and When

Microsoft’s timeline is unambiguous. Project Online—the server-based, multi-tenant service accessed via a dedicated Project Web App URL—will stop accepting new customer sign-ups by early 2025, though the exact cut-off for trials and new tenants hasn’t been publicly listed in the message center yet. For existing customers, the lights go out on September 30, 2026. After that date, Microsoft will delete all Project Online data and sites; there is no archive-only mode, no read-only grace period, and no hybrid coaster that keeps old reports alive while you transition.

This affects only the Project Online standalone product. Project Online Desktop Client (the thick client often paired with it) is already out of mainstream support for most perpetual versions, and the subscription-based Project Plan 3 and Plan 5 licenses will continue to work with Project for the web and the new Planner. But that nuance often gets lost: many license holders don’t realize that their Plan 3 seats will survive while their existing Project Online environments get vaporized. The confusion has sparked a cottage industry of consultants and ISVs offering “readiness assessments,” with BrightWork now positioning its 365 tool as more than a stopgap.

The retirement creates a hard boundary for compliance-heavy industries. Organizations that built custom workflows—particularly those using Project Server Interface (PSI) or complex SharePoint Designer flows to enforce stage-gate approvals—will find zero one-to-one equivalents in the new Planner or Project for the web. Microsoft’s official migration guidance points to using the Project Data Service to export plans, but that only grabs the raw .mpp data; it leaves behind the security groups, enterprise custom fields, and business intelligence (BI) cubes that PMOs spent a decade refining.

Why BrightWork 365 Chose This Moment to Refresh

BrightWork’s June 17 announcement wasn’t subtle. The press release, titled “Project Online is Retiring – Meet Your Next PMO Platform,” dropped alongside a webinar registration link and a feature comparison white paper. The new BrightWork 365 release—version 4.2, according to the release notes—introduces three headline capabilities that speak directly to Project Online refuges.

First is a Project Online Import Engine. Rather than simply ingesting .mpp files, the import tool connects to a tenant’s Project Online instance via OAuth, reads the entire project site collection, and maps enterprise custom fields, lookup tables, and resource plans to equivalent Dataverse tables. During early access demos, BrightWork showed a 2,500-project import completing in under six hours, complete with risk and issue lists preserved.

Second is the Power BI Template Hub. Project Online’s strongest selling point over the years was the OData feed that fed Excel and Power BI reports, especially for portfolio scorecards. BrightWork’s new hub ships with 28 pre-built Power BI reports—covering schedule variance, RAID logs, portfolio KPIs, and resource heat maps—that connect directly to the Dataverse instance underpinning BrightWork 365. Because the data model is open, PMOs can modify reports without writing SQL or waiting for IT.

Third is Stage-Gate Workflow Builder, a low-code progression engine that mimics the approval chains PMOs used in classic SharePoint Designer workflows. It runs natively inside Power Automate, so approvals can route through Teams, email, or the mobile Power Apps interface. Early testers at a Midwest construction firm reported that they recreated a 14-step capital expenditure approval process in two days, down from a four-week SharePoint workflow migration that never fully worked in the new Planner.

Under the Hood: The Power Platform Advantage

BrightWork 365 is essentially a model-driven Power App built on Microsoft Dataverse. That architecture matters because it sidesteps the classic SharePoint list limits that hamstrung Project Online for years—the 5,000-item threshold often forced PMOs to archive old projects just to keep the site working. Dataverse comfortably handles millions of rows, and BrightWork’s entity model separates projects, tasks, resources, and risks into relational tables that support complex reporting without aggregating across thirty lists.

Because it lives on the Power Platform, any organization with Microsoft 365 E3 or E5 licenses already owns the runtime, though BrightWork 365 itself requires an additional per-user or per-project subscription. The platform also benefits from Microsoft’s investment in Copilot: a growing number of BrightWork customers are using the Power Apps Copilot control to generate status reports from task comments, and the June 17 update officially supports the Copilot panel for natural-language portfolio queries such as “show all red projects owned by the marketing office.”

The security model is another differentiator. Project Online’s security relied on SharePoint groups and category permissions that often became unwieldy. BrightWork 365 uses Dataverse business units and role-based access inherited from the Microsoft 365 admin center. A PMO lead can see all projects while a project manager sees only her own, all enforced through Azure AD groups, which simplifies audit trails for SOC 2 or ISO 27001 compliance.

Community Reaction and Real-World Migration Pain

On Microsoft’s Project Community Forum and the PMO Leaders LinkedIn group, the June 17 announcement ignited a flurry of parallel conversations. Several long-time Project Online administrators expressed relief that an ISV was explicitly targeting the migration, but also skepticism about one-click import promises. One PMO director from a European pharmaceutical company posted a detailed critique: after testing the import engine on a 1,200-project environment, about 12 percent of custom field formulas broke because they referenced project-level summary tasks differently than Dataverse allows. BrightWork responded publicly within 24 hours, acknowledging the limitation and promising a formula translator in the next quarterly update.

Another common thread involved licensing costs. Project Online Plan 3 currently runs about $30 per user per month. BrightWork 365 starts at $15 per user per month for the professional plan, but advanced portfolio features and the new Power BI templates require the premium tier at $25 per user. When factoring in the Power Apps per-user plan—often already included in E5, but not in E3—the total cost can land close to what organizations paid for Project Online, erasing the cost-saving argument. However, analysts at Directions on Microsoft note that the elimination of dedicated Project Online server infrastructure can save mid-size firms $40,000–$80,000 annually, potentially offsetting the per-user delta.

How BrightWork Stacks Against Microsoft’s Native Path

Microsoft is pushing Project for the web (based on the Microsoft Power Platform) and the new Planner (which merges To Do, Planner, and Project for the web into a single application) as the forward path. For teams running simple task lists or agile boards, that evolution works. But for PMOs running traditional CPM scheduling with earned value, baseline tracking, and inter-project dependencies, Project for the web as of mid-2025 still lacks several features that Project Online delivered in 2016.

A side-by-side comparison of BrightWork 365 v4.2 and the latest build of Project for the web (as of June 2025) reveals key divergence points:

This gap explains why BrightWork isn’t just competing against Microsoft’s roadmap—it’s filling a vacuum that the new Planner roadmap hasn’t addressed yet. Microsoft’s own project management general manager acknowledged at the PMI event that advanced portfolio management will be a focus “beyond 2025,” leaving an uncomfortable window for organizations with September 2026 deadlines.

The Migration Playbook BrightWork Is Recommending

In the white paper that accompanied the June 17 release, BrightWork outlined a four-phase migration methodology that it’s now packaging as a service:

1. Analysis (30 days): The import engine scans the Project Online environment and produces a compatibility matrix, flagging custom workflows, fields, and reports that need rework.
2. Pilot (60 days): A subset of high-profile projects migrate first, using a dual-run approach where both Project Online and BrightWork 365 update simultaneously for a month.
3. Full migration (90 days): Remaining projects move in waves, with automated scripts handling data mapping and cleanup.
4. Optimization (ongoing): PMO teams use the Power BI Template Hub to refine reports and retire legacy SharePoint sites.

Crucially, BrightWork 365 does not require a SharePoint migration. Project Online data moves directly into Dataverse, and the original SharePoint project sites can remain untouched as an archive or get decommissioned separately. This decoupling is attractive to IT teams that want to freeze old infrastructure without rebuilding it.

Risks and Unanswered Questions

Any platform that promises to swallow a decade of customized Project Online data will hit edge cases. BrightWork’s own documentation lists unsupported features in version 4.2, including multi-language enterprise custom fields, some PSI custom integrations, and project-level budget tracking that uses cost resources tied to rate tables. Organizations that heavily customized their Project Online timesheet experience will need to rebuild those interfaces in Power Apps or adopt a third-party timesheet connector.

There’s also the question of BrightWork’s own long-term viability. With Microsoft itself iterating rapidly on Planner and Project for the web—and even hinting that Copilot-driven project management could subsume some PMO functions—committing to a third-party overlay carries platform risk. BrightWork’s leadership addresses this by pointing to its track record since 1995 and the fact that its product runs on Microsoft’s own technology, making it as much a part of the Microsoft 365 ecosystem as any first-party app.

Analyst Take: The 18-Month Window Tightens

Industry analysts are advising clients not to wait until 2026 to begin migration planning. “The September 2026 date feels far away, but if you factor in budget cycles, the need for UAT, and the reality that key staff may leave before the transition, 18 months is an aggressive timeline,” said an independent PPM consultant who works with government agencies. Government and education tenants, which often run on slightly different retirement schedules, will need to confirm their specific dates through their Microsoft account teams.

BrightWork’s announcement on June 17 may also pressure other ISVs in the PPM space—like Projectum, OnePlan, and Sensei Project Solutions—to accelerate their own migration tooling. Each has a Power Platform-based offering, but BrightWork’s dedicated import engine and template library give it a temporary lead in the “lift and shift” segment of the market.

What PMOs Should Do Now

For PMO leaders reading this news, the immediate action items are:

• Inventory your Project Online environment immediately. Use the built-in PWA settings to export a complete inventory of custom fields, workflows, security groups, and reports.
• Start a parallel pilot of either BrightWork 365 or another alternative on a small set of projects. Don’t wait for the final feature set to freeze—the learning curve is real.
• Engage your Microsoft licensing partner to understand what’s included in your current agreement. The move from Project Plan 3 to a Power Apps-based solution may require adjusting your licensing baseline.
• Map out your data archiving strategy. If you need to keep historical project data beyond 2026, decide whether it lives in Dataverse, a data lake, or a static backup.

BrightWork’s June 17 release isn’t a silver bullet, but it’s the most concerted effort yet by any ISV to turn Project Online’s sunset into a migration lane rather than a cliff. With the clock now ticking audibly, PMOs have about 15 months to choose a road—and the ones that start mapping today are far less likely to spend the summer of 2026 in crisis mode.