Project Online Retirement Consulting & Migration

Microsoft ended sales of Project Online-only SKUs to new customers on October 1, 2025. Existing customers can continue using supported Project Online environments until the September 30, 2026 retirement date.

After the retirement date, users will no longer be able to access their projects or associated Project Online data within the service. Important operational and historical information should therefore be migrated, exported or archived in a usable format before shutdown.

As of April 1, 2026, Microsoft blocked creation of new Project Online PWA site collections. It also blocked Project Online access for tenants that did not contain at least one project across any existing PWA site. Organizations must therefore plan from their current environment rather than assume that a new Project Online instance can be created for transition work.

SharePoint 2013 workflows were fully retired in SharePoint Online on April 2, 2026. If a Project Online environment relied on that workflow engine for project creation, approvals, stage gates or notifications, those processes require separate attention now.

Organizations should identify what must remain operational, what can be retained for reference and what can be retired. This includes project schedules, baselines, enterprise custom fields, resources, timesheets, project-site content, reports, workflows, integrations and security rules. The assessment should determine whether each site, subsite, list or library resides inside the PWA site collection or in an independent SharePoint site collection.

This may include the Project Online inventory, stakeholder and requirements summary, data-quality findings, dependency register and identified retirement risks.

Decision materials may include a feature-gap matrix, replacement-platform comparison, recommended migration path, target solution architecture and licensing considerations. Assumptions, constraints and items requiring proof-of-concept validation are recorded clearly.

We can provide data-mapping rules, transformation logic, archive decisions, pilot results, exception logs, reconciliation evidence and user-acceptance records. Where information is archived rather than migrated, the archive design may include searchable schedule records, preserved identifiers and relationships, a data dictionary, retention controls, and a supported viewing or reporting mechanism.

Cutover materials may include the migration schedule, responsibility matrix, communication plan, validation checklist, rollback criteria and issue-escalation process. Administrator documentation explains the future environment, ownership and recurring support tasks.

Role-based user materials, administrator guidance and a post-launch support plan help the organization move from implementation into stable operation.

Microsoft Project Online will officially retire on September 30, 2026. Customers can continue using it until then, but access will end afterward. Organizations should complete migration, reporting changes, workflow updates and user training before the deadline. September 30 is the end of service—not the start of planning.

After retirement, Project Online data will no longer be accessible. This includes schedules, resources, assignments, reports and historical records. All required data should be migrated, exported or archived in advance. Organizations should also validate that exported data is complete and usable.

The Project Online-hosted Project Web App experience will become unavailable when Project Online retires. PWA remains available as part of the separately deployed Project Server Subscription Edition platform.

There is no single replacement for all environments. Microsoft is investing in Planner and its premium capabilities, but organizations with advanced governance, resource, reporting, financial or integration requirements may need Power Platform extensions or another PPM solution.

Start by documenting what Project Online currently supports, including scheduling, reporting, resource management, workflows and integrations. Then evaluate replacement options based on functionality, customization effort, integration needs, cost, security and long-term support. A proof of concept is often the most reliable way to decide.

Not always. Planner Premium supports core project tracking features like timelines, dependencies and portfolio views, which work well for many teams. However, it may not cover advanced PMO needs such as complex governance, financial tracking, enterprise workflows or deep reporting without additional tools.

Schedules, tasks, dates, dependencies and selected task-level fields may be transferable, depending on the migration tool and plan limits. Native .mpp import does not preserve resources or several advanced scheduling objects, so resource assignments and other unsupported data may require separate migration or recreation.

Items that may be migratable, depending on the destination platform, migration tooling and required fidelity, include projects, tasks, schedules, resources, assignments, selected custom fields, baselines and some documents or history.

They usually need to be rebuilt rather than migrated. Each workflow or integration should be reviewed and mapped to modern tools like Power Automate or APIs. SharePoint 2013 workflows are no longer supported in SharePoint Online, so affected workflows must be replaced.

Power BI datasets, Excel queries and other reports that refresh from Project Online endpoints will no longer be able to retrieve new source data after retirement. Report files and previously imported data may remain available if stored elsewhere, but their connections, semantic models, credentials, refresh schedules and security rules must be redirected and validated.

No. Many organizations archive completed projects instead of migrating them into the new system. A common approach is to migrate active projects and archive older history, but the cutoff should be based on operational, reporting, legal, contractual and retention requirements.

Yes. A phased transition may use Project Online as the source system only until its retirement. During any coexistence period, ownership and update rules must prevent conflicting changes between Project Online and the target platform.

Timelines vary widely. Simple environments may take weeks, while complex enterprise setups can take several months. Factors include integrations, customizations, data quality, testing and training. A readiness assessment provides the most accurate estimate.

Costs depend on environment size, complexity and target solution. Key drivers include number of projects, custom configuration, integrations, reporting needs, licensing and training. A focused archive engagement may cost less than a full platform replacement; scope and retention needs determine the effort.

Immediately. The first step is to inventory the current environment, including projects, workflows, reports, integrations and data requirements. Then define business needs, evaluate replacement options and run a pilot migration. If time is limited, prioritize securing and exporting critical data first.