Microsoft Project Online Is Retiring: What Healthcare and Higher Ed Teams Need to Know
For hospital PMOs, healthcare IT teams, and higher education project managers using Microsoft Project Online: This guide explains what the September 2026 retirement means for your organization, what your options are, and how to evaluate alternatives without disrupting your current workflows.
Quick Answer: What’s Happening to Microsoft Project Online?
Microsoft Project Online will be permanently retired on September 30, 2026. After that date, you will lose access to all projects and data in the service.
| Milestone | Date | What It Means |
|---|---|---|
| End of sale for new licenses | October 1, 2025 | New organizations cannot purchase Project Online |
| No new tenants | April 2026 | Existing customers cannot create new Project Online environments |
| Service retirement | September 30, 2026 | Project Online stops working; all data becomes inaccessible |
What’s NOT retiring:
- Microsoft Project desktop application (standalone)
- Microsoft Planner
- Project Server Subscription Edition (on-premises)
What IS retiring:
- Project Online (cloud-based, SharePoint-hosted)
- Project for the Web (merged into Planner)
- Roadmap app in Microsoft Teams
The Announcement: What’s Actually Happening
Microsoft officially announced on September 5, 2025 that Project Online will be retired on September 30, 2026. After that date, you will no longer be able to access your projects or any associated data within the service.
Here’s the timeline:
- October 1, 2025: End of sale for new Project Online licenses
- April 2026: Existing customers can no longer create new tenants
- September 30, 2026: Project Online officially retires and data becomes inaccessible
This isn’t a rumor or speculation. It’s happening. And if you’re a hospital PMO tracking construction projects, an IT team managing EHR rollouts, or a university advancement office coordinating campaigns across departments, you need a plan.
Important clarification: The Microsoft Project desktop application is NOT being retired. This announcement specifically affects Project Online, the cloud-based service built on SharePoint architecture. If you’re using Project desktop as a standalone tool without Project Online, you’re not directly impacted. But if your team relies on Project Online for collaboration, reporting, or portfolio visibility, you have roughly eight months to migrate.
Why Microsoft Is Doing This
Microsoft’s reasoning comes down to architecture. Project Online was built on SharePoint, and that legacy foundation limits their ability to deliver modern, AI-powered experiences. Microsoft is investing instead in Planner (which now incorporates what used to be called “Project for the Web”) and the Power Platform.
The short version: Microsoft wants you to move to Planner Premium or build custom solutions on Power Apps. For some teams, that might work. For healthcare and higher education organizations with complex project portfolios, compliance requirements, and limited IT bandwidth, that path isn’t always realistic.
What IS retiring:
- Project Online (cloud-based, SharePoint-hosted)
- Project for the Web (merged into Planner)
- Roadmap app in Microsoft Teams
Why Microsoft Is Retiring Project Online
Microsoft stated that Project Online’s legacy SharePoint architecture limits their ability to deliver modern, AI-powered experiences. They’re shifting investment to:
- Planner Premium (formerly Project for the Web)
- Power Platform for custom project management solutions
- Copilot integration for AI-assisted project management
The practical implication: Microsoft wants you to either migrate to Planner Premium or build custom solutions on Power Apps. For many healthcare and higher ed teams, neither option is straightforward.
What This Means for Healthcare Teams
Hospital PMOs and healthcare IT departments face specific challenges that make this migration more complex than average:
Compliance and Regulatory Requirements
Every project touches regulatory requirements. Construction projects need Joint Commission consideration. IT implementations require HIPAA reviews. New service lines need compliance and legal sign-off. Your replacement tool needs to support these multi-step approval workflows.
Multi-Stakeholder Complexity
A single EHR rollout might involve clinical teams, IT, revenue integrity, compliance, training, and external vendors. You need a tool where all stakeholders can see their piece without requiring full licenses or extensive training.
Resource Constraints
Hospital IT teams are already stretched thin. You don’t have months to spend building custom Power Apps solutions or configuring complex platforms from scratch.
Continuous Operations
You can’t pause patient care during migration. Whatever you choose needs to run alongside existing workflows during transition.
Diverse Project Types
The same team might manage a capital campaign, website redesign, event logistics, and donor communications. You need flexibility without sacrificing structure.
What This Means for Higher Education Teams
University project teams face parallel challenges:
Decentralized Stakeholders
A single campaign might involve advancement, marketing, academic departments, athletics, and the foundation. You need visibility across all groups without forcing everyone onto the same complex tool.
Budget Cycles and Procurement
Higher ed procurement moves slowly. A typical software evaluation and approval process takes 3-6 months. If you need a new tool by September 2026, you should be starting evaluations now.
Diverse Project Types
The same team might manage a capital campaign, website redesign, event logistics, and donor communications. You need flexibility without sacrificing structure.
Why This Hits Healthcare and Higher Ed Differently
If you’re managing projects in a hospital or university, you already know that generic project management advice rarely applies to your world.
Healthcare Challenges
Hospital PMOs and IT teams face unique pressures that most project management tools weren’t designed to handle:
Compliance-driven workflows. Every project touches regulatory requirements. Construction projects need Joint Commission sign-off. IT implementations require HIPAA reviews. New service lines need compliance, legal, and physician approval before launch.
Multi-stakeholder complexity. A single EHR rollout might involve clinical teams, IT, revenue integrity, compliance, training, and external vendors. When Dawn Luebeck at Riverside Healthcare described her challenges with Microsoft Project, she put it simply: “Not everybody can see it. It’s not allocating or identifying resources accurately.”
Continuous operations. You can’t pause patient care while you migrate project management systems. Whatever you move to needs to work alongside existing workflows, not disrupt them.
Resource constraints. Hospital IT teams are already stretched thin. They don’t have months to spend configuring a new platform from scratch or building custom Power Apps solutions.
Higher Education Challenges
University project teams face their own version of these same pressures:
Decentralized stakeholders. A single campaign might involve advancement, marketing, academic departments, athletics, and the foundation. Getting visibility across all of those groups is nearly impossible with tools that weren’t built for cross-departmental collaboration.
Budget cycles and governance. Higher ed procurement moves slowly. If you need to make a change, you need to start the evaluation process now, not six months from now.
Diverse project types. The same team might manage a capital campaign, a website redesign, event logistics, and donor communications. You need flexibility without sacrificing structure.
At the University of Oklahoma Foundation, Bill Moakley described the challenge of scaling from 100 to nearly 300 employees after a major organizational change: “We couldn’t just operate off hallway conversations anymore.”
How to Evaluate Microsoft Project Alternatives
Use this framework to compare your options:
Must-Have Criteria Checklist
| Requirement | Questions to Ask | Why It Matters |
|---|---|---|
| Implementation timeline | How long does typical implementation take? | You have ~8 months; avoid tools requiring 6+ month implementations |
| Resource management | Can you see workload across multiple projects? | Critical for teams with shared resources |
| Portfolio visibility | Can leadership see status across all projects without manual reporting? | Eliminates Friday afternoon report scrambles |
| Stakeholder access | Can external collaborators participate without full licenses? | Essential for cross-departmental work |
| Approval workflows | Does it support multi-step approval routing? | Required for compliance-driven environments |
| Support model | Do you get humans or chatbots? What’s response time? | Healthcare and higher ed need responsive help |
| Industry experience | Do they have customers in healthcare/higher ed? | Vendors who understand your world implement faster |
Evaluation Scorecard Template
Rate each option 1-5 on these criteria:
| Criteria | Weight | Option A | Option B | Option C |
|---|---|---|---|---|
| Ease of adoption | 20% | |||
| Resource management | 15% | |||
| Portfolio visibility | 15% | |||
| Implementation timeline | 15% | |||
| Total cost (3-year) | 15% | |||
| Support quality | 10% | |||
| Industry fit | 10% | |||
| Weighted Total | 100% |
What Healthcare and Higher Ed Teams Actually Need
If you’re evaluating alternatives, here’s what matters most for healthcare and higher education project management:
Visibility Without Complexity
You need the 30,000-foot view that leadership keeps asking for, without spending hours pulling data from multiple systems. Portfolio views that show what’s in flight across departments, campuses, or service lines.
Micro-example: Your VP asks for a status update on all active IT projects. Instead of spending Friday afternoon compiling a report, you share a dashboard link and get on with your weekend.
Resource Allocation That Actually Works
Microsoft Project’s resource management was a common pain point in healthcare. “I have somebody slated to do something, doesn’t mean they can’t be doing something on multiple projects,” Dawn explained. “But according to Microsoft Project, it says you’ve exhausted all their time.”
You need resource views that reflect how work actually happens, where people contribute to multiple projects simultaneously and priorities shift weekly.
Structured Workflows Without IT Dependency
Healthcare and higher ed teams don’t have months to spend configuring workflows or building custom Power Apps. You need software that comes with structure out of the box, templates you can modify, and workflows that reflect how your team actually operates.
Collaboration Across Stakeholders
When a project involves clinical teams, IT, compliance, external vendors, and department chairs, you need a system where everyone can see their piece without needing extensive training or full licenses.
Support From People Who Understand Your World
When something breaks, you need a human who picks up the phone. Healthcare and higher ed teams don’t have time to submit support tickets that disappear into a void or troubleshoot software on their own.
90-Day Migration Action Plan
Days 1-30: Assessment and Requirements
Week 1: Audit Current State
- Document all active projects in Project Online
- List all users and their access levels
- Identify integrations (Power BI, SharePoint, etc.)
- Note custom workflows or configurations
- Calculate data volume (projects, tasks, files)
Week 2: Define Requirements
- Survey project managers on must-have features
- Survey stakeholders on reporting needs
- Document compliance/approval workflow requirements
- Identify pain points with current system (these guide your evaluation)
- Determine budget constraints
Week 3: Research Options
- Review Microsoft’s migration guidance for Planner Premium
- Research 3-5 alternative platforms
- Check vendor experience with healthcare/higher ed
- Request pricing from top candidates
- Read reviews from similar organizations
Week 4: Build Evaluation Team
- Identify key stakeholders for decision
- Schedule demo time with top 3 vendors
- Prepare evaluation scorecard
- Set decision deadline (end of Day 60)
Days 31-60: Evaluation and Selection
Week 5-6: Vendor Demos
- Complete demos with all vendors
- Ask vendors to show your specific use cases
- Request references from healthcare/higher ed customers
- Get detailed implementation timelines
- Clarify support model and response times
Week 7: Trial Period
- Set up trial accounts for top 2 candidates
- Test with actual project data (sample, not production)
- Have 3-5 team members test daily workflows
- Document friction points and questions
- Test reporting capabilities
Week 8: Decision and Procurement
- Complete evaluation scorecards
- Present recommendation to leadership
- Begin procurement/contracting process
- Set implementation start date
Days 61-90: Implementation Planning
Week 9-10: Implementation Prep
- Finalize contract and kickoff date
- Assign internal project lead
- Identify pilot group (1 team or department)
- Create data migration plan
- Schedule training sessions
Week 11-12: Pilot Launch
- Configure system for pilot group
- Migrate pilot group’s active projects
- Train pilot users
- Gather feedback daily during first week
- Document issues and solutions
Data Migration Checklist
Before September 30, 2026, you must export and migrate:
Critical Data to Export
- All project plans and schedules
- Task assignments and history
- Resource allocations
- Project documents and attachments
- Custom fields and metadata
- Reporting data and dashboards
- Timesheet data (if used)
Export Methods
| Data Type | Export Method | Format |
|---|---|---|
| Project plans | Project Online export or API | XML, Excel |
| Documents | SharePoint export | Native files |
| Reports | Power BI export | Excel, PDF |
| Custom data | API extraction | CSV, JSON |
Migration Validation
- Verify all projects transferred
- Confirm task counts match
- Check resource assignments
- Validate dates and dependencies
- Test reports against original data
Common Migration Mistakes to Avoid
Mistake 1: Waiting Too Long
The problem: Procurement in healthcare and higher ed takes 3-6 months. Implementation takes another 2-4 months. If you start in June 2026, you won’t make the deadline.
The fix: Begin evaluation now. Even if you don’t migrate until Q2 2026, you need a selected vendor and signed contract by Q1.
Mistake 2: Trying to Replicate Everything
The problem: Organizations try to recreate every custom workflow and configuration from Project Online. This extends implementation timelines and often recreates problems that existed in the old system.
The fix: Use migration as an opportunity to simplify. Ask “do we still need this?” before migrating each workflow.
Mistake 3: Underestimating Change Management
The problem: Teams focus on technical migration and forget that people need to learn new tools and processes.
The fix: Budget time for training. Identify power users who can support colleagues. Plan for productivity dip during transition.
Mistake 4: Ignoring Data Backup
The problem: Organizations assume they can export data later and discover issues when it’s too late.
The fix: Export critical data now, even if you haven’t selected a new tool. Store backups outside Project Online.
Mistake 5: Choosing Based on Features Alone
The problem: Teams select the tool with the longest feature list, then struggle with implementation and adoption.
The fix: Prioritize ease of adoption and implementation support. A simpler tool your team actually uses beats a complex tool they abandon.
Questions to Ask Vendors
About Implementation
- What’s your typical implementation timeline for healthcare/higher ed organizations?
- What does onboarding include? Is training additional cost?
- Who manages implementation – us or you?
- Can we pilot with one team before full rollout?
About Support
- What’s your average response time for support requests?
- Do we get a dedicated contact or general support queue?
- Is support included or additional cost?
- What hours is support available?
About Migration
- Do you have a migration path from Microsoft Project Online?
- What data can you import automatically vs. manually?
- How long does data migration typically take?
- Can we run both systems in parallel during transition?
About Fit
What do customers in our industry like most/least?
How many healthcare/higher ed customers do you have?
Can you show me an example configured for our use case?
What’s your customer retention rate?
A Realistic Migration Timeline
If you’re starting from scratch, here’s what a realistic timeline looks like:
Now through March 2026: Evaluate and Select
- Identify your must-have requirements
- Request demos from 2-3 alternatives
- Involve key stakeholders in evaluation
- Make a decision and get budget approval
April through June 2026: Plan and Pilot
- Work with your new vendor on implementation planning
- Migrate a pilot group or department first
- Refine workflows based on feedback
- Train power users who can support broader rollout
July through September 2026: Full Migration
- Roll out to remaining teams
- Export and archive Project Online data
- Ensure all active projects are transitioned
- Decommission Project Online before September 30
This timeline is tight. If your organization’s procurement process takes months (common in healthcare and higher ed), you need to start the evaluation phase immediately.
Questions to Ask When Evaluating Alternatives
When you’re comparing options, focus on these questions:
- How long does implementation typically take? If the answer is “months,” that may not fit your timeline.
- What does onboarding and training include? Do you get hands-on support, or are you pointed to documentation and left to figure it out?
- How does resource allocation work across multiple projects? Can you see who’s overloaded and who has capacity?
- What does reporting look like for leadership? Can you get the portfolio visibility your executives want without manual data compilation?
- Do you have experience with healthcare/higher education organizations? A vendor who understands your compliance requirements, stakeholder complexity, and budget cycles will be a better partner than one who treats you like any other customer.
- What happens when something breaks? Do you get a human, or do you get a chatbot?
Frequently Asked Questions
When does Microsoft Project Online retire?
Microsoft Project Online officially retires on September 30, 2026. After this date, you will no longer be able to access your projects or data within the service. New Project Online licenses stopped being sold on October 1, 2025, and existing customers cannot create new tenants after April 2026. Organizations currently using Project Online should begin migration planning immediately to ensure adequate time for evaluation, selection, implementation, and training before the deadline.
What are the best Microsoft Project Online alternatives for healthcare organizations?
The best Microsoft Project Online alternatives for healthcare organizations are purpose-built project management tools that offer: (1) multi-step approval workflows for compliance requirements, (2) resource management across multiple simultaneous projects, (3) stakeholder access that doesn’t require full licenses for occasional users, (4) responsive human support from teams familiar with healthcare environments, and (5) implementation timelines short enough to complete before the September 2026 deadline. Microsoft’s Planner Premium is an option for simple use cases, but healthcare PMOs with complex portfolios often need more robust solutions. Tools like Workzone, Wrike, and Smartsheet serve healthcare organizations, with varying levels of industry-specific features and support.
What are the best Microsoft Project Online alternatives for higher education?
The best Microsoft Project Online alternatives for higher education institutions are platforms that support: (1) cross-departmental collaboration between advancement, marketing, academic affairs, and administration, (2) flexible project types from campaigns to events to ongoing programs, (3) easy adoption for users who aren’t project management professionals, (4) procurement-friendly pricing and contracting, and (5) quick implementation that can complete within an academic calendar cycle. Higher ed teams should prioritize tools with existing higher education customers and support teams who understand university budget cycles and governance structures.
How long does it take to migrate from Microsoft Project Online?
A complete migration from Microsoft Project Online typically takes 3-6 months, depending on complexity. This includes: evaluation and vendor selection (4-8 weeks), procurement and contracting (2-8 weeks depending on organization), implementation and configuration (4-8 weeks), pilot testing (2-4 weeks), and full rollout with training (2-4 weeks). Healthcare and higher education organizations should add buffer time for procurement approvals and change management. To complete migration before September 30, 2026, organizations should begin vendor evaluation no later than Q1 2026, with Q4 2025 being ideal.
What happens to my data when Microsoft Project Online retires?
After September 30, 2026, all data in Microsoft Project Online will become inaccessible. Microsoft will not automatically migrate your data to another platform. You are responsible for exporting project plans, task history, documents, resource allocations, and reporting data before the retirement date. Microsoft recommends backing up data well in advance and completing migration to either Planner Premium or Project Server Subscription Edition before retirement. If you’re migrating to a non-Microsoft platform, you’ll need to export data and work with your new vendor on import processes.
Last updated on February 3, 2026
Want a Peak Inside Workzone?
Continue reading
