In an acquisition, the information system is rarely in the spotlight. Yet it determines business continuity, the cost of the first hundred days and part of the deal value. IT due diligence is not about perfection: it puts facts on the table so you can negotiate and plan.
1. Mapping and dependencies
Which applications are critical, who hosts them and who maintains them? Even a rough map quickly reveals the weak spots: an ageing business application whose vendor is no longer active, an in-house tool only one person understands, a single provider for managed IT services.
2. Contracts and licences
Review the contracts with key software vendors and providers: change-of-control clauses, termination terms, data reversibility. Check that the licences in use match the licences purchased. A gap can turn into an invoice after signing.
3. Cybersecurity posture
A few questions are enough to gauge the level. Are backups tested and isolated? Does multi-factor authentication protect sensitive access? Have there been incidents, and how were they handled? An undetected past compromise becomes your problem on takeover day.
“A target’s cyber risk becomes yours on closing day.”
4. Regulatory compliance
For the GDPR, the record of processing activities is a good place to start: whether it exists, and how well it is kept, says a lot. Also check whether the target, or the combined entity after the deal, falls within the scope of NIS2 (see our NIS2 note).
5. Key people and organisation
Who holds the administrator access, the passwords, the knowledge of past decisions? Dependence on one or two people is common in SMEs. It is addressed through documentation, knowledge transfer and sometimes retention measures.
6. Technical debt and future investment
Hardware at end of support, unpatched systems, upgrades that keep being postponed: each one is a future investment. Better to identify it before setting the price.
7. Integration or separation
If the target is being carved out of a group, which IT services will the seller keep providing, and for how long? If it is to be integrated, which systems will be kept, migrated or retired? The answers feed directly into the hundred-day plan.
In practice
Effective IT due diligence combines document review, interviews with the teams and a few targeted technical checks. The expected deliverable is simple: a prioritised list of risks, their estimated impact and the points to bring into the negotiation.
Preparing an acquisition? Let’s talk about your timeline.




