Post merger software integration start: the first moves.

A disciplined post merger software integration start plan is the difference between a first hundred days that protect the combined business and one that quietly creates the next audit exposure. The instinct after close is to chase synergies fast: cut duplicate tools, consolidate platforms, and show savings. That instinct, acted on too early, is exactly how a careless integrator breaches licences and triggers a true up. Knowing where to start post merger software integration is therefore not about cost cutting at all. It is protecting what both companies already hold, building a single picture of the combined estate, and only then moving on the savings that the picture reveals. This guide sets out the first moves in sequence, from day zero to day one hundred.

Post merger software integration start: protect entitlements first

The first phase, in the opening fortnight, is to stabilise and protect entitlements. Both companies arrive with their own licences, their own deployments, and their own compliance positions. The danger on day one is that integration enthusiasm pushes usage across boundaries: staff from one entity gain access to software licensed only for the other, and deployment quietly drifts beyond entitlement. That drift is the seed of an audit finding. Before anything is combined, the integration team confirms what each company is entitled to and freezes any change that would expand usage beyond it. The risk of getting this wrong is set out in integration and the risk of accidental over deployment. Only once entitlements are protected does the work move to building the combined inventory.

Build the combined inventory before you cut anything

The second phase, across the first six weeks, is a single inventory of the combined estate: every publisher, every contract and its key clauses, every deployment, and every renewal date. Two companies almost always overlap, holding separate agreements with the same major publishers on different terms, different metrics, and different renewal cycles. Without one combined view, the integration team cannot see where the double spend is, cannot tell which contract offers the better terms to consolidate onto, and cannot anticipate the renewals that are about to land. The inventory is the foundation for everything that follows, which is why it precedes any consolidation decision. The structure of that combined view is described in the integration roadmap for the software estate, and the inventory is the input that roadmap is built from.

Take the quick wins, then plan the rest

The third phase, from roughly day thirty, is to capture the savings that are safe to take early. These are the overlapping software as a service subscriptions, the duplicate point tools, and the contracts approaching renewal where the combined business no longer needs both. Cutting these is low risk because it reduces usage rather than expanding it, and it shows the deal sponsors early progress. The deeper savings, consolidating two major platform agreements into one, renegotiating from combined volume, and rationalising an application portfolio, are not quick wins and should not be forced into the first hundred days. They belong on a sequenced roadmap that uses the combined volume as leverage at the right renewal moment. The mechanics of cutting the overlap are covered in eliminating double software spend after a merger.

Why true up risk is the trap to avoid

The single most expensive mistake in early integration is triggering a true up. A true up is the back charge that lands when a publisher finds that combined usage of its product has run beyond the licensed entitlement. Mergers create the conditions for it: two estates combine, usage rises, and the metrics that govern entitlement, whether users, cores, or revenue based bands, are crossed without anyone reconciling them. The major audit publishers, Oracle, SAP, Microsoft, IBM, and increasingly Broadcom following its VMware acquisition, watch for exactly this moment, because a merger is a natural prompt to audit. Avoiding the true up means reconciling entitlement against deployment for each major publisher before integrating their estates, which is why protection and inventory come before consolidation. The detail of that risk and how to manage it is set out in post merger true up risk and how to avoid it. The wider context is that inherited software licensing exposure is usually latent and unquantified, and integration is the moment it surfaces unless the team gets ahead of it.

Who owns the first 100 days

A plan with no owner drifts, and software integration drifts faster than most because it sits between functions. Procurement sees the contracts, IT sees the deployments, finance sees the spend, and no one sees the whole picture unless someone is made accountable for it. The first move on day one is therefore not technical at all: it is naming a single owner for the combined software estate, with a mandate that spans both companies and authority to freeze changes that would expand usage beyond entitlement. That owner runs the inventory, signs off the quick wins, and holds the consolidation roadmap. Without that accountability, entitlements get breached by well meaning teams who never knew the boundary existed, and the savings the deal promised slip because no one is driving them. The governance model that supports this ownership is set out in building a combined software governance model, and it is worth standing up early rather than retrofitting it once problems appear.

A worked example

Consider an anonymised composite: a private equity backed software group integrating a 1,200 employee acquisition into a platform of similar size. The integration team wanted a fast synergy number and proposed migrating all acquired staff onto the platform company productivity and database tooling in the first month. A combined inventory, built before any migration, showed that the platform company database licensing was metered by processor cores and was already close to its entitlement, while the acquired company held a separate agreement with room to spare. Migrating everyone onto the platform agreement would have pushed it well past entitlement and exposed the group to a large true up at the next audit. The team instead protected both entitlements, took the genuine quick wins on overlapping subscriptions worth a meaningful annual saving, and put the database consolidation on the roadmap for the next renewal, when combined volume gave them leverage to renegotiate rather than back pay. The lesson for buyers is that the fastest path to savings runs through the inventory, not around it.