PSSE is Microsoft’s on-premises enterprise PPM option for organizations that need close continuity with Project Online capabilities—advanced scheduling, resource management, timesheets, and governed PWA processes—built on SharePoint Server Subscription Edition.

It’s often chosen when regulatory, data residency, integration complexity, or operational control makes cloud-only tooling impractical.

When PSSE is a good fit:

• You need Project Online-like PPM with strong scheduling + enterprise controls.
  
  
• You rely on resource management, timesheets, enterprise calendars, and governed project lifecycle.
  
  
• You need PWA features: custom fields, workflows, approvals, portfolio views, and reporting DB access.
  
  
• You require platform control (on-prem or hosted), predictable change windows, and controlled upgrades.

Microsoft has announced that Project Online will retire on September 30, 2026, with end of sale for Project Online‑only SKUs to new customers on October 1, 2025. We help organizations migrate to PSSE in a controlled way—preserving governance, reporting continuity, and delivery cadence.

To ensure a controlled transition, we usually deliver the following:

• Assessment of your Project Online footprint (PWA config, workflows, fields, security, custom solutions, reporting).

• Target-state design in PSSE (PWA architecture, EPTs, templates, workflows, environments).

• Data & configuration mapping (projects, resources, timesheets, metadata, custom fields, lookups, calendars).

• Reporting continuity plan (Reporting DB access, KPI mapping, validation checkpoints).

• Pilot + migration waves with cutover runbook, go-live support, and rollback plan.

Implementation approach

Step 1 — Discover & Align (2–10 days)
Assess your Project Online / Project Server current state, align on PSSE outcomes, define pilot scope, risks and priorities.

Step 2 — Design, Configure & Integrate
Design PWA structure (templates, EPTs, custom fields), governance rules, permissions and metadata, and configure the required integrations (identity, reporting, Power Platform/LOB) to reduce manual work.

Step 3 — Pilot, Validate & Refine
Run with real teams, validate scheduling, timesheets and reporting signals (KPIs), and decide what should be standardized vs. left flexible.

Step 4 — Roll Out in Waves
Roll out in controlled waves with cutover runbooks, clear adoption targets, feedback loops and change management support.

Choose a focused starter or a full rollout—each engagement is scoped around clear deliverables and measurable outcomes.

Engagement options:

• Discovery & PSSE Assessment (2–10 days)
  Fast alignment on outcomes, current state of your Project Online / Project Server environment, target approach in Project Server Subscription Edition (PSSE), and a prioritized implementation and migration roadmap.
  
  
• PSSE Design & Quick Start (2–4 weeks)
  Design and configuration of a core PSSE PWA environment: enterprise templates, governance rules, custom fields and views, plus initial reporting, delivered with one or two pilot teams.
  
  
• PSSE Rollout Waves (4–12+ weeks)
  Scaled rollout of PSSE across teams, with adoption enablement, training, and reporting consistency checks, and with adjustments to templates and governance based on real usage.
  
  
• Project Online to PSSE Migration (3–8+ weeks)
  End‑to‑end migration from Project Online to PSSE: analysis and mapping, migration of selected projects, resources and timesheet data where feasible, validation with key users, and handover into your steady‑state PSSE setup.