1. Why IT is a critical node in M&A
In a merger or acquisition, the IT infrastructure is often considered only at the end, when the work on finance and contracts is already well advanced. Yet without email, access, business systems and shared data the two companies cannot operate together. Delays on the IT side slow down the benefits the deal was meant to deliver and increase operational risk, because the systems of two organisations must coexist for months before they are unified.
The main problem is that the acquired company brings with it systems, contracts, licences and risks that are often undocumented. A preliminary check, known as technical due diligence, shows what really exists, which systems are critical, which licences are transferable and which vulnerabilities are already present before integration. Discovering these elements after signing costs far more than discovering them beforehand.
2. Technical due diligence: what to check
IT due diligence should cover the inventory of assets, identities and access, supply contracts, software licences, the status of backups and recovery plans, and reports of past incidents. The aim is not to judge the company, but to estimate integration costs and timescales with reasonable accuracy, and to identify the points that need specific negotiation.
One point that is often underestimated is ownership of domains, certificates and administrative accounts. Who holds the domain names, the certificates and the privileged credentials? If this information rests with a single person or with a supplier that is leaving, the integration stalls at the first problem, and the renewal of an expired certificate can halt entire services at the least convenient moment.
3. Active Directory domains: merge, separate or coexist
There is no single route. The choice depends on the size of the two structures, how quickly integration is needed and the acceptable level of risk. The table summarises the four most frequent scenarios, which can also be combined over time, for example starting with coexistence and moving to unification in phases. Each step should still be documented with the same care, because it changes the permissions users see every day.
Many operations begin with controlled coexistence, using trust relationships between domains, and move to unification only once the services are stable. Any scenario requires a precise inventory of service accounts, of applications that authenticate against Active Directory and of sensitive permissions. Changing the structure without mapping these dependencies causes outages that only surface when a business application stops working, often on a Friday evening.
| Scenario | What it involves | Main risk |
|---|---|---|
| Coexistence with trust relationships between domains | The two structures remain separate, with controlled cross-access | Management complexity and cross-permissions that are hard to follow |
| Migration of users and groups to a single domain | Centralised access management after profiles are migrated | Duplicate accounts and permissions that break |
| Full restructuring of the forest | Redesign of organisation and management policies | Long timescales and impact on all services |
| Progressive integration by site | Migration of user groups in successive phases | Prolonged coexistence and uneven security levels |
4. Data migration and privacy obligations
Moving data between branches or between two companies carries responsibilities under the GDPR. If personal data of customers or employees changes controller or purpose, you need to clarify the legal basis, update the notices and keep the record of processing activities aligned. This also applies to employee data transferred to a new structure, which employees have a right to know about: who processes their information and for what purpose.
From a technical point of view, migration should be planned with full copies before each step, spot checks and a controlled period of coexistence. Sites with slow links need a different approach, with overnight windows and progressive data synchronisation. Each phase should have a verifiable completion criterion, for example the number of records compared and the outcome of access tests, before moving on to the next.
5. Security and compliance during integration
During an extraordinary operation the attack surface grows: new users, new devices and new connections between networks. Fraudsters often exploit these moments, with emails from fake suppliers or urgent requests to change bank details. Clear rules are needed for communications and for every change to payment details, with verification through a channel different from the one the request came through, for example a phone call to a number already known.
If one of the companies falls under NIS2 or DORA, or provides regulated services, its risk management and notification obligations may change after the deal. Check with your lawyer which obligations remain, which are added and from what date. Customer contract clauses may also require specific communications in the event of a change of control, and must be read before any systems are touched.
6. Getting started: the map comes first
The first useful step is a technical map of the target company, to be completed before signing or immediately afterwards, with the agreement of the parties. The map shows what exists, what depends on what and where the highest risks are concentrated. It should be shared with management and with legal advisers, because decisions on timing and methods of integration depend on both.
Once the map is ready, the integration plan can be discussed with those responsible in both companies. An IT provider with experience of similar operations can help you estimate the phases, but decisions on compliance and contracts remain with management and legal advisers. A written plan, with criteria for moving between phases, is the tool that makes the integration controllable.
- Request an inventory of systems, licences, IT contracts and suppliers of the target company.
- Map identities and domains, including the owners of domains, certificates and administrative accounts.
- Identify critical systems and their dependencies on Active Directory.
- Verify backups and recovery plans of the acquired company.
- Define communication rules to prevent payment fraud and urgent requests.
- Set an integration sequence in phases, with clear criteria for moving to the next one.
Frequently Asked Questions
When should the IT department be involved in an M&A deal?
As early as possible, ideally already during due diligence. Involving it only after signing reduces the opportunities to negotiate costs, liabilities and timescales. Even a light technical check before the agreement can bring to light non-transferable licences or vulnerable systems that affect the price.
Can Active Directory be unified without stopping work?
In many cases yes, through a progressive migration, agreed maintenance windows and testing of the services that depend on the domain. It does require accurate mapping of accounts, permissions and connected applications. A unification done in a hurry is one of the most frequent causes of disruption during integrations.
Can customer data be transferred to the new company?
It depends on the original notices, the purposes and the legal basis for processing. A change of controller or a transfer between companies within the group should be assessed with a privacy consultant. Do not assume the transfer is allowed: first check what customers have authorised and what the record of processing activities provides for.
What happens to software licences after an acquisition?
It depends on the contract. Some licences are tied to the company that bought them and do not transfer automatically; others include special conditions in the event of a change of control. Ask for a list of licences with their transferability terms, and plan renewals before you unify the environments.
How long does an IT integration take?
There is no standard duration. It depends on the size of the companies, the number of systems, the complexity of the integrations and the speed the business requires. It is better to define phases with measurable objectives and passing criteria, rather than fixing a single completion date.