Ask an employee at a newly combined company how their first Monday after close went, and you’ll often hear some version of this: two email inboxes open, two passwords for two networks, a vendor invoice waiting for approval in a system they’ve never seen, and a meeting invite from a new colleague that won’t land because the two companies’ calendars can’t see each other.
None of that shows up in the purchase agreement. All of it shows up in productivity, in morale, and eventually in whether the deal delivers what the model promised.
What is post-merger IT system consolidation? Post-merger IT system consolidation is the process of combining two companies’ overlapping technology into one shared environment after a deal closes. It typically covers four areas: identity and access, email and collaboration, ERP and financial systems, and software licensing. The goal is one set of systems that employees, leaders, and auditors can trust.
Integration is the broad effort of making two companies work as one. Consolidation is the part of that effort where you decide which of two overlapping systems survives, then move everyone onto it. For most mid-market acquisitions, that work falls into four workstreams.
| Workstream | What it covers | The core decision |
|---|---|---|
| Identity and access | User accounts, single sign-on, multi-factor authentication (MFA), admin rights | One directory, or a temporary trust between two while you plan the merge |
| Email and collaboration | Email domains, Teams or Slack, file storage, shared calendars | Which tenant becomes home, and when everyone moves |
| ERP and financial systems | Enterprise resource planning (ERP), accounting, payroll, CRM, reporting | Which system becomes the single source of financial truth |
| Licensing and SaaS | Microsoft 365, line-of-business apps, duplicate subscriptions | Which contracts to keep, merge, or cancel at renewal |
Each workstream touches people differently. Identity changes how they sign in. Email changes how they talk to customers. ERP changes how they close the month. Licensing changes which tools they have at all.
Because that’s where a large share of the synergies live. In PwC’s 2026 M&A Integration Survey of 530 senior dealmakers, technology and data enabled at least a quarter of deal synergies for nearly nine in ten acquirers, and more than half of synergies for almost a third.1 Yet the same survey found that only about one in three acquirers fully achieved all of their prioritized deal objectives.1
The distance between those two findings is often a consolidation gap. Running two of everything costs money in ways the deal model rarely captures: duplicate licenses, two support contracts, reports stitched together by hand, and security controls that cover one environment but not the other.
Licensing alone is a meaningful leak. Zylo’s 2026 SaaS Management Index found that only 54% of software licenses in the average organization are actually used.2 Combine two companies that each carry their own subscriptions, and that waste compounds.
If you’re the M&A director or operating partner carrying the integration plan, the frustration is familiar. The deal was approved on the strength of synergies, but nobody owns the unglamorous work of retiring the second ERP. It shouldn’t take a year of duplicate costs to learn which systems were supposed to go away.
The instinct is to default to the acquirer’s systems. Often that’s the right call, but not always. A smaller add-on may be running a better-configured, more modern platform than the parent. Ask the same five questions about every overlapping system:
Write down each decision and the reason behind it. Six months from now, when someone asks why the legacy CRM is still running, you’ll have an answer.
Sequence matters as much as the choices themselves. A practical order for most mid-market deals:
For how this sequence fits into the broader post-close timeline, see our guide to post-merger IT integration in the first 90 days. Most ERP consolidations run well past that window, and that’s fine. A clear plan with named owners and dates matters more than raw speed.
Every consolidation decision changes someone’s workday. The accounting team that closed the books in one ERP for a decade now has to learn another. Sales has to adopt a new CRM in the middle of a quarter. If training ends at “here’s your new login,” productivity dips right when the combined company needs momentum.
PwC found that only 16% of acquirers assessed leadership and talent before signing.1 That tells you how often the people side becomes an afterthought. Build retraining into the plan from the start:
We explore this further in your people are the hardest system to integrate.
At Sentry, we’ve guided acquirers and portfolio companies through technology diligence and integration, and we use our Technology Maturity Model (TMM) to keep consolidation grounded. The model has four stages: Operate, Secure, Integrate, and Innovate.
System consolidation lives in the Integrate stage. But you can’t integrate on a shaky foundation. If the acquired company is still working through Operate (unreliable infrastructure, untested backups) or Secure (missing MFA, unknown admin accounts), those gaps come first. Scoring both companies on the TMM before close shows where each one stands and what has to happen before systems merge. It’s also why the IT due diligence red flags every acquirer should run down matter so much: what you uncover in diligence becomes your consolidation roadmap.
Employees sign in once and reach everything they need. Customers see one company, one domain, one experience. Finance closes the month from a single system, and leadership trusts the numbers. Duplicate contracts are gone, so the savings in the deal model show up in the actual P&L. And when the next add-on arrives, you have a repeatable playbook instead of a blank page.
That’s the moment the combined company stops being two businesses sharing a logo and starts operating as one.
IT integration is the full effort of making two companies’ technology work together, including security, support, and connectivity. Consolidation is the part where overlapping systems are reduced to one. You can connect systems temporarily, such as with a trust between two directories, before you fully consolidate them.
It depends on deal size and complexity. Identity and email consolidation can often be completed in the first few months after close. ERP consolidation usually takes much longer because it touches finance, operations, and reporting. Planning before close shortens every phase.
Not automatically. The acquirer’s systems are often the right choice for consistency, but evaluate each overlap on fit, security, cost, and the number of people affected. Sometimes the acquired company’s platform is the better long-term option.
Before the deal closes. Technology due diligence should identify overlapping systems, contract terms, and migration costs so they can be built into the purchase price and the integration budget.
One accountable leader, typically a CIO, vCIO (virtual Chief Information Officer), or experienced integration partner, with named owners for each workstream. Consolidation stalls when it’s split across business units with no single decision maker.
You don’t have to decide which systems survive on your own. You need a clear picture of where both companies stand and a guide who has helped acquirers through this before.
Heading into a transaction? Let’s talk about technology due diligence before it’s too late. Schedule a Project Consultation. [PLACEHOLDER LINK]
1. PwC. “2026 M&A Integration Survey.” September 29, 2026. https://www.pwc.com/us/en/services/consulting/deals/library/ma-integration-survey.html
2. Zylo. 2026 SaaS Management Index, as cited in Zylo, “SaaS License Management.” https://zylo.com/blog/saas-license (Verify the 54% figure against Zylo’s full 2026 index before publishing.)