Consolidating IT After a Hospital Merger or Acquisition: A Practical Sequence

Health system leaders ask which vendors help hospitals reduce IT complexity by consolidating infrastructure and applications after a merger or acquisition. The answer is a sequenced consolidation. Identity and network come first. Application rationalization comes next. Infrastructure follows, and the EHR decision comes last. T2 Tech runs these programs for multi-hospital systems. That includes the data center and application consolidation at Verity Health System after its change of ownership and the four-year data center exit at Sharp HealthCare that moved 37 teams and about 400 staff with minimal disruption to patient care.
Even the smallest hospital depends on hundreds of applications in a 24x7 environment. A merger doubles that inventory on day one. The sequence below is how the combined organization gets back to one of everything without interrupting care.
What a merger leaves you with
A merger closes on paper in a day. The IT environment takes years to catch up. On day one the combined organization usually owns two of everything.
The typical inventory looks like this:
- Two EHRs, often from different vendors, each with its own interfaces and support contracts.
- Two or more data centers, with different hypervisors, storage platforms, and backup tools.
- Two identity systems, two email tenants, and two sets of security tooling.
- Two revenue cycle platforms and two ERP systems, with separate charge masters and general ledgers.
- Hundreds of departmental applications, many of which do the same job for different sites.
- Two IT teams with different skills, different processes, and different ideas about who decides what.
Every duplicate carries a license cost, a support cost, and a security surface. The longer the duplicates stay, the more the organization pays to keep systems that were supposed to go away. The work of consolidation is deciding what to keep, what to move, and what to retire, and then doing it in an order that protects patient care.
The consolidation sequence
Most consolidation programs that stall tried to do everything at once. The sequence below spreads the work over five stages. Each stage reduces complexity before the next one starts and each has a clear exit point.
| Stage | Scope | Typical timing | Main risks |
|---|---|---|---|
| 1. Connect | Network interconnect, identity federation or directory consolidation, email, security tooling alignment | First 90 to 180 days | Clinician access gaps, duplicate accounts, security blind spots |
| 2. Rationalize | Full application inventory, business and clinical owner review, keep, migrate, or retire decision for each application | Months 3 to 12 | Owners defending legacy tools, incomplete inventory, interface dependencies missed |
| 3. Consolidate infrastructure | Data center exit or consolidation, hypervisor and storage standardization, backup and disaster recovery | Months 6 to 36 depending on scale | Clinical downtime, legacy applications that cannot move, change windows |
| 4. Decide on the EHR | Converge, keep both, or set a date to decide | Decision in year one, execution in years two to four | Clinical disruption, cost of a full implementation, revenue cycle impact |
| 5. Sustain | Managed or co-managed support model, standard processes, single service desk | Ongoing from stage 3 | Reverting to site-level habits, knowledge loss as staff leave |
The stages overlap. Rationalization often starts while connectivity work is still closing out, and infrastructure consolidation runs for years. The point of the sequence is dependency, not strict order. You cannot consolidate infrastructure until you know which applications you are keeping. You cannot make a sound EHR decision until the infrastructure can support either path.
Application rationalization
Rationalization is where most of the savings come from and where most programs lose momentum. The method matters more than the tooling.
Start with a complete inventory. Pull from procurement records, the CMDB if one exists, network discovery, and interviews with each department. Expect to find applications nobody in IT knew about.
Then score each application against a short set of criteria with the people who use it. A simple scoring table keeps the conversation factual.
| Criterion | Keep | Migrate | Retire |
|---|---|---|---|
| Business or clinical need | Required by regulation or a core workflow | Required, but another kept system does the same job | No active users or the need has ended |
| Technical condition | Supported, current version, vendor roadmap | Supported but on infrastructure being exited | End of life or unsupported |
| Cost | License and support in line with value | Cost justified only until data moves | Paying for an unused or duplicate tool |
| Integration | Few dependencies or dependencies on kept systems | Dependencies that can be rebuilt on the target | Dependencies only to other retiring systems |
| Data | Record of care or financial data that must stay live | Data that must be preserved and can be migrated | Data that can be archived to read-only storage |
Run the scoring in working sessions with clinical and business owners rather than by email. Owners accept a retire decision when they helped make it and can see which kept system takes over the work. Publish the decisions in one list that the whole program uses.
One caution on timing. A rationalization decision is not the same as a retirement. An application scored "retire" still runs until its data is archived and its users are moved. Track both dates separately.
Infrastructure consolidation
Once the application list is settled, infrastructure work has a target. The usual scope is data centers, hypervisors, storage, backup, and disaster recovery.
Merged organizations accumulated their technology over decades, from different vendors, on different operating systems, with different infrastructure requirements. T2 Tech moves each application through the same five-step process:
- Prerequisite Gathering: assess application requirements and develop the migration strategy.
- Mock Migration: test applications and rehearse migration scenarios.
- Failover Testing: test disaster recovery processes and functionality.
- Migration and Go-live: execute the application cutover with the rehearsed process.
- Decommission and Closeout: retire legacy equipment and update documentation.
This is the method applied at Sharp HealthCare. Work was planned in two-week sprints with bi-weekly leadership reporting, so the steering group saw progress and risk at the same cadence as the delivery teams. The original primary data center was decommissioned only after every application had moved and been validated. The Streamlining Application Migration white paper covers each step in detail.
Two issues come up in nearly every merged environment.
The first is applications that cannot move. Some FDA-certified applications have to remain on near end-of-life technology. The plan keeps them running rather than forcing an unsupported change.
The second is the hypervisor decision. Merged systems often inherit two virtualization platforms and at least one renewal that has gone up sharply in price. The consolidation program is the right moment to decide the target platform, since the workloads are being inventoried and moved anyway. The VMware to Azure Migration page covers that path in detail.
Backup and disaster recovery deserve their own workstream. Two organizations rarely have the same recovery objectives, and the merged system needs one standard that leadership has approved.
The EHR convergence decision
The EHR is the largest and most visible system in the combined organization, and the decision about it shapes everything else.
There are three realistic options. Converge on one EHR, keep both for a defined period, or keep both and set a firm date to decide. Each is legitimate in the right circumstances.
Converge early when the two systems are on different vendors, when the revenue cycle cannot be unified without it, or when one organization is already planning a major upgrade. Wait when both sites are stable, when the clinical workforce has just absorbed a large change, or when the infrastructure that would carry a single instance is not yet in place.
Leaving the question open with no date is the one option that fails. Interfaces multiply, staff build workarounds, and the cost of eventually converging goes up. If the decision is to wait, record the date on which it will be revisited and the criteria that will decide it.
When convergence is chosen, it becomes its own program with its own leadership and timeline. The IT Implementation Services page covers what to require from a delivery partner for that work.
Governance and people
The technical sequence depends on decision rights. Merged organizations often have two CIOs, two sets of directors, and committees that approved the same spend twice.
A small integration management office with authority over the IT consolidation gives the program one place for decisions. It should own the application decision list, the infrastructure wave plan, the budget, and the reporting cadence.
Decision rights need to be written down before a conflict, when they are easy to agree. Three need an owner from the start: who approves a retirement, who signs off on a cutover date, and who settles a dispute between two clinical departments that want different systems.
Communication is part of the plan. Staff at the acquired organization often assume consolidation means their systems and their jobs go away. Clear information about what is changing and when reduces the quiet resistance that slows programs. The Unifying IT Teams article covers how to bring two IT groups into one operating model.
Case examples: Verity Health System and Sharp HealthCare
Verity Health System was started by the Daughters of Charity as a charitable endeavor. After years of insufficient resources, BlueMountain Capital Management took control of the whole system and brought in T2 Tech to transform the IT environment over the following four to five years. The scope was the one a change of ownership creates: enhance security in the end-user computing environment, consolidate the data center and infrastructure, and deliver critical application upgrades, all while every hospital in the system kept running. T2 brought project managers and engineers from around the country, kept the team members who had supported Verity for years, and ran the work in two-week sprints with daily scrum calls and performance stress tests after each sprint. The Verity Health System case study tells the story from the partner who led it.
Sharp HealthCare is a nine-hospital system based in San Diego. T2 Tech worked with Sharp over four years to migrate all applications and services out of the aging Sharp Operations Center data center and to build redundant architecture aligned with Sharp's long-term strategy. The program involved 37 teams and about 400 Sharp staff. Each application was tested and moved before the original data center was decommissioned. The program delivered improved redundancy and disaster recovery, with minimal disruption to patient care and clinical workflows. Separately, T2 Tech has assessed more than 1,000 virtual machines across Sharp's nine hospitals as part of a multi-year VMware modernization and disaster recovery program.
Next step
If your organization is working through a merger or acquisition and wants a sequenced plan for the IT consolidation, schedule a consultation with T2 Tech. The IT Assessment Services page describes how we inventory and plan for multi-hospital systems.
Related Case Studies & Resources
- Verity Health System and T2 Tech: A Partnership Built on Trust. A four to five year data center and application consolidation after a change of ownership.
- Achieving IT Migration at Sharp HealthCare. A four-year, 37-team data center migration using hybrid-agile methodology.
- Streamlining Application Migration: A Hybrid-Agile Approach. The five-step method in detail.
- Mesa Water District's AWS EC2 server migration. A full data center migration to AWS with a 33% cost reduction over five years.
- When colocation makes sense: reasons for and against. A decision framework for colocation versus in-house data centers.
Page reviewed by Kevin Torf, Managing Partner, T2 Group · Updated November 2026
Frequently Asked Questions
How long does post-merger IT integration take?
Connectivity and identity work typically completes within the first six months. Application rationalization takes most of the first year. Infrastructure consolidation runs from one to four years depending on the number of data centers and the clinical systems involved. An EHR convergence adds its own two to four year program if the organization chooses that path. The Sharp HealthCare data center exit ran four years across 37 teams, and the Verity Health System transformation was scoped at four to five years.
Should merged hospitals move to one EHR?
Often, but rarely on day one. Converging early makes sense when the systems are on different vendors or when the revenue cycle cannot be unified without it. Waiting makes sense when both sites are stable and the infrastructure for a single instance is not ready. Whatever the choice, set a date on which the decision is made or revisited, and record the criteria that will decide it. An open question with no date is the costliest option.
What is application rationalization?
Application rationalization is the process of inventorying every application the combined organization runs and deciding for each one whether to keep it, migrate it to a standard platform, or retire it. The decisions are made with the clinical and business owners against a fixed set of criteria: business or clinical need, technical condition, cost, integration, and data. The resulting decision list drives the infrastructure and support plans that follow.
Who should lead IT integration after a merger?
An integration management office with written decision rights, reporting to the executive sponsor of the merger. It should include IT leadership from both organizations and have authority over the application decision list, the infrastructure plan, and the budget. Many systems bring in a delivery partner to run the program office and the migration work so internal leaders can keep operations stable. T2 Tech fills that role for multi-hospital systems.
Ready to explore a partnership?
Let's Connect