Project Online to Project Server Migration Services

Move from Microsoft Project Online and Project Web App (PWA) to Project Server Subscription Edition with expert migration planning and support. With Project Online retiring on September 30, 2026, Bsuite365 helps assess your current environment, define what can be migrated, rebuilt, archived, or redesigned, and validate the new platform before go-live.

Need help choosing the right path?

TRUSTED BY

goverment-of-canada
Alberta-government
ocwa

Direct Answer

Microsoft Project Online is being retired on September 30, 2026. Organizations using Project Web App / PWA should review their project schedules, custom fields, resources, workflows, reports, permissions, and integrations before choosing a replacement. For teams that need a familiar PWA-style experience, Project Server Subscription Edition can be a strong migration path. For teams that want a modern Microsoft 365 and Teams-first experience, Planner Premium, Power Platform, or a hybrid model may be a better option.

⬤ Official Microsoft Partner

Bsuite365 logo

Microsoft 365 automation specialists

BSuite365, a division of BSUPERIOR SYSTEM LTD, is proud to be a Microsoft Official Partner. We help businesses get more from Microsoft 365 through automation, Excel consulting, and streamlined workflow solutions that improve productivity.

What Is a Project Online to Project Server SE Migration?

Project Online to Project Server Subscription Edition migration is the process of assessing an existing Project Online / PWA environment, identifying projects, resources, custom fields, workflows, reports, project sites, permissions, and integrations, and moving or rebuilding the required components in a new Project Server SE environment.

Our Clients

goverment-of-canada
ocwa
the-jim-pattison-group
ch-groupe
isovolta-group
eureka-comions-lague
westcoast-robotics
weaver-group-limited
summit fine wines
klein-group
perephone-brewing
bureau-veritas
kanaweyimik-child

Migration Support Includes

Our migration services cover the key areas needed for a successful transition from Project Online to Project Server Subscription Edition.

  • We review your current Project Online setup and define a practical migration path.

  • We help plan and configure the Project Server SE environment.

  • We assess infrastructure, hosting, authentication, database, and security needs.

  • We review reports, dashboards, data models, and reporting connections.

  • We support testing, validation, go-live, and post-migration issue resolution.

Why Organizations Are Migrating from Project Online

Organizations are migrating from Project Online for several important reasons:

Project Online Retirement

Microsoft Project Online is scheduled to retire on September 30, 2026, creating a deadline for organizations to plan their next steps.

Risk Reduction

Delaying migration can increase risks related to data access, reporting continuity, user adoption, and project delivery timelines.

Opportunity to Modernize

Migration provides an opportunity to clean up outdated configurations and evaluate modern alternatives such as Planner Premium or Power Platform solutions.

Reporting and Data Continuity

Project Online often supports Power BI dashboards, reports, and executive reporting. Migration planning helps ensure continued access to historical data.

Infrastructure Planning Requirements

Organizations choosing Project Server Subscription Edition need time to prepare supporting infrastructure and licensing such as SharePoint Server Subscription Edition Enterprise.

Business-Critical Project Management Processes

Many organizations use Project Online and Project Web App (PWA) for governance processes that must continue without disruption.

Project Server SE vs Planner Premium / Power Platform

Project Server Subscription Edition suits organizations that want a familiar Project Web App experience. However, Planner Premium is not a direct PWA replacement. It should be assessed carefully where organizations depend on enterprise resource management.

Choose Project Server SE If You Need

  • Familiar Project Web App style experience
  • Portfolio governance and stage-gate processes
  • Enterprise schedules with Microsoft Project Professional
  • Enterprise resource pool and capacity planning
  • On-premises, Azure, or customer-controlled infrastructure
  • Complex custom fields, reporting, and PWA configuration

VS

Consider Planner Premium / Power Platform If You Need

  • Modern Microsoft 365 / Teams-first work management
  • Lightweight project and task management
  • Modern Power Platform extensibility
  • Simpler team collaboration
  • Cloud-native Microsoft 365 experience
  • Lower infrastructure management

What Can Be Included in a Project Online to Project Server Migration?

A Project Online migration can include more than project schedules.

Project schedules

Active projects, baselines, dependencies, calendars, task structures, and project metadata.

PWA configuration

Enterprise custom fields, lookup tables, views, security categories, and Project Web App settings.

Resource management

Enterprise resource pool, roles, rates, capacity planning data, and resource assignments.

Timesheets and task updates

Timesheet processes, approvals, task update workflows, and related governance rules.

Project sites

SharePoint project sites, documents, risks, issues, deliverables, and site templates.

Workflows

Demand management, stage-gate approvals, project intake, and workflow logic.

Reporting

Power BI reports, OData connections, dashboards, data models, reporting datasets, and reports that may need to be repointed or rebuilt for the new platform.

Permissions

Groups, categories, project access, admin permissions, and security rules.

Integrations

Power Automate flows, SharePoint, Excel, ERP, CRM, and third-party tool connections.

Historical data

Archived projects, completed projects, reporting-only records, and data retention needs.

Book a Project Online Migration Assessment

Let us review your Project Online environment and identify what should be migrated, rebuilt, archived, or modernized.

free consultation

What Does Not Migrate Automatically?

We take a comprehensive approach, carefully considering every component to ensure it is appropriately aligned for optimal performance in the new environment.

OData-based Power BI reports

Reports built in Project Online using OData connections often depend on specific data structures. As a result, these reports typically need to be redesigned to align with the new reporting architecture.

Some workflows

Complex workflows are often tightly integrated with Project Online features. These workflows may not transfer directly and usually require rebuilding.

Custom integrations

Integrations with systems are often customized to the Project Online environment. These connections may break or behave differently after migration.

Permission models

Security configurations are structured differently across environments. These settings rarely migrate cleanly and must be reviewed and validated.

Project sites and SharePoint customization

Project sites often contain custom SharePoint components that are deeply embedded in the existing environment. Migrating these elements requires separate planning.

Historical and archived data

Older or completed projects may not need to be fully migrated into the new system. Instead, organizations often choose to retain this data for reporting purposes.

Custom reporting datasets

Custom-built reporting elements are typically tailored to Project Online’s data schema. These components often need to be rebuilt to align with the data structures.

Third-party add-ins

Add-ins and extensions used in Project Online may not be compatible with Project Server SE. Each add-in must be evaluated to determine whether it can be supported.

Our Project Online to Project Server Migration Process

Our migration process is designed to reduce risk, protect critical project data, and give business and technical stakeholders a clear path from planning to go-live. This should be treated as a platform transition, not a simple upgrade

1

Discovery and Environment Inventory

We review your Project Online and PWA environment, including project count, active and archived projects, custom fields, workflows, reports, project sites, permissions, integrations, and data volume.

2

Migration Strategy and Platform Recommendation

We confirm whether Project Server Subscription Edition, Planner Premium, Microsoft Power Platform, or a hybrid model is the best fit for your organization. This avoids forcing a migration path.

3

Target Architecture Design

We design the technical foundation for the new system, including servers, SharePoint, SQL Server, authentication, security, backups, and support responsibilities.

4

Data Mapping and Migration Planning

We define what will be migrated, transformed, archived, rebuilt, or excluded. This includes project schedules, enterprise custom fields, lookup tables, resources, permissions, and SharePoint project site content.

5

Pilot Migration

We migrate a sample set of projects and validate key areas such as schedules, resources, custom fields, permissions, reports, and project sites. Pilot testing helps find issues before production cutover.

6

Validation and User Acceptance Testing

We help confirm data accuracy, reporting continuity, user access, performance, and usability. This gives project managers, resource managers, and administrators confidence before go-live.

7

Post-Migration Validation Checklist

Before production cutover, the migrated environment should be validated by both technical and business users. This helps confirm that the new system is accurate, usable, secure, and ready for daily project management operations.

8

Production Cutover

We support the final migration, go-live process, issue resolution, and cutover coordination. The goal is to reduce disruption and help users continue working with minimal confusion.

9

Training and Post-Migration Support

We provide practical training for administrators, project managers, and reporting users. We can also prepare documentation, validation checklists, and post-migration support plans.

Manual vs Automated Project Online to Project Server Migration

The right migration approach depends on the size, complexity, and business importance of your Project Online environment.

Manual MPP export/import

✔ Best for

Small number of simple projects

⚠ Limitations

Does not fully handle complex PWA configuration, workflows, reporting, permissions, or project sites.

Tool-assisted migration

✔ Best for

Larger or more complex Project Online environments

⚠ Limitations

Requires technical planning, validation, governance, and careful testing.

Hybrid migration

✔ Best for

Organizations that want to clean up or modernize during migration

⚠ Limitations

Requires more discovery, stakeholder alignment, and migration decision-making.

Project Server Subscription Edition Hosting Options

Project Server Subscription Edition gives organizations more control over infrastructure and data, but it also requires proper planning and administration.

On-Premises Project Server SE

  • On-premises Project Server SE is best for organizations with existing infrastructure, internal IT governance, and strict data residency requirements. This option gives your organization direct control over servers.

Most Popular

Azure-Hosted Project Server SE

  • Azure-hosted Project Server SE can be considered when an organization wants to run the Project Server / SharePoint Server farm on customer-controlled Azure infrastructure. This is still a server-based deployment and requires planning for licensing.

Managed / Dedicated Hosting

  • Managed or dedicated hosting is best for organizations that want Project Server functionality without fully managing the infrastructure internally. This option can reduce internal IT workload.

Technical Dependencies to Plan

A successful Project Server Subscription Edition environment requires licensing and long-term administration responsibilities before migration. Itmay require planning for:

Windows Server

Server operating system requirements must be reviewed before deployment.

Backup and disaster recovery

Project data and reporting assets need a recovery plan.

Monitoring and maintenance

Updates, performance, storage, and service health need ongoing management.

SharePoint Server Subscription Edition Enterprise

Project Server SE is connected to SharePoint Server Subscription Edition Enterprise.

Authentication / Microsoft Entra ID planning

Authentication and identity planning, including Active Directory, SharePoint claims authentication and hybrid identity.

SQL Server and reporting components

Project Server databases and reporting depend on SQL Server planning. OLAP, Cube Building Service, or Portfolio Analysis may require additional SQL Server and SharePoint configuration.

When Project Server SE Is a Good Fit — and When It Is Not

A trustworthy migration plan should explain both sides. Project Server SE can be a strong option, but it is not always the best replacement for every Project Online customer.

Good Fit for Project Server SEBetter Alternative May Be
You need a familiar PWA-style experience.You want a modern Teams-first experience.
You rely on Project Desktop for detailed scheduling.Your projects are simpler and task-based.
You need enterprise resource management.You mainly need collaboration and basic timelines.
You need infrastructure and data control.You prefer SaaS with less infrastructure management.
You have complex PWA workflows and reporting.You are open to rebuilding on Power Platform.
You need structured PMO governance.You want lighter work management.
industry section bg 1

Project Online Environment Assessment

We review your current Project Online and PWA environment to understand how your teams work today. This helps identify important projects and processes that need to be considered during migration.

Migration Readiness Report

You receive a clear summary of migration risks, dependencies, and areas that may require attention. The report helps stakeholders understand what is needed for a smooth and successful transition.

Recommended Target Architecture

We provide recommendations for the future Project Server environment based on your needs. This gives your team a clear blueprint for infrastructure, security, performance, and scalability.

Migration Scope and Roadmap

We define exactly what should be migrated, archived, rebuilt, or improved. The roadmap provides a step-by-step plan, so everyone understands the migration journey.

Data and Configuration Mapping

We document where your existing projects, fields, resources, permissions, and reports should go in the new environment so important information is not lost or recreated incorrectly.

Pilot Migration Results

We perform a test migration and share the results with your team. This allows issues to be identified and resolved before the final production migration.

Validation Checklist

You receive a structured checklist to verify that all key data and functionality are working correctly. This helps build confidence that the new environment is ready for users.

Production Migration Plan

We create a detailed plan for the final migration and go-live activities. The plan helps minimize disruption and keeps stakeholders informed throughout the process.

Cutover Support

Our team provides hands-on assistance during the migration launch period. We help address questions and resolve issues quickly to support a smooth transition.

Admin and User Documentation

We provide easy-to-follow guides for administrators, project managers, and end users. This helps teams understand the new environment and work effectively from day one.

Post-Migration Support Plan

We outline the support available after migration to help with stabilization and improvements. This ensures your team has guidance as users adapt to the new platform and processes.

What You Receive from Our Migration Service

Our Project Online to Project Server migration service gives your team clear deliverables, practical recommendations, and technical support from assessment through cutover.

Get the Migration Readiness Checklist

Not sure which path is right? Request a Project Online migration assessment before choosing Project Server SE, Planner Premium, Power Platform, or a hybrid approach.

Why Choose Bsuite365 for Project Online to Project Server Migration?

We help organizations work with Microsoft 365, SharePoint, Power Platform, Excel, Power BI, SQL Server, workflow automation, and custom business applications.

Microsoft 365 and SharePoint Experience

We understand how Project Online connects with Microsoft 365 and SharePoint. We help maintain project sites, permissions, documents, and collaboration processes during migration.

Power Platform and Workflow Automation Knowledge

We review your current workflows and identify what should be moved, improved, or rebuilt.
We can help modernize approvals, notifications, and business processes using Power Platform tools.

Power BI and Reporting Support

We assess dashboards, reports, and reporting data sources before migration begins. This helps maintain reporting accuracy and visibility for your teams after go-live.

SQL Server and Data Awareness

We support database planning, data mapping, and migration preparation. Our team reviews reporting structures, storage needs, and data dependencies. Our approach helps protect data quality.

Support for Technical and Non-Technical Stakeholders

We work closely with IT teams, PMO leaders, project managers, and business stakeholders. Our experts explain technical topics in a clear and practical way. This helps keep everyone informed.

Practical Migration Advice

We help you decide what should be migrated, archived, rebuilt, or retired. This prevents unnecessary complexity from being carried into the new environment. Our recommendations focus on long-term usability.

FAQ

Microsoft Project Online is scheduled to retire on September 30, 2026.

No. Microsoft’s Project Online retirement applies to Project Online, not Project Server Subscription Edition. However, organizations should still review Project Server SE lifecycle, licensing, support, and infrastructure requirements as part of planning.

Yes, but it should be treated as a migration and redesign project rather than a simple upgrade. Project schedules, metadata, resources, permissions, sites, reports, and workflows must be assessed to determine what can be transferred, rebuilt, archived, or replaced.

A migration assessment reviews your projects, PWA configuration, custom fields, resources, permissions, workflows, reports, project sites, integrations, and data volume. It also identifies migration risks and recommends the best target platform.

Planner Premium may be better for teams that need modern Microsoft 365 collaboration, simpler project tracking, and less infrastructure management, but it should be assessed carefully if the organization depends on PWA governance, enterprise resource management, complex workflows, or advanced portfolio reporting.

Not always. Some data and configurations can be migrated, while complex workflows, reports, integrations, permissions, or historical data may need to be rebuilt, archived, or redesigned.

The main risks include missing data, broken reports, permission issues, workflow failures, integration gaps, project site problems, poor user adoption, and insufficient infrastructure planning.

Yes. Project Server Subscription Edition works with SharePoint Server Subscription Edition Enterprise and requires proper planning for SharePoint, SQL Server, Windows Server, authentication, backup, and maintenance.

Yes. Many organizations migrate only active or business-critical projects and archive older projects for reference, compliance, or reporting.

The timeline depends on the number of projects, configuration complexity, workflows, reports, integrations, project sites, and validation requirements. Simple migrations may be shorter, while complex enterprise environments usually require more planning and testing.

Contact us

Contact us today at – and speak with our specialist.