Project Online End-of-Life Migration: To Power Platform PPM (Step-by-Step Enterprise Playbook)

TL;DR

• Microsoft Project Online is on a published end-of-life trajectory. Enterprises running Project Online face a migration decision: to the modern Microsoft 365 PPM stack (Project for the Web + Power Apps + Dataverse + Power BI), to a non-Microsoft PPM platform, or to a custom Power Platform implementation.
• For most enterprises, the Microsoft 365 PPM stack is the right target — it preserves the Microsoft platform investment and provides modern capabilities (Project Copilot, Power BI integration, Microsoft Loop coordination) the legacy stack cannot match.
• The migration spans four dimensions: data migration, customization migration, integration migration, and adoption migration. Each requires deliberate planning.
• The typical Fortune 500 migration is 30–34 weeks depending on Project Online customization depth and active project count.
• This guide details the step-by-step playbook and the EPC Group implementation framework.

Executive Summary

For 15 years, Microsoft Project Server and its successor Microsoft Project Online powered enterprise PMOs. The architecture — SharePoint as the data layer, Project Web App as the user interface, Project Professional desktop as the planning tool — was the dominant pattern. Microsoft's strategic shift to the Power Platform retired this architecture in favor of Project for the Web + Power Apps + Dataverse + Power BI.

For enterprises running Project Online, the migration is the dominant 2026 PMO project. This guide details the playbook.

The Migration Dimensions

Dimension 1: Data Migration

Project Online data lives in SharePoint lists and the Project Server Reporting database. The data migration:

1. Inventory the source data — projects, tasks, resources, custom fields, project sites, project workflows.
2. Schema mapping to Dataverse — standard mappings documented by Microsoft; custom fields require explicit mapping.
3. Extract project, task, assignment, resource, and custom field data into a staging environment.
4. Transform — ID remapping, lookup resolution, date format normalization, calculated field rebuilds.
5. Load to Dataverse via the Web API or bulk-import tools.
6. Validate — comparison reports verifying data integrity.

For hundreds of active projects, the data migration is typically 4–8 weeks of dedicated work.

Dimension 2: Customization Migration

Project Online customizations — custom fields, custom workflows, custom event handlers, custom Project Web App pages — do not migrate as-is. Each customization requires a rebuild on the Power Platform.

EPC Group's customization migration pattern:

1. Inventory all customizations.
2. Classify each as Keep / Rebuild / Retire.
3. Design the new-state customization on Power Platform.
4. Build in Power Apps and Power Automate.
5. Validate against the original customization's purpose.

The classification step is critical. Many Project Online customizations accumulated over years are no longer needed and should be retired rather than rebuilt.

Dimension 3: Integration Migration

Project Online integrations — connections to financial systems, HR systems, time tracking, document management — do not migrate as-is. Each integration requires a rebuild.

The integration rebuild leverages Power Automate, Azure Logic Apps, or Microsoft Fabric Data Factory depending on the integration pattern.

Dimension 4: Adoption Migration

Project for the Web is a different user experience from Project Web App. Project managers who have spent years in PWA need training and adoption support to be productive in the new surface.

The adoption migration runs in parallel with the technical migration: pilot a business unit, train, refine, expand.

Step-by-Step Playbook

Stage 1: Pre-Migration Planning (Weeks 1–4)

• Project Online tenant assessment.
• Customization inventory.
• Integration inventory.
• Active project inventory.
• Data quality assessment.
• Target architecture design.
• Migration roadmap with sequencing.

Stage 2: Foundation (Weeks 5–10)

• Microsoft 365 PPM target tenant provisioning (typically a dedicated Dataverse environment).
• Standard PPM solution deployment.
• Custom Dataverse table design.
• Security role design.
• CI/CD pipeline for Power Apps and Power Automate.

Stage 3: Customization Build (Weeks 11–18)

• Project intake Power App.
• Stage-gate Power Automate workflows.
• Custom field mapping in Dataverse.
• Resource capacity management Power Apps (if applicable).
• Document management integration.

Stage 4: Integration Build (Weeks 19–22)

• Financial system integration.
• HR system integration.
• Time tracking integration.
• Other integrations specific to the enterprise.

Stage 5: Power BI Build (Weeks 23–26)

• Power BI semantic model on Dataverse.
• Portfolio dashboard suite.
• Replacement of Project Online reporting.

Stage 6: Data Migration (Weeks 27–30)

• Extract from Project Online.
• Transform and load to Dataverse.
• Validation.

Stage 7: Cutover and Adoption (Weeks 31–34)

• Pilot business unit cutover.
• Training delivery.
• Broader rollout.
• Project Online tenant decommissioning planning.

The 34-week pattern is for a Fortune 500 enterprise with hundreds of active projects and substantial customization. Smaller enterprises run shorter.

Cutover Patterns

Pattern A: Big-Bang Cutover

All active projects migrate on a single cutover date. The pattern is appropriate when:

• Active project count is modest (under 100).
• Customization is minimal.
• The team can support concurrent legacy and new operations for a brief overlap.

Pattern B: Phased Cutover

Active projects migrate in waves by business unit or project type. The pattern is appropriate for:

• Larger active project counts.
• Complex customization.
• Phased adoption support requirements.

EPC Group's typical Fortune 500 pattern is Pattern B — phased cutover by business unit over 4–8 weeks.

Pattern C: New Projects on New Stack Only

Active Project Online projects remain in Project Online to completion; new projects start on Microsoft 365 PPM. This pattern eventually decommissions Project Online as the legacy projects close. The pattern is appropriate when:

• Project Online tenant remains supported through the active projects' completion.
• The adoption team prefers no in-flight project disruption.

Common Pitfalls

1. Trying to migrate every customization 1:1. Many customizations are no longer needed; use the migration as simplification.
2. Skipping the data quality assessment. Source data quality issues cascade into the new platform.
3. Under-investing in user adoption. Project for the Web is a different experience; training matters.
4. Forgetting Project Professional desktop. Some users have built habits around the desktop client; the transition needs deliberate attention.
5. Treating the migration as a single project. The four dimensions (data, customization, integration, adoption) are parallel workstreams, not sequential steps.
6. Not planning the Project Online decommissioning. Decommissioning includes tenant offboarding, license cancellation, and audit retention.

Frequently Asked Questions

When does Microsoft Project Online reach end of life?

Microsoft has placed Project Online on a published end-of-life trajectory. Specific end-of-support dates are documented in the Microsoft 365 service description. Verify the current dates against Microsoft documentation for your tenant's planning.

Why migrate to Microsoft 365 PPM rather than a non-Microsoft PPM?

For enterprises with Microsoft investments, the Microsoft 365 PPM stack preserves the platform investment and provides modern capabilities (Project Copilot, Power BI integration, Microsoft Loop coordination) the legacy stack cannot match. Non-Microsoft PPM may be appropriate for enterprises pivoting away from Microsoft.

What is the typical migration timeline?

For a Fortune 500 enterprise with hundreds of active projects and substantial customization, 30–34 weeks. Smaller enterprises run shorter. Greenfield implementations without Project Online migration run 20 weeks.

Can I migrate Project Online templates?

Project Online project templates do not migrate as-is. Equivalent templates are configured in the new stack via standard Project for the Web templates plus Power Apps configurations.

What happens to my Project Professional desktop client?

Project Professional desktop remains available for users who prefer it (Project Plan 5 license includes the desktop). The data backing the desktop in the new stack is Project for the Web / Dataverse, not Project Online.

How does the migration affect resource management?

Resource pool data migrates from Project Online to Dataverse. The resource management capabilities in the new stack are typically delivered through Power Apps PPM (separate from Project for the Web's task-level assignment).

Can I migrate Project Online project sites?

Project Online project sites (SharePoint-based) typically migrate to SharePoint Online team sites associated with Microsoft 365 PPM projects. The migration pattern depends on the site customization depth.

What is the data migration tooling?

Microsoft provides documented migration patterns; specific tooling includes Power Automate for scheduled extracts, the Dataverse Web API for bulk loads, and custom Power Platform solutions for transformation logic.

How do I handle customizations that depend on Project Server APIs?

Project Server API customizations require rebuild on Power Platform APIs. The rebuild is typically through Power Apps and Power Automate. Some customizations may use Azure Functions or custom code where the Power Platform pattern doesn't fit.

What about Project Online integrations with non-Microsoft systems?

Integrations rebuild on Power Automate, Logic Apps, or Microsoft Fabric Data Factory depending on the integration pattern. The new integrations typically run faster and are easier to maintain than the Project Online versions.

How does the migration affect reporting?

Project Online reporting (typically Power BI on ODATA feeds) migrates to Power BI on Dataverse. The semantic model is rebuilt; the reports may need refinement. The migration is often a reporting modernization opportunity.

Can I keep Project Online for some projects while migrating others?

Yes. The Pattern C "new projects on new stack only" approach keeps active Project Online projects in Project Online to completion while new projects start on Microsoft 365 PPM. Project Online decommissions when the legacy projects close.

What is the licensing transition?

Project Online subscriptions transition to Project Plan 1, 3, or 5 in Microsoft 365 based on user role. Some users may consolidate licenses; verify against your Microsoft licensing.

How does EPC Group support Project Online migrations?

EPC Group works with Fortune 500 enterprises on Project Online to Microsoft 365 PPM migrations. The standard 30–34 week engagement covers all four dimensions (data, customization, integration, adoption). Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct Project Online migration experience.

What is the typical Project Online tenant decommissioning timeline?

Decommissioning includes tenant offboarding from Project Online, license cancellation, and audit retention. The technical decommissioning is typically 2–4 weeks; the contract-level decommissioning aligns to the Project Online subscription renewal calendar.

Next Steps

If your enterprise is running Project Online and approaching the end-of-life trajectory:

1. Review Microsoft's published end-of-support timeline.
2. Inventory current Project Online customizations.
3. Classify customizations as Keep / Rebuild / Retire.
4. Plan the 30–34 week migration with phased cutover.
5. Engage a partner with deep Project Online migration experience.

EPC Group has been delivering enterprise Microsoft consulting since 1997 — in its 30th year — and is Microsoft Solutions Partner with the core designations. We were historically the oldest continuous Microsoft Gold Partner in North America through the program's retirement. Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct Project Online migration experience across Fortune 500 enterprises. To discuss your Project Online migration, contact EPC Group for a 30-minute discovery call.