For energy and utilities portfolio teams, the Project Online shutdown lands on data that regulators depend on. Capital project records in a regulated utility feed rate cases, drive depreciation from in-service dates, and support the regulatory capital recovery that determines allowed returns. Losing that data, or breaking the link between project cost and regulated asset, is not an IT inconvenience, but a threat to how the utility recovers its capital investment.
The shutdown date is fixed, and the planning work for regulated utilities is heavier than a standard migration because the data carries financial and regulatory weight that outlives the software. Before Project Online goes away, energy and utilities teams need to protect the capital tracking, cost data, and asset records that their rate recovery and compliance reporting depend on. Here is how to plan the transition around what actually matters.
Why the shutdown hits utilities differently
The core difference is that utility capital data is tied to regulated financial outcomes, not just project delivery. A construction firm loses scheduling history. A utility risks the traceability between capital spend and the regulated asset base that rate recovery is built on.
According to ​Microsoft’s lifecycle documentation, Project Online retires on September 30, 2026, after which the service and its data become inaccessible. For a utility, several things sit on that data that a general PMO never has to consider. Capital projects link to fixed assets and depreciation schedules driven by in-service dates. Rate-case reporting draws on documented project costs. Long asset lifecycles mean project records may be referenced years after completion. Preserving these connections requires the ​enterprise architecture and data integration discipline that keeps cost, asset, and regulatory data linked through the move.
What utilities need to protect before the deadline
Several categories of data need explicit attention, because each supports a regulated financial process that a broken migration would disrupt.
Capital cost tracking and asset linkage
Confirm that the link between project costs and the fixed assets they create survives the migration. Utilities recover capital through rates based on documented, in-service assets, so a break between project spend and asset record directly threatens rate recovery. Preserving this linkage is the single most important protection, and it depends on connecting project data to the ​work and operations management and financial systems that own the asset base.
Rate-case and regulatory reporting data
Rate cases draw on historical project cost data to justify recovery. Confirm that the documented costs, schedules, and supporting records regulators may examine are exported and preserved in a defensible form before access is lost. Reconstructing this after the deadline may not be possible, which is a compliance risk no utility wants during a rate proceeding.
In-service dates and depreciation triggers
In-service dates drive when depreciation begins and when an asset enters the rate base. Confirm that the project data establishing these dates is preserved accurately, since errors here ripple directly into financial reporting and regulated returns, which is why connecting project data to trustworthy ​analytics and reporting matters through the transition.
Long-horizon project history
Utility assets operate for decades, and their originating project records may be referenced long after the project closes. Confirm that historical project data is archived in an accessible, searchable form for the full period the utility may need it, using disciplined ​data migration practices.
How utilities should plan the transition
A regulated utility cannot afford a rushed cutover that risks its capital data. The planning has to lead with financial and regulatory continuity.
Start by inventorying which project records feed rate cases, asset accounting, and depreciation, and get sign-off from finance, regulatory, and IT on what must be preserved and how. Establish how the new platform will maintain the project-to-asset linkage before migrating, then move in controlled stages with capital data integrity confirmed at each step. Utilities are increasingly shifting capital programs toward a larger number of smaller projects, which makes portfolio-level visibility across many concurrent projects more important than ever. Grounding the transition in a governed approach that connects project, cost, and asset data is what protects rate recovery through the change.
Protect the capital data your rates depend on
The Project Online shutdown gives energy and utilities teams a hard deadline to protect data that regulators and rate recovery depend on. Capital cost tracking, asset linkage, rate-case records, and in-service dates all have to be preserved while the source system is still live, because after the deadline the data is gone and the regulatory exposure is real. The utilities that plan this transition around financial and regulatory continuity come through with their capital data intact. Those that treat it as a routine tool swap risk breaking the traceability their rate recovery is built on.
If your energy or utilities organization is planning its move off Project Online, ​connect with Advaiya’s team. Advaiya combines energy and utilities experience with Microsoft data platform and OnePlan migration expertise to help regulated portfolio teams preserve capital tracking, asset linkage, and the rate-case data their recovery depends on.
Frequently asked questions
Microsoft Project Online retires on September 30, 2026, after which the service and its data become inaccessible. For energy and utilities organizations, this date functions as a deadline to preserve capital project data that feeds rate cases, asset accounting, and regulatory reporting before access is lost.
Utility capital data ties to regulated financial outcomes, not just project delivery. Capital projects link to fixed assets and depreciation, rate cases draw on documented project costs, and long asset lifecycles mean records are referenced years later. Breaking these links threatens rate recovery in a way general project management never faces.
Utilities should protect the linkage between project costs and the fixed assets they create, rate-case and regulatory reporting data, in-service dates that drive depreciation, and long-horizon project history. Each supports a regulated financial process that a broken migration would disrupt.
Utilities recover capital through rates based on documented, in-service assets. Project cost data establishes what was spent and when assets entered service. If the migration breaks the link between project spend and the asset record, it can disrupt the traceability that rate recovery and rate-case justification depend on.
Utilities should inventory which records feed rate cases, asset accounting, and depreciation, get sign-off from finance, regulatory, and IT, establish how the new platform maintains project-to-asset linkage before migrating, and move in controlled stages with capital data integrity confirmed at each step.
In-service dates determine when depreciation begins and when an asset enters the rate base. If the project data establishing these dates is lost or corrupted during migration, it ripples directly into financial reporting and regulated returns, making their accurate preservation essential.
