Microsoft Project Online is approaching retirement - or, in this case, its retirement date has already passed. But replacing a project management platform is not as simple as moving tasks from one product to another. In this episode of Support Engineering Weekly, Alex and Maya examine the architectural differences between Project Online and Planner Premium, and why treating Planner Premium as a one-to-one replacement can put important business processes at risk. We begin by separating project execution from enterprise project and portfolio management. Planner Premium is well suited to structured collaborative execution, including task dependencies, milestones, timelines, and critical paths. But enterprise workloads may also depend on resource capacity planning, complex timesheets, financial forecasting, and cross-project management capabilities that require a different approach. The discussion explores Planner Premium’s technical boundaries, including task, resource, custom field, successor link, and project duration limits. We then examine the illusion of equivalence: why workload visibility is not the same as enterprise resource management, and why portfolio views do not automatically unify every project management system. From there, we look at the hidden dependencies that make migrations difficult: Power Automate flows, custom Power Apps, APIs, reporting, financial systems, governance, and the need to establish an authoritative plan of record. Alex and Maya then walk through a fit-gap assessment approach, from identifying the business capabilities teams actually use to classifying requirements, validating dependencies, selecting the right destination, and testing complex workloads in a pilot. Finally, we explore how different workloads may need different destinations - including Planner Basic, Planner Premium, Project Server, Dynamics 365 Project Operations, Project desktop, or archival for inactive projects. The central lesson: Don't replace the product. Replace the capability. Disclaimer: This episode discusses the Microsoft Project Online retirement date of September 30, 2026, which has already passed. The episode is being published after that date because an earlier publication slot was not available. The discussion reflects the retirement timeline referenced during the original recording. Chapters 00:00 - The Retirement Deadline and the Assumption 02:01 - Project Execution vs. Enterprise PPM 04:35 - Planner Premium's Technical Boundaries 07:44 - Visibility vs. Resource Management 11:29 - Dependencies, Governance, and Migration Risk 17:12 - Routing Workloads to the Right Platform 20:01 - Archive What No Longer Needs a Home Learn more: The full technical article, references, and supporting resources are available through the Support Engineering Blog at https://blog.sadhan.ch/.
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
You are listening to Support Engineering Weekly. You know, there is a very specific kind of quiet panic that sets in when a major piece of enterprise software gets a firm retirement date. Oh, yeah. Absolutely. Because you look at the calendar, you look at your infrastructure, and suddenly the clock is just taking incredibly loud. And for, I mean, thousands of IT leaders in project management offices right now, that date is September 30th, 2026.
Right. Which is when Microsoft Project Online officially retires. Exactly. And when you're staring down a deadline like that, human nature kind of kicks in, right? You wanted immediate one-to-one replacement. You just want the easy button. Yeah, exactly. You see that Microsoft's premium project management capabilities are now, you know, integrated into Planner. And it creates this massive tempting assumption that Planner Premium is just the automatic drop-in replacement for project online. I'm Alex. And I'm Maya. But the reality of Enterprise IT is rarely that simple.
I mean, if you just hit the Migrate button based on a product name, you are likely going to break core business processes you didn't even know existed. Exactly. And hey, we want to explicitly thank you, the listener, for joining us today. Because in this deep dive, we are going to help you figure out what your teams actually need to survive this deadline. Rather than, you know, just blindly trusting a software swap. Right. We're essentially doing a capability gap analysis today. Yeah. We are. We're going to unpack the engineering reality of where Planner Premium actually fits,
where it's technical capability stop, and how to safely navigate the migration without bringing your entire organization to a halt. And doing that really requires stripping away the marketing assumptions. We have to look at the fundamental architecture of these two platforms because they were designed to solve two entirely different engineering problems. Okay. Let's unpack this because understanding that foundational difference in project management layers is really where every single migration strategy has to start. Right. So we could think about project execution
as being like building a single house. You have a foundation, you have walls, you have a roof, you need a hammer, you need nails, and you need a schedule that dictates the drywall can't go up until the electrical is finished. That is project execution. I like that analogy. Yeah. But enterprise project portfolio management, which is what a lot of people actually used project online for. That is like urban planning. You weren't just building one house. You are managing the city zoning permits, the cross city plumbing grid connections,
the tax codes across the whole neighborhood. And forecasting if the city even has enough concrete to support the 50 houses being built this year. Right. Exactly. That captures the structural difference perfectly because when we look at the underlying mechanics of plan or premium, it is giving you the tools to construct the house. It's really designed for structured collaborative project execution. Okay. So it absolutely excels at the mechanics of building, managing the timeline, handling direct task dependencies, highlighting the critical path for that specific deliverable,
right, tracking milestones and giving you people views to see who is doing what on that individual site. It calculates when the roof can go on based on when the walls are finished. And I mean, for a massive portion of everyday work, that level of coordination is exactly what a team needs. Oh, absolutely. Like if I'm launching an internal IT service desk, I need to know that testing depends on server configuration and end user training depends on testing. Plan or premium handles that workflow beautifully, right? It handles it seamlessly.
But the architectural friction happens because, well, project online was rarely deployed just to build a single house. Over the last decade, organizations built these massive, complex operating models on top of it. Yeah. It became the urban planner. Exactly. It handled deep resource scheduling algorithms across hundreds of concurrent projects. It managed complex, multi-tiered time sheets that fed directly into, like enterprise financial forecasting and cross-project reconciliation. Wow. Those are enterprise PPM concerns. They require a completely different data structure.
And frankly, there are areas that sit totally outside of Planner Premium's core architectural scope. I mean, Planner Premium doesn't natively run enterprise level financial forecasting or organization-wide capacity leveling. So the operational impact of that is just huge. Because if you try to use the house building tool to run the city zoning department, you're going to hit a wall very quickly. Very quickly. And that brings us to the actual hard technical boundaries of the platform. Because Planner Premium has specific scale limits
that dictate what you can and cannot build. Yeah. And we really need to treat these limits as strict engineering parameters. If we look at the platform's constraints right now, you are looking at a maximum of 3,000 tasks per project. Okay. You can allocate up to 300 resources per project. You're hard-capped at 10 custom fields, 10 goals, and 2,000 successor links. Wow. Okay. And the maximum mathematical duration for any single project is 3,650 days, which is about 10 years. See, I have to challenge the task limit though, because 3,000 tasks
and 300 resources per project sounds massive. I mean, if a single project manager is trying to manually track 3,000 individual tasks, that feels like a micromanagement nightmare, not a software limitation. Yeah, I get that. Is scale really going to be the bottleneck for most teams? Well, for a marketing team launching a campaign or HR rolling out a new policy, no, 3,000 tasks is more than enough. But let's look at the messy reality of enterprise IT. Right. What if you're migrating a multi-year global ERP rollout,
a project that has been living in project online for, say, seven years, tracking every single server migration, every user acceptance test across 40 countries. Oh, wow. Yeah. You might not hit 3,000 tasks, but you will absolutely hit 2,000 successor links because of how deeply interconnected that schedule is. Okay. That makes sense for the schedule. But what about the 10 custom fields? That number feels incredibly arbitrary to me. Like, why limit it to 10? If project online let me have 50 custom fields, why can't plan our premium just add more columns to the database?
It comes down to a fundamental difference in the data model. Project online was a massive, heavy, sequel-backed beast. You could define endless custom schema because it was basically a monolithic database dedicated just to your PMO. Right. And then you can define a private playground. Exactly. But plan or premium is built on dataverse and operates within the broader Microsoft 365 architecture. It is optimized for speed, real-time cloud collaboration, and standardized reporting across millions of tenants globally. Okay.
So to maintain that performance and integration speed, the schema has strict boundaries. It's not just a smaller database. It's a completely different approach to structuring data. So if my PMO demands 15 specific metadata tags on every project for legal compliance, and I just try to force that migration through, it doesn't just quietly clip the last five fields. No, it doesn't. The API calls fail. The compliance dashboards downstream break, and suddenly legal is knocking on my door because we have 50 active projects missing their regulatory metadata.
Precisely. And that is why those numbers, the 3,000 tasks, the 10 fields, are not automatic reasons to reject plan or premium. It's a highly capable tool. Right. But they are vital assessment points. You have to validate the specific architectural requirements of your legacy data against those exact limits before you move a single byte of data. Which I think introduces one of the most dangerous traps in this whole process. The illusion of equivalence. Yes. Because when IT leaders are rushing to meet that 2026 deadline, they look at a feature checklist.
I look at plan or premium's interface and I see it has a people view. I see an assignments view. It even has plan or portfolios. And while on paper, that sounds exactly like resource and portfolio management. Yeah. And what's fascinating here is how easily the concept of visibility gets confused with the concept of management. Oh, that's a great point. From a software engineering perspective, those are two completely different problems to solve. Let's look at resource management, for example. Planner premium gives you excellent project level workload visibility.
You can look at a board and see that your senior developer is over allocated this week on this specific task. Right. But visibility just tells me what is happening. It's like the difference between staring at a crowded restaurant and actually having the reservation system to book the tables and manage the kitchen's capacity. Exactly. A true project management office doesn't just need to see that the developer is busy. They need enterprise resource management. They need a system that reconciles that developers timesheet, cross references their availability across 50 other in-flight projects and automatically levels the resource pool to figure out who gets to use that scarce specialist next month.
So planner gives you a beautiful window into the project's daily reality, but it does not give you a back-end engine to manage enterprise wide capacity planning. Spot on. It just doesn't. And the same illusion happens when we look at portfolios. Right. Because the planner portfolios feature sounds like a silver bullet for executive reporting. It sounds like it, but again, we have to look at the mechanics. Planner portfolios provide great visibility across supported premium plans, but they have strict structural limits.
Like what? Well, you cannot connect planner basic plans to a planner portfolio. You cannot connect Azure DevOps projects. You cannot connect your legacy project online projects. And crucially, some of the fields in that portfolio view are entirely view only. Oh. So let's talk about the operational reality of that. If my engineering team is running their sprints in Azure DevOps, and my marketing team is organizing their launch in Planner Basic, and my PMO wants one unified pane of glass for the C suite,
Planner portfolios isn't going to magically stitch all those disparate data models together. No, it won't. So if executives are relying on project managers to manually update status fields every Friday just to make the portfolio view look green, the system is fundamentally broken. It is broken. Yeah. And that friction usually bleeds directly into reporting and financials. If your Power BI dashboard suddenly disagree with what's manually entered in Planner, you have completely lost data integrity. That's an nightmare. Furthermore, we have to separate project scheduling from project finance.
Managing tasks, tracking dependencies, and hitting dates is not the same thing as managing actual costs, billing rates, revenue recognition, or integrating with an ERP system. If your workload requires deep financial management, you are looking for specialized enterprise tools, like Dynamics 365 project operations, not a project execution tool. And here's where it gets really interesting, because moving those tasks while ignoring the financial integrations is like moving all your high-end appliances into a brand new house, plugging them into the wall, but realizing you forgot to wire the house for electricity.
I love that. Yes. The data might look pretty sitting in the new kitchen, but the business process quietly fails, because the surrounding ecosystem is basically dead. And that ecosystem is where most migrations actually fail, because a project online environment is rarely just an isolated collection of project schedules. Right. It's plugged into everything. Exactly. Over the years, it becomes this hidden web of technical dependencies. You have power automate, workflows, firing off budget approvals. You have custom power apps reading the metadata. You have downstream APIs feeding your financial systems and operational dashboards that the CEO checks every single morning.
And because plan or premium operates on a fundamentally different data model, you aren't just copying rows into database. You are moving to a new architecture. Right. So all those existing flows, those custom apps, those API calls, they are all going to break if you don't rebuild them for databases. They will. And it's not just the digital wiring we have to worry about. It's the human wiring too. The governance? Yes. The governance model. Replacing the application does not automatically replace the governance. In fact, ignoring governance during this migration is probably one of the biggest unforced errors an IT department can make.
Because plan or premium lives inside the broader Microsoft 365 environment, right? Which means if you don't lock it down, you are dealing with Microsoft 365 group sprawl. Like anyone can just spin up a plan, which spins up a group, a SharePoint site, a share it in box. And suddenly you have thousands of unmanaged plans. You have messy ownership structures where it's entirely unclear who actually owns the data when the project management is. Right. You have external sharing risks where contractors might have access to internal metadata they shouldn't see. And most dangerously, you create complete uncertainty over which system is the actual authoritative plan of record.
Oh, man. I live through that nightmare. If the P&M O swears the plan of record is in project online, but the engineering team is only updating plan or premium and finances refusing to look at anything except an Excel export from last Tuesday, you don't have a plan of record. No, you really don't. You have chaos. And you spend your entire status meeting arguing about which data is accurate instead of talking about the actual project, which is exactly why organizations need a highly structured way to evaluate their environment before that 2026 deadline.
You can't just guess you need a formalized fit gap assessment. So how do we actually execute that? Because if I'm an IT director, starting this tomorrow, my very first instinct is to pull up a spreadsheet and meticulously get a job. And meticulously catalog every single feature project online has, and then just check if planter has it. And that is the first major trap. You should not inventory what the software can do. You need to inventory what your teams actually use. Okay, that makes sense.
When you conduct a fit gap assessment, there is a specific methodology to follow. It's an eight step process. First, you inventory your actual environment. Document the active sites, the roles and uncover all those hidden API integrations and power automate flows we just discussed. Right, finding the shadow IT that is quietly keeping the business running. Exactly. Then step two, you identify what each workload depends on. And this leads to step three, which is the crucial pivot.
You have to translate features into business capabilities. Yes, and that means looking past the terminology, right? Because if I send a survey to the PMO, they are going to say, we absolutely must have the critical path feature. Of course it will. But I can't just put critical path on a checklist. I have to translate that to the business need, which is we need the capability to understand how schedule changes affect delivery. Exactly. Or instead of saying we need resource pools, the actual capability is we need to allocate shared specialists across multiple simultaneous projects.
But translation is the secret to a successful migration because it stops being a feature comparison and becomes a functional requirement. Right. Once you have that requirement, step four is you classify the gap into one of three categories. First is covered, meaning plan or premium satisfies the business requirement natively out of the box. Nice and easy. Yep. Second is partially covered, meaning planner can handle the core tasks, but you are going to need additional architecture like building a new power automate flow or whatever. And the third category is not a fit, meaning the workload depends on enterprise capabilities like cross project financial leveling that simply belong at a different tool entirely.
Spot on. So then step five, once you've classified the gaps, you validate the operating model. Who owns the project lifecycle? How is access governed? What data must be retained for legal compliance? Okay. Then step six is validating the dependencies, right? Yes. Mapping out exactly how the power BI reports and downstream financial systems will connect to the new architecture. And then step seven, only after all of that, do you select the final destination for the workload based on the gap, not the product name?
And then finally, step eight, we get to the pilot phase. But we aren't just running a pilot to get people used to the interface colors, right? No. And this is a critical distinction. The objective of your pilot is not to prove that plan or premium works. Microsoft has already proven the software work. Right. We know it turns on. Exactly. The objective of your pilot is to discover exactly where it doesn't work for your specific use cases. You want to run your most complex edge case workloads through the system to find the breaking points.
You need to discover that the 10 custom field limit breaks your compliance dashboard in a controlled pilot environment, not on day one of a global company rollout. Wow. Yeah, that is crucial. So synthesizing all of this, we have the 2026 deadline. We know how to run the capability assessment. We understand the limits and the hidden dependencies. If project online is going away and we know plan or premium isn't a magical one size fits all answer. Where exactly is all this enterprise work going?
It all comes down to a logical decision sequence. You are essentially asking three sequential questions. One, what are we managing and what business capabilities are required? Two, does plan or premium actually satisfy those capabilities? And three, if not, which platform in the ecosystem addresses the missing gap? Okay. If we break down the typical routing, it usually looks like this. If a team's workload requires straightforward task coordination, essentially just a list of things to do, who is doing them and basic Kanban tracking, that workload doesn't even need premium.
It can likely go straight to plan or basic. But if they need the structured execution, the dependencies, the milestones, the timeline, the critical path for a specific build, that is the exact sweet spot for plan or premium. Correct. But what about the workloads that don't fit? If your assessment reveals deeper enterprise resource needs, complex timesheets or integrated financial management, plan or is not your destination. Those enterprise workloads need to migrate to project server, dynamics 365 project operations, or another specialized third party.
PPM solution that handles those heavy architectural demands. And what about the traditionalists? You have the hardcore project managers who clutch their complex.mbp files like a safety blanket, who don't want cloud collaboration and just want to run heavy desktop simulations. For those highly specific isolated workloads, the destination is often just project desktop. The desktop clients still exist for that exact reason, heavy offline schedule modeling. The reality is that these destinations are not mutually exclusive.
And I think that is the biggest paradigm shift for an IT leader. A successful migration for a large organization isn't a monolithic event where project online moves to plan or premium. No, not at all. A successful migration is a triage exercise. It looks like classifying your workloads and routing them across multiple appropriate environments. Your HR and marketing teams might land in plan or basic. Your internal IT rollouts might land in plan or premium. And your global construction initiatives might move to dynamics 365 project operations.
You are giving each workload the exact environment it needs to succeed, rather than forcing everything into a one size fits all box, just because the clock is ticking. That is the core lesson. The goal of this entire massive exercise is not to replace a product as fast as possible to beat a deadline. The goal is to preserve the business capabilities the organization depends on, to modernize the workflows that actually need changing, and to ensure operational continuity. Don't replace the product. Replace the capability.
That is the perfect takeaway. But before we wrap up today's deep dive, I want to leave you with a final, provocative thought to mull over. Something that builds right on this idea of classifying workloads, but focuses on the past instead of the future. What about your historical data? The projects that have been closed and gathering digital dust for three years. Oh, that's a great point. Sometimes the most successful migration decision for an inactive workload isn't moving it to a new platform at all. Sometimes the smartest architectural move is simply archiving it to meet your legal retention requirements and leaving it at that.
Not every single project needs a new home. Some of them just need a quiet retirement. That is the ultimate form of workload optimization. You've been listening to Support Engineering Weekly from the Support Engineering blog. For the full articles, references, and technical resources from today's discussion, visit the link mentioned in the description. Until next week, keep troubleshooting, keep learning, and keep engineering. Thank you for listening to Support Engineering Weekly. This podcast is available on Apple Podcast, Spotify, iHeartRadio, and other major podcast platforms.
Follow the show on your preferred platform and never miss an episode.
What happens when a routine network maintenance operation triggers a failure deep inside a cloud provider's authentication infrastructure? In this week's episode, Alex and Maya investigate how a seemingly isolated...
How can a routine network capacity upgrade trigger a global cloud outage - and why can the very systems designed to protect availability make the failure worse? In this Support Engineering Weekly bonus episode, Alex and...
Microsoft 365 administrators deal with information from several places: the Microsoft 365 Roadmap, Message Center, and Service Health. But knowing where to find an update is only part of the challenge. The real question...
A server under pressure fails its health checks. Automated traffic management removes it from service, pushing even more load onto the remaining infrastructure. What was designed to protect the system becomes part of...
Microsoft 365’s latest updates are reshaping how users communicate and collaborate - but beneath the cleaner interfaces, this week’s incidents reveal just how fragile cloud routing and data pipelines can be. Alex and...