Microsoft Project Online Is Retiring. Here’s Your 5-Step Game Plan!
Project Online Is Retiring. Here’s Your 5-Step Game Plan.
Microsoft Project Online shuts down September 30, 2026. But the real deadline hits sooner: April 2, 2026, when SharePoint workflows powering your approvals, stage gates, and status reports are removed. If your PMO runs on those workflows, parts of your operation break six months early.
That means starting now. Here are five steps to get from Project Online to a platform (like Primavera P6 or Oracle Primavera Cloud) without losing data, governance, or your team’s sanity.
1. Audit What You Have!
Inventory everything in Project Online: active and archived projects, resource assignments, baselines, custom fields, reports, dashboards, and SharePoint workflows. Count users by role. Document which reports drive decisions and which are gathering dust. This audit becomes your migration acceptance criteria—you can’t validate the move if you don’t know what you started with.
2. Pick Your Platform
Microsoft’s suggested replacements (Planner, Project for the Web) work for lightweight task management. They don’t replace enterprise scheduling, portfolio rollups, or resource leveling. Evaluate platforms on what your PMO actually needs: critical-path scheduling, multi-project portfolio visibility, cost-loaded schedules, and resource optimization. Run a proof of concept—export a real project, import it into your finalist tool, and see what breaks.
3. Migrate Data in Waves
Don’t move everything at once. Create three waves: pilot (2–3 projects), early adopter (5–10), then full portfolio. For each wave, export schedules, resources, and costs from Project Online. Import into a staging environment. Validate that task counts, durations, dependencies, and baselines survived the trip. Map custom fields between platforms—migrate the business-critical ones, archive the rest. Run each wave in parallel with Project Online for 1–2 weeks before sunsetting the old data.
4. Rebuild Governance and Workflows
Your SharePoint workflows die April 2, 2026 regardless. Rebuild project approval gates, status reporting cadences, resource request processes, and portfolio intake in your new platform. This runs in parallel with data migration—don’t wait until the data is moved to start. Test workflows with real users before go-live.
5. Rebuild Reports and Train Your Team
Prioritize executive dashboards and PMO-critical reports first—these drive decisions. Then build PM-level views (task lists, timelines, dependencies) and stakeholder reports. Train admins before go-live, power users shortly after, and onboard executives at launch. Keep a help desk running for the first month. Gather feedback and iterate.
You Don’t Have to Do This Alone
At Global PM, we’ve helped hundreds of organizations navigate the process—from the initial audit through tool selection, data migration, workflow rebuilds, and team training. Whether you’re just starting to plan or you’re mid-migration and need expert support, we’re here to help.
Ready to get started? Reach out to Global PM for a conversation about parth forward!