You made it.
Project Online is behind you. Your projects are in Project Server Subscription Edition (PS-SE), your users can get to their work, and the migration that consumed more meetings, planning, testing, and troubleshooting than anyone probably wanted is finally done.
Take the win.
But once the dust settles, a different question starts to emerge:
Now what?
For many organizations who migrated to PS-SE it was first and foremost a continuity decision. It provided a familiar Project Web App experience and allowed organizations to preserve many of the processes, configurations, and ways of working they had built around Project Online.
That familiarity was one of its biggest advantages during a time-sensitive transition.
It can also make it very easy to assume the work is finished.
Migration gets you from one environment to another. It doesn’t necessarily tell you whether everything you brought with you still belongs there, whether your new environment is being managed effectively, or whether PS-SE is where your organization ultimately wants to stay.
Now that the deadline is behind you, you have something you probably didn’t have much of during the migration: room to think beyond the migration itself.
First, Make Sure Everything Actually Works
A successful migration and a successful working environment aren’t quite the same thing.
Testing can tell you whether projects moved, users can connect, and critical functionality is available. Day-to-day use tends to uncover the rest.
As teams settle into PS-SE, you may begin finding smaller issues that weren’t obvious during migration. Reports may not behave exactly as expected. Permissions may need adjustment. Integrations may require additional work. Data may need cleanup. Performance issues may appear under normal workloads.
Custom integrations deserve particular attention. In discussions among organizations preparing for PS-SE, maintaining existing integrations in the future environment has emerged as one of the more complicated parts of the transition.
None of that necessarily means the migration went badly.
It means your organization has moved from migration mode into stabilization mode.
This is the time to pay attention to what users are reporting, validate the things that matter most to the business, and resolve the small issues before everyone develops new workarounds for them.
Because if there’s one thing users are remarkably good at, it’s inventing a workaround before IT knows there’s a problem.
Decide Who Owns PS-SE Now
This is one of the biggest changes organizations underestimate when moving from Project Online to PS-SE.
Project Online was a cloud service. With PS-SE, your organization has considerably more responsibility for the environment itself.
Project Server Subscription Edition is part of SharePoint Server Subscription Edition Enterprise, so its infrastructure and ongoing management are tied closely to your SharePoint environment.
That makes some previously behind-the-scenes responsibilities much more important.
Who is responsible for administration? Who monitors the environment? Who handles updates? Who troubleshoots Project Web App issues? Who owns backups and recovery? Who handles integrations and reporting when something changes?
Updates deserve particular attention. SharePoint Server Subscription Edition follows a continuous update model, with monthly Public Updates and Feature Updates released twice annually. Microsoft gives each Public Update build a one-year support window and requires organizations to remain on a supported build to receive support.
In other words, PS-SE isn’t something you migrate to and forget about.
For some organizations, the internal IT team will comfortably own those responsibilities. Others may have the capacity to handle infrastructure but not specialized Project Server administration. Still others may prefer outside support rather than maintaining deep PS-SE expertise internally.
There isn’t one right model.
There does need to be a model.
You Preserved What Worked. Now Decide What’s Still Worth Preserving.
One of the reasons PS-SE made sense for many Project Online customers was that they didn’t have to reinvent their entire project management environment while racing a retirement deadline.
Custom fields, Project Web App configurations, reporting requirements, governance processes, security models, and other familiar structures could continue to play a role in the new environment. Microsoft documentation, for example, confirms that enterprise custom fields remain available in PS-SE, helping organizations standardize how information is captured across projects, tasks, resources, and assignments.
That’s valuable.
But familiarity has a downside.
If your Project Online environment accumulated ten years of custom fields, workflows, templates, reports, exceptions, workarounds, and “we’ve always done it this way” processes, migration may have preserved some things you wouldn’t choose to build today.
And that’s okay.
During a deadline-driven migration, the right question may have been:
What do we need to preserve to keep the organization running?
Now you can ask:
What do we actually need?
Maybe you’re maintaining fields nobody uses anymore.
Maybe a reporting process exists because of a limitation that no longer applies.
Or maybe your environment is working beautifully and very little needs to change.
The point isn’t to clean things up simply for the sake of cleaning them up. It’s to look at your environment intentionally instead of assuming everything deserves to survive because it existed before.
Revisit the Decisions You Made Under Deadline Pressure
The Project Online retirement date created a very real constraint.
Organizations had to evaluate options, develop migration plans, test environments, move data, train users, and keep normal business running at the same time.
Not every decision could become a six-month transformation initiative.
Some organizations deliberately chose the option that allowed them to maintain continuity and revisit larger questions later.
Later is here.
Think back to the decisions that were intentionally deferred.
Were there workflows you migrated knowing you wanted to redesign them eventually?
Reports you recreated because there wasn’t time to rethink them?
Integrations you kept because replacing them would have expanded the migration scope?
Those items don’t have to become immediate projects now either. But they shouldn’t disappear back into the organizational background simply because the migration is complete.
Create the list.
Then decide what is actually worth fixing.
Is PS-SE Your Destination or Your Bridge?
There’s one larger question worth asking once the urgency of migration is gone:
If you were choosing your project and work management environment today, without a retirement deadline hanging over the decision, would you make the same choice?
The answer may absolutely be yes.
For organizations that need the capabilities, control, architecture, or familiar PWA experience PS-SE provides, it can be a legitimate long-term destination.
If that’s you, the next phase is about making PS-SE better: stabilizing the environment, simplifying processes, improving reporting, strengthening governance, supporting users, and maintaining the platform.
But PS-SE can also serve another purpose.
It can be a bridge.
Your organization may have chosen PS-SE because it provided the safest path away from Project Online without forcing you to simultaneously redesign years of project management processes.
Now you have the luxury of separating two decisions that previously had to happen at once:
Where did we need to go to get off Project Online?
and
Where do we ultimately want to go?
Those answers don’t have to be the same.
If PS-SE isn’t your long-term destination, that doesn’t mean the migration was a mistake. It may have given your organization exactly what it needed: continuity, breathing room, and time to properly evaluate what comes next.
That could mean exploring Planner Premium and Power Platform, another Microsoft solution, a third-party platform, or something outside the Microsoft ecosystem entirely.
This time, you can start with your requirements instead of your deadline.
Migration Was the Milestone, Not Necessarily the Finish Line
For the past year, the Project Online retirement date gave organizations a very clear objective: get somewhere else before September 30, 2026.
If you successfully migrated to PS-SE, you accomplished that objective.
What happens next doesn’t need the same urgency.
You don’t have to redesign every process, replace every report, or decide your five-year technology strategy tomorrow.
But you do have an opportunity.
- Stabilize what you migrated.
- Make sure someone owns the environment.
- Clean up the things that no longer serve you.
- Fix the processes people have been working around.
- And when you’re ready, decide whether PS-SE is the environment you want to continue investing in or the place that gave you enough time to thoughtfully choose your next one.
Getting off Project Online was a milestone. Now you can focus on making what comes next actually work for your organization.
Need Help with What Comes Next?
Whether you’re still stabilizing your PS-SE environment, need ongoing technical support, want to clean up the processes you carried over from Project Online, or are starting to question whether PS-SE is your long-term destination, you don’t have to figure out the next phase alone.
We can help you assess where things stand, identify what needs attention now, and build a practical path forward based on how your organization actually works.
Ready to talk about what’s next? Contact Advisicon to start the conversation.
