Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two colleagues at a whiteboard covered in technical diagrams in a glass-walled meeting room

IT due diligence in an acquisition: what to request and what you only see when you look further

IT due diligence is the part of a deal where the data room tells you least. A three-year-old network diagram, a licence list without end dates and the line “backups run daily” say little about what you are buying. This is what we request, what we look at next, and what the first hundred days after completion look like.

8 min read Written by the ITproposal team
Short answer

IT due diligence is not about whether the IT is tidy, but about what you will have to do after completion and what that costs in time and risk.

The questions that matter most are about ownership and dependency: who holds the admin accounts, whose name the domain is in, and what happens if one person or supplier disappears.

We provide the technical part. Valuation, legal review and the financial books belong with your M&A adviser, solicitor and accountant.

What IT due diligence is, and what it is not

IT due diligence is the technical review of the IT of a business you are acquiring or investing in. It runs alongside the financial, legal and tax work and answers a narrower question: what are you taking on, what is worth keeping, and what has to happen after completion.

It is not an audit that grades the IT team, and it is not a certification. An environment can be untidy and still carry little risk; a tidy one can depend entirely on a single outside administrator who will not stay after the deal.

There are two moments. Before signing you work with what the seller puts in the data room and a few conversations. After completion you get access and see how things really stand. Good due diligence knows which part it has not yet seen and puts that explicitly on the list for the first weeks.

What to request

Do not ask for “an overview of the IT”. Ask for documents and exports you can put side by side:

  • Network diagram and inventory. Sites, connections, firewalls, wifi, servers and endpoints, with their age and whether they still receive updates. An up-to-date IT asset register is worth more than anything else here.
  • Contracts and licences. Every supplier with term, notice period and end date, and for each licence whose name it is in. Check for terms that change or lapse on a change of control; they are in the supplier’s conditions, and interpreting them is a job for your solicitor.
  • Security incidents. What has happened in recent years, what was reported to the ICO, and what changed afterwards. A business with no incidents on record more often has no records than no incidents.
  • Backup and recovery. What is backed up, where it is stored, whether there is a copy an attacker cannot delete, and when something was last actually restored.
  • Ownership of domains and accounts. Whose name the domains, DNS, the Microsoft 365 tenant and the cloud subscriptions are in, and who holds the admin accounts.
  • Dependency on one person or supplier. Who knows how it works, and what happens if that person or company is gone tomorrow.
  • Technical debt. Systems that no longer receive updates, undocumented customisation, and postponed replacements that become your bill after the deal.
  • Data processing under UK GDPR. The record of processing, the data processing agreements with suppliers, and where personal data physically sits.

What you see when you look beyond the data room

Documents describe how things should be. An hour in the admin consoles shows how they are. If the seller allows it, ask for a shared screen rather than more documents, and look together at:

  • Who has admin rights. How many global administrators there are, whether former staff or outside parties are among them, and whether they sign in with multi-factor authentication.
  • The last successful restore test. Not the backup report with green ticks, but the date someone actually restored a file or server.
  • Patch status. How many devices are behind, and which systems are deliberately not updated because “it breaks the application”.
  • The invoices of recent months. They reveal subscriptions that appear in no overview.

Talk to the people who run it day to day as well as to the directors. The question “what would you do if you had budget tomorrow?” often produces the most honest list of technical debt.

Red flags

Not every mess is a problem. These are the things we always call out separately, because they create work or risk straight after completion:

  • The domain or tenant is in the name of an individual or an outside party. Getting it back can take weeks, and until then you have no control over your own email.
  • One administrator knows every password, with no vault and no second account.
  • No restore has ever been tested. Then nobody knows whether the backup works.
  • Core systems run on software that no longer receives security updates, with no plan to replace it.
  • An incident was resolved but never investigated. You do not know whether the attacker still has access.
  • There are no data processing agreements, or personal data sits with a supplier nobody can place.
  • Long-running contracts that do not fit how you intend to run IT.

A red flag is rarely a reason not to buy. It is a line in the integration plan and sometimes a point for negotiation; how much weight it carries is for you and your advisers to decide.

Integration after completion

The first decision is organisational, not technical: do you merge the IT, or does the acquired business keep running on its own? Merging gives you one way of managing and one security baseline, but it costs a migration. Keeping it separate is faster, but you inherit two environments that both have to be managed and secured.

If you are buying part of a larger company, its IT often still runs on the seller’s systems. Agree in a transitional services agreement which services the seller keeps providing, for how long, and what is handed over at the end. Without it, you can find yourself without email or ERP on completion day.

Whatever the route, the integration plan covers the order of migrations (identity and email first, applications after), which contracts are terminated or taken over, how staff will notice the change, and when the old environment is actually switched off.

The first hundred days

Day one. Make sure your organisation holds the admin accounts, that departing administrators and outside parties have lost their access, and that multi-factor authentication is on for every administrator. Move the domains into the right name. This is the one step that cannot wait.

The first thirty days. Complete the inventory with what you can now see, test a restore of the most important systems, and measure the security baseline against your own: patching, password policy, endpoint protection, logging. Whatever you could not check during due diligence, check now.

Days thirty to a hundred. Agree the integration plan, start the identity and email migration if you are merging, terminate redundant contracts within their notice periods, and put the data processing agreements in order. Tell the acquired business’s staff where to go with IT questions; uncertainty about that is the biggest source of frustration in the first months.

Where our work stops

What we do. We provide the technical part of IT due diligence: the inventory, the look inside the admin consoles, the list of red flags with the work each one means after completion, and then the integration plan and its delivery, from day one to the last migration. We are certified to ISO 9001 and ISO/IEC 27001, and that describes how we work, not a verdict on the business you are buying.

What we do not do. We are not an M&A adviser, a solicitor or an accountant. We do not value businesses, review sale and purchase agreements or warranties, assess whether a licence or contract can legally be transferred, or examine the books. Our findings are input for those advisers, and they decide what they mean for price and terms.

Frequently asked

Questions we get about this

The five that come up most often.

What is IT due diligence?

IT due diligence is the technical review of the IT of a business you are acquiring. It maps what you are taking on, where the risks are and what has to happen after completion. It runs alongside the financial and legal review and does not replace it.

What should an IT due diligence checklist include?

A network diagram and inventory, every IT contract and licence with end dates, recent security incidents, the backup set-up and its last restore test, and who owns the domains, the tenant and the admin accounts. Add dependency on any single person or supplier, technical debt, and data processing with its agreements.

What are the biggest red flags in IT due diligence?

A domain or tenant in the name of an individual or outside party, one administrator who knows every password, a backup that has never been restored, and core systems without security updates. An incident that was fixed but never investigated also belongs on the list. They are rarely reasons to walk away, but they are lines in the integration plan.

What should happen to IT in the first 100 days after an acquisition?

On day one, take over the admin accounts, remove access for departing administrators and turn on multi-factor authentication. In the first thirty days, complete the inventory and test a restore. After that, agree the integration plan, start the identity and email migration and terminate redundant contracts.

Do you review the sale and purchase agreement?

No. We are not an M&A adviser, solicitor or accountant, and we do not value businesses or review contracts legally. We provide the technical part: what is there, what the risk is and what it takes after completion. What that means for price or terms is for your own advisers.

Related services

Further reading

Where this review connects.

An acquisition on the table? Let us look at the IT

Tell us what you are acquiring and what you have received so far. We will say what is still missing, what we would look at first and what the first hundred days look like; the legal and financial side stays with your advisers.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call