Author: Jason Rose, CEO, Clearsense
The financial case is straightforward: retire a legacy system and you permanently eliminate its licensing fees, infrastructure costs, and maintenance overhead. But the bigger opportunity is what happens when that becomes a continuous program rather than a periodic cleanup. Systematic technical debt removal compounds over time, freeing operating budget that funds the modernization and innovation investments health systems are under pressure to make.
Here are six reasons a managed service provider (MSP) model is the right structure for that program.
1. Healthcare is good at implementing. It struggles to retire.
There is a well-documented pattern in how most health systems manage their application portfolios. When a new system is implemented, the focus lands on getting the replacement live. Decommissioning gets bundled into the same project and quietly deprioritized as the implementation runs over budget and schedule. The replacement goes live. The old system lingers. The reason is structural: no one owns the retirement. Gartner's Application Undertaker research makes the case that decommissioning requires a designated, accountable role committed to the work over years, not a responsibility bolted onto an existing project team. Without that dedicated owner, what remains are zombie and abandoned applications: zombie apps have known usage but can't be fully decommissioned, abandoned apps lack ownership entirely. Both keep draining budget, creating compliance exposure, and contributing to a portfolio that grows more distorted with every new implementation.
This isn't a failure of intent. It is a failure of organizational structure. Technical debt accumulates quietly across the balance sheet. Most health systems treat it as an IT problem. It is a financial problem, and it belongs on the CFO's agenda alongside every other margin improvement initiative. Addressing it requires the same C-suite alignment, dedicated ownership, and sustained investment that any strategic program demands. Decommissioning requires program governance, data acquisition, clinical and operational archiving, compliance management, and technical retirement running in parallel across dozens of applications. Most IT organizations weren't built for that. Without executive sponsorship and a dedicated owner, the work ends up off the side of someone's desk, and the results reflect it.
Health systems have long relied on MSPs to run infrastructure, security, and application portfolios, but the industry has been slow to apply the same model to one of its largest operational cost drivers: technical debt. A managed service is exactly that dedicated owner at scale: a team whose entire mandate is moving applications from the retirement list to fully decommissioned, continuously and accountably.
2. Decommissioning is not a project. It's a permanent mandate.
The zombie and abandoned application problem doesn't resolve itself after one decommissioning initiative. According to Gartner®, the average health system application portfolio in merged systems carries 20% to 30% bloat: applications that should be rationalized but haven't been (Stefan Van Der Zijden, Gartner, November 2023). That bloat doesn't stay static. Application portfolios are living systems. Every new enterprise rollout, every M&A integration, every cloud migration, and every modernization initiative introduce new candidates for eventual retirement. The portfolio that looks rationalized today will be distorted again within a few years if there is no ongoing program actively searching for the next wave of applications to remove.
This is the operational reality that project-based models often fail to address. A one-time cleanup effort clears the current backlog. It does nothing for what accumulates behind it, and it does nothing for the technical debt that quietly keeps growing. The organizations that make meaningful progress are the ones that stop treating decommissioning as a project and start treating it as a permanent margin improvement engine that runs continuously alongside the business.
The strategic value compounds beyond cost reduction. A health system running continuous application rationalization and technical debt removal enters every major initiative with a cleaner, better-understood portfolio. Modernization strategies are more credible when the organization has a demonstrated track record of following through on retirement commitments. This is what C-suite alignment on decommissioning produces: not just savings on a spreadsheet, but a continuously optimized portfolio that makes every future investment more productive.
3. The true cost of the in-house model is almost always underestimated
Ask a CFO what application decommissioning costs annually and many can't give a clean answer. The spend is buried across IT operating budgets, payables, enterprise system rollout costs, IT inventories, security remediation fees, and other hidden charges. No single line item is alarming enough to trigger scrutiny. The total, when someone adds it up, usually is. Technical debt isn't a line item on the balance sheet, but it shows up everywhere else: in the cost of maintaining systems that deliver no value, in the compliance risk they carry, and in the organizational energy consumed keeping them alive.
A common assumption compounds this problem: many health systems believe they have archiving covered because they have a document management system. They don't. Document management systems are built for unstructured content: scanned paper records, faxes, consent forms, and clinical documents that live outside the EHR. What they don't do is reach into a decommissioned EHR, billing system, or practice management database, reconstruct its underlying data, and present it as a queryable, patient-centric record. That structured work is a fundamentally different capability, and it's the one that fails at scale. As the retirement list grows from a handful of applications to dozens, the gap between what a document management system can handle and what a true archiving program requires widens with every application added. Health systems that discover this mid-program face a choice between expensive re-architecture or carrying the legacy system indefinitely.
Beyond the hidden spend, legacy applications increasingly represent cybersecurity exposure and consume infrastructure and internal bandwidth that should be redirected toward AI and modernization priorities. Every engineering hour absorbed by a system that should have been retired is an hour not invested in the capabilities health systems are racing to build. This is why technical debt removal needs to be on the CFO's agenda. The financial exposure is real, measurable, and growing every quarter the program doesn't move.
A managed service makes the full cost visible, brings it under a single accountable structure, and replaces it with a predictable margin improvement program that the CFO can track, report on, and defend.
4. The cost takeout is large, permanent, and compounds with speed
Every retired application removes a permanent line item from the operating budget. Not a one-time saving. A permanent reduction in the cost structure of the organization: licensing fees eliminated, infrastructure decommissioned, maintenance contracts terminated, and internal staff time redirected to higher-value work. Those savings recur every year, indefinitely, from the moment the application goes dark.
The magnitude adds up faster than most organizations expect. When licensing, infrastructure, support, and internal overhead are fully accounted for, the annual run cost of a single enterprise application is almost always larger than anyone expects. Multiply that across a portfolio of retirement candidates and the total cost takeout available through a structured decommissioning program is often one of the largest untapped margin improvement opportunities, and one of the few that doesn't require revenue growth to realize.
A Gartner case study documented what this looks like at scale: a structured program delivered nearly $100 million in net annual recurring operating expense reductions. That figure represents permanent cost removal from the operating budget, not a project saving. It recurs every year.
The ratio of program investment to cost takeout is what makes this decision straightforward for a CFO. The cost of running a managed decommissioning program is a fraction of the annual run costs it eliminates. The program pays for itself within months of the first retirements, and the savings it generates compound as more applications exit the portfolio.
Speed accelerates that compounding. Every quarter a retirement is delayed is another quarter of permanent savings that never materializes. The larger the backlog and the longer it sits, the greater the cumulative cost of inaction. Deferred decommissioning also increases cybersecurity exposure and widens compliance gaps.
5. The CapEx/OpEx structure of a managed service changes the financial conversation
Most health system CFOs face the same tension: capital budgets are constrained, operating expenses are under pressure, and every initiative competes for the same resources. Application decommissioning often loses this competition, not because the ROI isn't there, but because the program structure makes it difficult to fund cleanly. Costs are distributed across IT operating budgets, payables, enterprise system rollout expenses, IT inventories, and security remediation fees with no single line item to approve and no natural home in a capital plan.
Consolidating the full decommissioning and archiving supply chain under a single managed service changes that and the accounting rules support it. The Big 4 accounting firms confirm the GAAP rules: archiving investment qualifies as CapEx for all implementation activity. Implementation activity includes replacement of an old technology with a new data management solution, data translation mapping, automation, optimization and associated project management, and new features and access, reporting and modernized security. Therefore, all archiving activity can be applied to CapEx budgets. OpEx covers only SaaS licensing and data storage fees.
The result is a financial structure CFOs can model and defend: one-time capital dollars used to unlock ongoing OpEx savings by permanently eliminating legacy licensing, infrastructure, maintenance, and support costs. Ensuring maximum use of CapEx budgets drives further financial benefit and ROI, and gives CFOs a structure they can approve, report against, and protect across budget cycles.
6. A unified archiving strategy is the foundation for AI and innovation
When health systems retire applications without a unified archiving strategy, they don't simplify their data landscape, they fragment it. Clinical data ends up in one archive. Financial records in another. HR data somewhere else. Each archive has its own access model and integrations. The legacy application is gone, but the complexity lives on. The archivers themselves accumulate, and the problem multiplies.
A managed service with an integrated enterprise archiving platform takes a different approach: one unified data layer consolidating clinical, operational, and financial records across all retired applications. End users access historical data from a single interface. Compliance requests are handled from one place. KLAS has documented health systems preserving 20+ years of patient data in a single accessible longitudinal data lake following mass decommissioning, with 100% on-time project delivery.
The more important shift is what happens to the archive itself. The goal is not passive storage. It is a governed intelligence foundation: decades of historical clinical, operational, and financial data, cleaned and structured through the archiving process, made available for AI models, analytics workflows, and longitudinal insight that fragmented point archives cannot support. Health systems that build this foundation are transforming the archiving program from a compliance obligation into a strategic asset that strengthens governance, supports regulatory defensibility, and surfaces the kind of enterprise intelligence their AI initiatives depend on.
This is precisely the trajectory industry analysts are tracking. Gartner projects that by 2030, 40% of organizations will use AI-driven data archives as a strategic resource, up from just 8% today. The health systems best positioned for that transition are the ones building the governed data foundation now, not after the AI initiative is already underway.
The OpEx freed through systematic decommissioning funds that future directly. Every legacy application retired eliminates a cost that can be redeployed toward AI development, data lake infrastructure, and analytics capabilities. The decommissioning program doesn't just clean up the past. It finances the future.
The Bottom Line
The six reasons above add up to one conclusion: application rationalization and active archiving is not an IT initiative. It is a C-suite margin strategy that deserves the same executive ownership, dedicated investment, and continuous governance as any other strategic program. Health systems that recognize this will move faster, reduce more cost, and build the data foundation their AI and modernization priorities depend on.
Clearsense built a managed service purpose-built for continuous application rationalization and active archiving. To learn more about the program, read the full announcement here.
|
Interested in a free assessment of your application portfolio? Visit clearsense.com/managed-services to get started. |