Microsoft’s scheduled retirement of Project Online on September 30, 2026, has sent ripples through project management offices (PMOs) worldwide, and BrightWork is the latest vendor to offer a dedicated lifeline. On June 17, 2026, the Boston-based company announced a new release of its BrightWork 365 platform, specifically engineered to streamline the migration process for organizations still dependent on the legacy tool. The move comes as thousands of businesses face a ticking clock to transition their project portfolios, resource plans, and custom workflows before the shutdown deadline.

The announcement underscores a pivotal moment in Microsoft’s broader strategy to modernize its project management ecosystem. Project Online, a longtime staple for enterprise project and portfolio management (PPM), has been in maintenance mode for years as Microsoft shifted focus to cloud-native solutions like Project for the web and Microsoft Planner. Yet for many PMOs, the path forward has been anything but clear, given the deep integration and customizations built into their Project Online environments. BrightWork 365 aims to fill that gap with a migration toolkit and a feature set that mirrors—and in some areas surpasses—what users have relied on for over a decade.

Project Online: A Legacy Titan Falls

Project Online’s origins trace back to the server-based Project Server, later reborn as a SharePoint-dependent cloud service. Launched in 2013 as part of Office 365, it quickly became the go-to platform for PMOs needing robust capabilities like demand management, portfolio analysis, and resource optimization. However, its reliance on older web technologies and SharePoint’s limitations made it less agile over time. Microsoft officially stopped investing in new features in 2019, and in 2023 confirmed the platform’s retirement, giving customers a three-year window to transition.

For PMOs, the retirement poses significant risks. Custom workflows, reporting dashboards, and integrations with other Microsoft 365 services like Teams and Power BI may not carry over automatically to newer tools. Many organizations have years of historical data, custom fields, and security configurations that need to be preserved. A rushed migration could lead to data loss, governance gaps, or prolonged productivity dips, turning a technology refresh into a business continuity crisis.

The Migration Predicament for PMOs

Industry analysts have warned that many organizations underestimated the complexity of moving off Project Online. Gartner noted that companies should have initiated migrations by Q1 2026 at the latest, yet a significant portion delayed action. With only a few months remaining, PMOs are scrambling to evaluate alternatives. The fragmentation in Microsoft’s own project management portfolio—spanning Planner, Project for the web, Azure DevOps, and the new Project Online Desktop Client—has only added to the confusion, leaving many to consider third-party solutions as a safer, more unified path.

Data complexity is the chief obstacle. Project Online tenants often contain hundreds of projects, intricate resource pools, and deeply embedded custom fields. Workflows built with SharePoint Designer are not portable, and OData feeds powering legacy Power BI reports need to be reconstructed. The cost of manual migration can be prohibitive, and the risk of error high, pushing organizations toward purpose-built migration tools.

BrightWork 365: A Purpose-Built Lifeboat

BrightWork has been a fixture in the Microsoft PPM ecosystem since 1995, originally known for its SharePoint-based project management templates. Its evolution to BrightWork 365 leverages the full Microsoft Power Platform, including Dataverse, Power Apps, Power Automate, and Power BI. This foundation ensures seamless integration into the Microsoft 365 environments that most enterprises already operate, a critical advantage when continuity is paramount.

The latest release introduces an advanced migration engine that directly imports Project Online data—projects, tasks, resources, assignments, and custom fields—into the BrightWork 365 data model. An assessment tool scans the tenant to uncover potential issues like unsupported custom field types or large datasets, reducing surprises. The platform then maps security and permissions from Azure Active Directory (now Microsoft Entra ID) to Dataverse roles, preserving access controls without manual reconfiguration.

Beyond migration, BrightWork 365 provides a centralized PMO hub that replicates the hierarchical project and portfolio views familiar to Project Online users. It supports both traditional waterfall and agile methodologies, offers real-time co-authoring, and includes mobile-friendly dashboards. Integration with Microsoft Teams allows project teams to collaborate without leaving their primary communication channel, a feature Project Online never natively supported.

Migration Roadmap with BrightWork 365

The recommended path follows a phased approach designed to minimize business disruption. First, PMOs install a trial environment and run the assessment tool. Next, they execute a pilot migration with a representative subset of projects, validating data fidelity and user acceptance. Once confidence is established, the full migration occurs—typically over a weekend—leveraging incremental sync mechanisms to keep data current until cutover.

Post-migration, the platform offers a familiar interface that dampens the learning curve. Pre-built Power BI dashboards replicate the most commonly used metrics: project status, resource utilization, cost tracking, and portfolio KPIs. These reports can be extended using Power BI’s native capabilities, connecting data from other business systems for richer insights.

Beyond Migration: The Modern PPM Experience

BrightWork 365’s value extends well beyond a one-time migration. The low-code nature of the Power Platform means PMOs can continuously adapt the system without heavy IT involvement. Forms, workflows, and reports can be modified using intuitive tools, while enterprise governance is maintained through centrally managed environments and security policies.

For organizations adopting hybrid project management, the platform supports mixed methodologies. Teams can work in agile sprints while maintaining high-level waterfall milestones, with rolling up status automatically. Time tracking, issue management, and risk registers are built in, eliminating the need for separate tools.

Collaboration features are deeply embedded. Every project site can have an associated Teams channel, and Microsoft 365 groups ensure appropriate document libraries and calendars are provisioned automatically. Co-authoring of documents in real time and mobile access mean project managers can stay productive from anywhere.

Market Context and Competitive Landscape

The Project Online sunset has ignited a scramble among PPM vendors. ServiceNow, Planview, and others have released migration tools, but BrightWork’s advantage lies in its Microsoft-native architecture and two-decade partnership. Being built on the same platform that Microsoft is pushing as the future of business applications—Power Platform—offers a level of compatibility and future-proofing that standalone SaaS products may lack.

Within the Microsoft ecosystem, the confusion is palpable. Project for the web and Planner are evolving into a new Planner-based work management solution, but they lack the portfolio-level governance and resource management that PMOs demand. Microsoft’s own Project Operations targets service-centric organizations and does not cover the broad PPM needs of internal PMOs. This gap makes specialized solutions like BrightWork 365 essential for many enterprises.

The Clock Is Ticking: Final Recommendations

With less than four months until the September 30 deadline, PMOs must act immediately. The first step is to audit the current Project Online footprint: how many projects are active, what customizations exist, and what integrations are critical. Starting a trial of BrightWork 365 or engaging a migration partner can kickstart the process and reveal hidden complexities.

Organizations should also back up their Project Online data using Microsoft’s native export tools, even if they plan to use a migration tool, as a safety net. Training programs for project managers on the new platform should run in parallel to ensure a smooth transition.

Looking Ahead: The Post-Project Online Era

Project Online’s retirement marks the end of an era but also an opportunity. By moving to a modern PPM platform, organizations can shed technical debt and embrace agile, collaborative, and AI-infused project management. Microsoft’s upcoming Copilot for the Power Platform promises to bring natural language processing to project management, something BrightWork 365 will be well-positioned to leverage as a native solution.

As the deadline approaches, the project management community will be watching closely. For those who embrace the change with deliberate planning and the right tools, the post-Project Online world may prove to be a significant step forward.