FR → Book a call
§ MENU
Approach
§ PRODUCTS · PLATINE Platine Vibe OS § PLATFORMS WE LEAD ON Dynamics 365 Business Central Project Online · Migration
§ THE PRACTICE Engagements Industries § THINKING & WRITING Field Notes
About Contact → Français → Book a call
§ SOLUTION · MICROSOFT PROJECT ONLINE · MIGRATION

Project Online is retiring.
Plan the move before
the move plans you.

Microsoft has retired Project Online — the SharePoint-based PWA that has run mid-market and enterprise project portfolios for two decades. Read-only mode arrives on the published date. Full deprecation follows. Custom workflows, third-party PWA add-ons, and SharePoint-coupled artifacts go with it.

Four migration paths exist, and they are not equivalent. This page is the planning brief — what each path costs, what you keep, what you lose, and how Platine helps you decide.

§ 01 · THE FACTS

What Microsoft actually said.

Microsoft has communicated a structured retirement for Project Online. The platform enters a read-only window before full decommissioning. After full retirement, the SharePoint-hosted PWA, its custom workflows, its database-backed reports, and its ecosystem of third-party PWA add-ons stop functioning.

Refer to Microsoft's official lifecycle and deprecation announcements for the exact timeline applicable to your tenant. The retirement is not a rumor and it is not a "future possibility" — it is a published transition with a date.

What remains supported indefinitely: Microsoft Project Desktop (the standalone .mpp client), and the modern successors — Project for the Web, Project Operations, and the broader Power Platform fabric. The retirement applies specifically to the SharePoint-based PWA experience.

§ 02 · WHAT YOU'LL LOSE / WHAT SURVIVES

The honest inventory.

→ Goes away

Lost at retirement.

  • PWA-specific custom workflows (SharePoint-based, often built over years)
  • Resource engagement / capacity-planning workflows native to PWA
  • Custom PWA timesheet flows (if not migrated to Project Operations)
  • Reports built directly on the SharePoint PWA database
  • Third-party PWA add-ons (SharePoint-coupled apps lose their host)
  • Earned-value management (EVM) — only Project Operations preserves this in-Microsoft
  • PWA-specific permission models (need re-design in Dataverse for the Microsoft paths)
→ Survives

Stays with you.

  • Project schedule data — exportable to standard formats (MPP, XML, CSV)
  • Resource master data — exportable and re-importable into any target
  • Historical project records (for archival)
  • Microsoft Project Desktop client (continues to work standalone)
  • Power BI reports built on the Project Online OData feed (need re-pointing to new source)
§ 03 · THE FOUR PATHS

Four migration paths. Not equivalent.

Comparison below. The right answer depends on your project culture, your ecosystem investment, and the workflows that actually matter to your operators.

A. Project for the Web Microsoft · Dataverse-native · cloud-first 6–12 weeks

Lightweight project planning for teams that managed simple work in Project Online — task lists, schedules, basic resourcing. Microsoft's recommended path for most former Project Online users.

→ Gains
  • Native Microsoft 365 + Teams integration
  • Power Platform-extensible
  • Modern UX, lower learning curve
  • Per-user pricing aligned to Microsoft 365
→ Trade-offs
  • Earned-value management (EVM)
  • Custom PWA workflows
  • Resource engagement workflows from PWA
  • Some PMI/PMBOK compliance features
B. Project Operations on Dynamics 365 Microsoft · D365-native · full PSA 12–20 weeks

Project-driven services firms that need full PSA — billable hours, resource management, project finance, revenue recognition tied directly to ERP. The migration target for organizations that ran Project Online tightly coupled with billing or resource economics.

→ Gains
  • Full project accounting integrated with finance (BC or F&O)
  • Billable resource management at scale
  • Revenue recognition automation
  • Dataverse-native, Power BI–ready
→ Trade-offs
  • Higher complexity than PWA — implementation effort grows
  • Per-user license cost rises significantly
  • Some PWA-specific reports require redesign
C. Third-party PPM Smartsheet · Asana · Monday · Wrike · ServiceNow SPM 8–14 weeks

Organizations whose project work has drifted toward task-tracking and collaboration rather than formal PPM. Frequently a better fit than the Microsoft path when your project culture is light.

→ Gains
  • Often faster adoption — operators tend to like these tools
  • Strong collaboration features out of the box
  • Independent of Microsoft licensing trajectory
  • Many vendors offer migration accelerators from PWA
→ Trade-offs
  • Integration cost into Microsoft 365 stack
  • Two ecosystems to govern
  • Licensing duplication if Microsoft 365 is non-negotiable
D. Hybrid — Power Platform + Planner / Loop Custom · Microsoft-aligned · lightweight 6–16 weeks (varies with custom scope)

Organizations whose Project Online usage was lightweight to begin with — many never needed a full PPM. Power Platform + Planner + Loop replaces 80% of the value at 20% of the cost, with custom Power Apps for the workflows that mattered.

→ Gains
  • Lowest total cost
  • Full alignment with Microsoft 365 fabric
  • Custom-fit to actual workflows (no force-fit)
  • No third-party licensing
→ Trade-offs
  • Custom-build cost up front (offset by license savings over 3–5 years)
  • Requires governance discipline
  • Not a "real" PPM — formal portfolio management is out of scope
§ 04 · HOW PLATINE HELPS

The methodology, applied to migration.

Listen. We sit with PMO, project managers, resource owners, and the IT team that built or maintained the PWA estate. We catalogue the custom workflows, the integrations, the reports, and the third-party add-ons. We name what each artifact actually does versus what its documentation says.

Diagnose. Current PWA usage measured. Custom artifacts assessed for survival. Project culture assessed (formal PPM vs. lightweight task tracking). Output: a written recommendation that names the path and the cost of getting there. Sometimes the answer is not a single path — it is a hybrid.

Design. Target architecture documented. Data migration mapped. Workflow rebuilds identified (which survive, which get retired, which become Power Automate). Change-management approach for the project-management community. Parallel-running cutover strategy.

Deliver. Phased migration with parallel operation. Knowledge transfer to PMO and IT. Operating runbook for the new platform. Outcome ledger measuring against the Phase-02 baseline.

§ 05 · TYPICAL ENGAGEMENT

Honest scope, duration, and cost.

§ 06 · INDUSTRY CONTEXT

What the data shows.

  1. 60%+

    Of organizations migrating off Project Online choose a Microsoft-native target (Project for the Web, Project Operations, or hybrid Power Platform). The remainder go to Smartsheet, Asana, Monday, or ServiceNow SPM.

    — Industry analyst surveys on PPM migration patterns
  2. 12–24 months

    Typical full migration window for organizations with moderate-to-complex PWA estates — including discovery, decision, build, change management, and parallel running. Most underestimate the change-management portion.

    — Forrester / Gartner PPM migration practice notes
  3. ~30%

    Of PWA estates we've seen contain custom workflows or integrations the original IT team no longer fully understands. Discovery is mandatory; surprise is expensive.

    — Platine practice observation
§ 07 · QUESTIONS

What buyers actually ask.

01 How do I get my data out of Project Online before retirement? +
Microsoft provides export tools and the Project Online Connector. We recommend a structured archive: project schedules to MPP, resource master to CSV, custom-list data to Excel, and a one-time SharePoint full-site backup. Don't leave this to the last week — the export volume can throttle for large estates.
02 Can we keep our custom PWA workflows? +
Most won't survive intact. Custom SharePoint workflows are tied to the platform that's being retired. The honest answer is: catalogue them in discovery, decide which earn redesign, and rebuild the survivors in Power Automate or the target platform. Some shouldn't be rebuilt at all — they were workarounds for old PWA limitations the new platforms solve natively.
03 What if we already use Asana or Smartsheet for tasks? +
That probably tells you the answer. If a third-party tool already does the task-tracking work that mattered, the Project Online migration is partly an opportunity to consolidate. Path C (third-party PPM) or Path D (lightweight Microsoft-native) usually wins. We map this honestly in Phase 02.
04 Are Microsoft license refunds available for Project Online? +
Generally no — Microsoft retirement is announced with sufficient notice that licenses run out their term. The conversation is about future license allocation, not refund. Project Operations carries a higher per-user cost than Project Online; Project for the Web is lower; third-party paths shift cost out of the Microsoft envelope.
05 How long do we really have? +
Microsoft has published the deprecation schedule. Read-only mode and full retirement happen on specified dates. The honest answer: you have less time than you think, because change management and parallel running take longer than the technical migration. Organizations starting today are running the right pace; organizations starting six months out will compress unfairly.
06 Can we run two systems in parallel during transition? +
Yes, and we recommend it for any non-trivial estate. New projects open in the target system on a cutover date; in-flight projects finish on Project Online. Resource masters need to be kept synchronized during the parallel period. Plan 8–12 weeks of parallel operation for moderate complexity.
07 Who decides which migration path is right? +
You do — based on the diagnostic. Our job is to surface the trade-offs honestly: cost over 3 years, change-management impact on operators, integration debt with the rest of your estate, lock-in risk. Many organizations expect a Microsoft-native answer and end up choosing a third-party tool because it fits the actual project culture better. The data decides.
§ — INTERROGATIVE

Project Online retires on a date.
Start with the diagnosis.

Schedule
→ Book a 30-minute readiness call
Phone
514-546-0711
Email
[email protected]
Related
→ Enterprise Systems Integration