Post-Merger IT Integration: What I’d Do Differently After Working on Four

What Deal Teams Routinely Miss

Before getting to the recommendations, it is worth being explicit about what deal teams routinely miss in pharma post-merger IT integration. Five patterns stand out across the four deals I have worked on.

First, deal teams systematically underestimate the cost of maintaining two states. Integration is not a discrete event; it is a transition during which both the legacy and the target states are partially in operation. The cost of operating both, including duplicative licensing, parallel processes, and the inefficiency of teams operating across two environments, is a real cost that runs for the duration of the integration. Plans that assume an immediate shift to the target state at close consistently miss this cost.

Second, deal teams systematically overestimate the speed at which validated systems can be integrated or migrated. A validated MES, LIMS, or QMS does not move in 90 days. The validation work, the change-control discipline, and the regulatory engagement that accompany any meaningful change to validated systems all extend the timeline. Plans that anticipate validated-system migration on enterprise-IT timelines produce delivery slippage that erodes deal-team confidence in the integration program.

Third, deal teams systematically underestimate the cybersecurity exposure during integration. The transition period is the period of highest cyber risk: combined environments are temporarily more complex, security postures are temporarily heterogeneous, and the attackers who track M&A activity know this. Plans that defer cybersecurity hardening until “after stabilization” produce exposures that are sometimes exploited.

Fourth, deal teams systematically underestimate the depth of vendor concentration changes that close triggers. Vendors that had different relationships with the two pre-merger entities now have one combined relationship, and the terms of that relationship are often renegotiated in ways that favor the vendor. Plans that anticipate seamless vendor continuity are routinely caught by mid-integration vendor renegotiations.

Fifth, and most consequentially, deal teams systematically underestimate the people dynamics. Key talent in the target leaves at higher rates than expected. Key talent in the acquirer also leaves at higher rates than expected. The integration team itself is under stress, and burnout in integration roles is common. Plans that do not have explicit retention, recognition, and rotation provisions tend to lose the integration team itself before the integration is complete.

The McKinsey life sciences insights have documented these patterns across multiple pharma post-merger integrations, and the BCG biopharmaceuticals practice has produced similar diagnostics. The patterns are not specific to one deal or one company; they are structural to pharma M&A.

Thing 1: Start Day-1 Planning Before Close, Not After

Day-1 readiness work — the set of activities that make the combined entity operationally functional on the first day post-close — should begin no later than the announcement of the transaction, not at close. The work includes identity and access management decisions, communication tool integration, email routing, shared file access for transition teams, security posture during the transition, and the legal and compliance frameworks under which combined operations will run.

The reason this matters: starting day-1 work at close means day 1 is also day 1 of the planning, and the gap is felt immediately. Employees on both sides cannot collaborate effectively, key meetings cannot be scheduled because participants cannot see each other’s calendars, file sharing requires workarounds, and the impression of a chaotic combined entity sets in within days. The impression matters; it shapes employee perception of whether the integration is being run competently for the next six months.

The pre-close work is constrained by the limits of what can be done before close (anti-trust, confidentiality, deal certainty). But within those limits, substantial preparation is possible. Identity and access design can be done in principle. Communication tool integration can be planned and tested in sandboxes. The legal frameworks for combined operations can be drafted. The integration team can be mobilized and given clarity about who they will work with at close. Done well, this work means day 1 looks operational; done poorly, day 1 looks improvised.

Thing 2: Inventory Validated Systems Before Touching Anything

The first substantive operational activity post-close should be a complete validated-systems inventory across the combined entity, with current validation status documented and any in-flight change activity captured. This work should be done before any integration activity begins on validated systems.

The reason is straightforward: validated systems are the hardest things to move and the most consequential to get wrong. Touching a validated system without first understanding its validation state risks producing changes that have not been validated, audit findings, and remediation costs that often dwarf the value of the change being attempted. The inventory work is the foundation that the rest of the validated-system integration is built on.

The inventory should include: system name, version, vendor, business owner, IT owner, GxP classification, validation status, last validation date, last periodic review date, planned changes in flight, and any open audit or inspection findings. The artifact should be maintained as a living document throughout integration, and the integration team should reference it any time a change to a validated system is contemplated. ISPE GAMP 5 provides the framework against which the inventory should be calibrated.

Thing 3: Stabilize Before Optimizing

The temptation in early integration is to begin optimizing — consolidating vendors, retiring duplicate systems, harmonizing processes — before the combined entity has stabilized. The temptation is understandable: synergies are usually a stated outcome of the deal, and optimization activity produces visible progress that signals the integration is moving forward.

The temptation should be resisted. Stabilization first, optimization second, in that order. Stabilization means: the combined entity is operationally functional, employees on both sides can do their jobs, day-to-day execution is not being disrupted, and the integration is not consuming so much organizational capacity that the underlying business suffers. Only when stabilization is achieved should optimization activity begin in earnest.

Optimization activity launched before stabilization tends to produce one of two failure modes. Either the optimization stalls because the underlying environment is too unstable to support the change, or the optimization succeeds but at the cost of operational disruption that exceeds the value of the optimization. In either case, the deal economics are degraded.

The discipline is to articulate stabilization criteria explicitly: which operational metrics must be at acceptable levels, which integration foundations must be in place, what the employee experience must look like. Until the criteria are met, optimization activity is deferred. The criteria do not have to be exhaustive; they have to be specific enough that the integration leader can defensibly say “stabilization is achieved” or “stabilization is not yet achieved” when the question arises.

Thing 4: Plan for the People Loss You Will Not Predict

Retention planning during integration typically focuses on the most visible senior leaders and the most obvious key roles. The retention pool is structured around them, and the expectation is that the rest of the organization will mostly stay. This expectation is consistently wrong.

The people loss that hurts most during pharma integration is rarely the senior leader who was already retention-planned. It is the mid-level validated-systems administrator who held institutional knowledge about why the QMS was customized a particular way, the senior data engineer who maintained the data flows that the analytics platform depended on, the regulatory affairs specialist who knew the inspection history. These people are not on the retention list, often leave during integration for reasons that are partially about the integration and partially about other factors, and their departure leaves operational gaps that are expensive to fill.

The remedy is to broaden the retention frame deliberately. Beyond the obvious senior roles, identify the institutional knowledge holders — the people whose absence would meaningfully degrade the integration’s ability to execute — and include them in the retention frame even when they are not in the formal leadership structure. The cost of doing this is modest; the cost of not doing it is often substantial.

Thing 5: Treat AI Assets as First-Class Integration Objects

Five years ago, AI assets in pharma integrations were rare enough that they did not need special treatment. Today, both sides of most pharma deals have meaningful AI assets, and these assets require dedicated integration treatment that generic IT integration playbooks do not provide.

AI assets need their own inventory, their own governance treatment, and their own integration plan. The inventory should capture each AI use case, the data it depends on, the validation status (particularly for GxP-touching uses), and the operational owner. The governance treatment should determine whether the combined entity’s AI governance framework can absorb the inherited AI assets directly or whether remediation work is required. The integration plan should sequence AI consolidation, AI governance harmonization, and any AI deployments that depend on combined data resources.

The risk of not doing this is twofold. First, AI assets that are not brought into a shared governance framework continue to operate under whatever governance they had pre-merger, which is often inconsistent and sometimes inadequate. Second, AI use cases that depend on data that is now split across legacy environments may degrade or fail entirely, with operational consequences that are not immediately visible. The FDA AI in drug development resources have become a reference point for how acquirers should think about inherited AI assets and their compliance posture post-close.

Thing 6: Resist Premature Vendor Consolidation

Vendor consolidation is one of the most visible synergy categories in pharma post-merger integration, and the temptation is to pursue it aggressively early in the integration. The temptation should be moderated. Premature vendor consolidation produces several reliable problems.

First, vendors that are being consolidated away know they are being consolidated and become difficult to work with during the transition. Service quality degrades, contract terms become less flexible, and the acquirer is at a disadvantage in any disputes that arise. Second, the team supporting the consolidated-away vendor is often demoralized during the transition, which produces both retention risk and execution risk. Third, the operational consequences of vendor consolidation often surface late and are then difficult to reverse. Validated systems that depended on the consolidated-away vendor may need to be re-validated against the new vendor’s offering, which is work that should have been planned but often was not.

The remedy is sequencing. Vendor consolidation should follow stabilization, should be sequenced based on operational risk rather than dollar value, and should be preceded by deliberate due diligence on the operational dependencies the consolidation will affect. Some consolidations are easy and should be done early; many consolidations are harder than they look and should be done later in the integration, when the combined operating environment is well-understood.

Thing 7: Build the Communication Cadence Before Day 1

Integration communication is consistently under-resourced. The integration leader has so many operational fires to manage that communication often defaults to whatever the corporate communications function produces, which is rarely calibrated to the granularity that integration audiences need.

The remedy is to design the communication cadence before close and to staff it as a dedicated workstream. The cadence should include: weekly all-hands updates for the integration team and immediate stakeholders, monthly broader updates for the entire combined entity, quarterly business reviews with the deal team and the executive leadership, and ad-hoc updates triggered by specific events (major milestones, significant changes, key personnel transitions).

Each of these touchpoints requires content, distribution, and follow-up. The discipline is to treat communication as a first-class workstream with dedicated resources, not as an overflow activity that gets squeezed in when other work is done. Integrations that do this well sustain organizational momentum through what is otherwise a draining 12 to 18 month period; integrations that do this poorly accumulate organizational fatigue that erodes execution capacity over time. The Harvard Business Review M&A coverage has documented this pattern across multiple integration contexts, including in life sciences.

What Will Still Be Hard Even If You Do All This

The seven recommendations above will materially improve the outcome of a post-merger IT integration. They will not make the integration easy. Several dimensions remain hard even when the integration is run well.

The combined entity’s culture will take longer to settle than any operational integration plan accommodates. Two cultures rarely merge into one; usually one culture dominates and the other is largely absorbed, with residual tension that can persist for years. The IT function’s culture is no exception, and the cultural dynamics shape execution in ways that operational plans cannot fully anticipate.

The board’s appetite for integration spend will erode as the integration proceeds. The first six months typically have substantial board patience for integration costs; the next six months see growing pressure to demonstrate synergies; by month 12, the integration is often expected to be self-funding through synergies even if the original plan called for ongoing investment. Integration leaders should anticipate this pressure and plan their spend trajectory accordingly.

The deal team that championed the integration will move on to other deals within 12 months of close, and the institutional memory of why specific deal commitments were made will erode. The integration leader will increasingly be operating without the deal team’s continuing engagement, which produces both freedom (less second-guessing) and challenge (less air cover when integration costs exceed plan).

The underlying business will continue to evolve during integration, and integration plans built against the pre-close business reality will need ongoing recalibration. A target company that looked one way during diligence may look meaningfully different 12 months later, both because of business evolution and because of what integration itself reveals. Integration plans need built-in mechanisms for recalibration; rigid plans tend to produce stress fractures.

The compounding payoff of doing this well across multiple deals

One final observation that has become clear across the four deals: the organizations that build genuine post-merger IT integration competency across multiple deals develop a compounding advantage. The playbooks improve with each deal. The integration team builds institutional knowledge that transfers across deals. The vendor relationships develop in ways that facilitate future consolidations. The cultural dynamics become better understood. The board’s confidence in the function’s integration capability grows.

For acquirers in pharma and adjacent life-sciences segments that anticipate multiple deals over a multi-year period, this compounding is itself a strategic capability worth building deliberately. The investment in the second deal is materially lower than the investment in the first, and the investment in the fourth deal is lower still. The acquirers that recognize this and build the post-merger IT integration function as a durable organizational capability — rather than as an ad-hoc team mobilized per deal — produce post-close outcomes that are systematically better than acquirers that rebuild the team and the approach each time.

The seven things above are the right things to do in any single deal. The compounding capability is the right thing to build across a portfolio of deals. The two together are what separate acquirers who consistently produce successful integrations from acquirers who consistently produce ones that disappoint.

References & Sources