Free Your IT Team from Legacy ERP Maintenance: A Practical Playbook for Hospital CIOs
If you are running applications at a mid-market hospital, you already know where your team’s hours actually go. Not to the digital front door. Not to the EHR optimization roadmap. Not to the cybersecurity work the board keeps asking about. The hours go to keeping the financial platform standing.
Patches. Batch job failures. Middleware updates. EHR-to-GL integration scripts that break every time the source system ships a release. A monthly close that depends on three people on your team being available to troubleshoot when the data does not land where it should.
This is the legacy ERP maintenance burden. It is invisible in the project portfolio because nothing about it looks like a project. It is just the cost of running. And until you quantify it, the modernization conversation never moves forward, because nobody can see what you are actually paying.
This playbook is for CIOs and VPs of Applications who suspect their team is over-allocated to ERP maintenance but have not yet built the case internally. The goal is not to sell you on a platform. The goal is to give you a structured path from problem recognition to modernization readiness, so that when the finance team brings up cloud ERP again, you are the one with the data.
Here are the six steps.
Step 1: Quantify the Maintenance Burden in FTE Terms
You cannot make the case for change with a feeling. You need the number.
Pull your team’s time data for the last 90 days and tag every ticket, incident, and project-coded hour that touched the ERP, its integrations, or its supporting infrastructure. Include the obvious work (database administration, backup management, version patching) and the less-obvious work (helping finance staff troubleshoot exports, rebuilding broken file transfers, answering “did the batch run last night?” questions on Monday mornings).
If you do not have ticket-level tagging, run a structured interview with each member of your applications and infrastructure teams. Ask three questions:
- What ERP-related work did you do this week?
- How many hours did it take?
- How much of it was reactive (something broke) versus proactive (planned maintenance or improvement)?
Aggregate the answers. Convert hours to FTE equivalents. The number is almost always higher than IT leaders expect when they first put it in writing. That is a budget line item your team is paying without ever seeing it priced.
Document the split between reactive and proactive work. The reactive percentage is the more important number. When the majority of ERP-related hours are reactive, your team is not maintaining a platform. They are stabilizing it.
Step 2: Map the Integration Architecture
Most legacy ERP maintenance does not happen inside the ERP. It happens at the seams between systems.
Draw the integration architecture between your financial platform and every system it touches: the EHR, payroll, AP automation, supply chain, revenue cycle, donor management for the foundation, the bed management system, anything that exchanges data with the GL. For each connection, document four things:
Method:
Flat file transfer, scheduled batch job, custom middleware, point-to-point connector, or API.
Direction:
One-way or bidirectional.
Frequency:
Real-time, hourly, nightly, weekly, ad hoc.
Owner:
Which team or person on your staff is on the hook when it breaks.
This map almost always surprises the CIO. The number of unique integration patterns is higher than expected. The dependence on specific staff members for specific connections is higher than expected. And the percentage of connections built on fragile methods (flat files, batch jobs, undocumented middleware) is usually well over half.
For a deeper look at why those fragile methods accumulate and how API-native architecture changes the model, see our earlier post: Open APIs for EHR Integration: How Cloud ERP Eliminates Integration Spaghetti.
The map is the artifact you use later when finance asks “what would it take to move?” You already know. The map tells you.
Step 3: Identify the Capacity Your Team Is Not Spending Elsewhere
Maintenance hours are not just hours. They are hours not spent on the work your CIO peers are doing at organizations that already modernized.
List the strategic initiatives your team should be advancing but has deferred or under-resourced because of ERP maintenance load. Common examples:
Clinical systems optimization:
Epic upgrades, Cerner consolidation, EHR workflow improvements.
Cybersecurity hardening:
Zero-trust architecture, identity management, ransomware preparedness.
Patient-facing digital initiatives:
Patient portals, telehealth, scheduling automation.
Data and analytics maturity:
Clinical data warehouse, population health analytics, dashboarding.
AI and automation pilots:
Clinical documentation, revenue cycle automation, operational forecasting.
For each, estimate the team capacity that would be required to move it forward and compare it to what you have available after maintenance is accounted for. The gap is your opportunity cost. It is the work that is not getting done because the ERP keeps demanding hours.
For a concrete example of the kind of capacity that gets unlocked on the finance side when these patterns change, see our earlier post: 20+ Hours of Manual Imports, Gone: What the EHR-to-GL Workflow Looks Like After Cloud Migration. The IT-side version of that same story is the redirection this step is asking you to quantify.
This list does two things. It changes the modernization conversation from defensive (we need to fix what is broken) to offensive (we need to redirect capacity to what we cannot currently do). And it gives your CFO and CEO peers a concrete picture of what your team could deliver if the maintenance burden lifted.
Step 4: Define What "Liberation" Actually Looks Like
Vague target states do not build business cases. Specific ones do.
For each of the maintenance categories you documented in Step 1, define what success looks like on a modern platform. Be precise. Use your own numbers from Step 1 in the table; the directional pattern looks like this.
| Maintenance Category | Legacy ERP (Current) | Multi-tenant SaaS like Sage Intacct (Target) |
|---|---|---|
|
Database administration
|
Active capacity on patching, backups, performance tuning
|
Near zero; vendor manages infrastructure
|
|
Integration maintenance
|
Heavy capacity on file transfers, batch monitoring, middleware patching
|
Reduced to configuration and exception monitoring on an API-native platform
|
|
Version upgrade coordination
|
Annualized capacity on planning, regression testing, deployment
|
Minimal; continuous updates on the vendor’s schedule, not yours
|
|
Custom report development
|
Ad hoc finance requests requiring database queries
|
Reduced as finance self-serves from healthcare-validated reports
|
A note on the integration line: APIs do not eliminate integration work, but they change the nature of it from reactive maintenance to proactive configuration.
The total reclaimable capacity from this exercise is the centerpiece of your business case. Whatever your specific numbers turn out to be, the value is in expressing the maintenance burden in the only language your CFO needs: people, hours, and what they could do instead.
Step 5: Build the Cross-Functional Case Before You Need It
CIOs who go to the board alone with an IT modernization argument tend to lose. CIOs who arrive with the CFO and the CEO already aligned tend to win.
Start the alignment work early. Bring your numbers from Steps 1 through 4 to the CFO. Frame the conversation around shared outcomes, not technical preferences.
Lead with capacity
Show what your team is spending on maintenance today and what could be redirected. In a hiring environment where administrative vacancies remain elevated across healthcare, the idea that you can recover meaningful IT capacity without adding headcount is consistently interesting to a CFO.
Connect to the finance team's pain
Your team’s maintenance hours map directly to delays, errors, and rework on the finance side. The integration that breaks at 2am is the same integration that causes finance to miss its close target. The CFO already knows this from their angle. You are confirming it from yours.
Establish shared ownership of the case
The strongest modernization arguments are joint. CFO owns the financial value (close time, margin visibility, board reporting). CIO owns the operational value (capacity, risk, integration architecture). When the case goes to the board with both signatures, it does not look like an IT pet project. It looks like enterprise transformation.
Be honest about what modernization will require from finance
Implementation is not something you outsource entirely to a partner. The finance team will need to invest meaningful capacity during the implementation window, often the equivalent of a part-time-but-substantial dedicated role. The CFO needs to plan for that. Surprises on this point derail more projects than budget overruns.
Document the alignment in writing
A one-page joint memo from CFO and CIO, signed by both, is worth more than three deck reviews. It locks in the framing before competing priorities have a chance to fragment it. It also gives the CEO and the audit committee something concrete to react to when the case gets escalated.
Step 6: Establish Modernization Readiness
Before you commit to an evaluation, audit your organization’s readiness across four dimensions.
Sponsorship readiness
Is there an executive sponsor (typically the CFO) who will own the project at the steering committee level? Will the CEO endorse the initiative publicly to the board? Without active executive sponsorship, modernization projects stall the first time scope creep meets resistance.
Data readiness
How clean is your current GL? How many open intercompany items, unreconciled accounts, and legacy customizations need to be addressed before migration? Most healthcare organizations need a dedicated cleanup window before implementation kickoff. Scope it explicitly and build it into your timeline.
Process readiness
Are your close, reconciliation, and consolidation processes documented? If the institutional knowledge lives in three people’s heads, the implementation will be harder than necessary. Documenting current-state processes is a useful pre-implementation exercise regardless of timing.
Change management readiness
How many of your finance, IT, and operational staff have lived through a major system implementation? If the answer is “very few,” budget more heavily for training, communications, and stakeholder management. Cultural readiness is the variable that most often separates implementations that hit their targets from those that drift.
The output of Step 6 is a readiness scorecard. Anything scoring below 3 on a 5-point scale is a workstream you need to address before kickoff, not during it.
Putting the Playbook Together
You now have six artifacts:
- A quantified maintenance burden expressed in FTEs.
- An integration architecture map.
- An opportunity-cost list of strategic initiatives that maintenance is crowding out.
- A target-state definition with reclaimable capacity by category.
- A cross-functional alignment plan with finance and executive sponsorship.
- A readiness scorecard.
Together, these are the structured path from problem recognition to modernization readiness. They are also the briefing document for any modernization conversation, whether it is internal (board, CFO, CEO) or external (an implementation partner, a software vendor, a peer CIO who is further along the path).
The CIOs who run this exercise end up in a different position than the ones who do not. They have data instead of opinions. They have a partnership with finance instead of a turf conflict. And they have a clear-eyed view of what modernization will and will not solve, which is the only foundation that makes the eventual decision durable.
Where DSD Comes In
DSD Business Systems is a Sage Intacct implementation partner specializing in mid-market healthcare organizations. Our consulting team includes former healthcare finance leaders, paired with implementation engineers who have spent years inside hospital IT environments. That combination means we understand both sides of the maintenance burden you are trying to quantify: the IT hours it consumes and the finance-side consequences when those hours run short.
When CIOs work with us, the early conversations look more like peer benchmarking than vendor pitching. We share what other mid-market hospitals saw when they ran a similar playbook. We pressure-test your integration map against patterns we have seen across implementations. We help you build the cross-functional case with finance, because we have built that bridge on dozens of engagements. When the case is ready and the architecture criteria are clear, Sage Intacct is consistently the platform that meets them for mid-market healthcare: multi-tenant, API-native, and built around a dimensional GL.
If you are at the point where you suspect ERP maintenance is consuming more of your team than it should, the next step is the audit in Step 1. Run it. Bring us the numbers. We will tell you what we see, including the parts where the answer is “you are not ready yet, here is what to address first.”
Talk to a partner who knows what this audit looks like from both sides.
Schedule a consultation.
Douglas Luchansky
Director, Client Transformation
