elevate techConsulting Group

Technology integration after an acquisition

IT due diligence checklist for buying a company

IT due diligence on a company you are buying should cover seven areas: a complete systems inventory, contracts and licenses, dependencies on a parent or key person, security and backups, data quality, technical debt, and the cost to integrate or to stand alone. The inventory comes first, because everything else depends on knowing what exists.

Financial diligence tells you what the company earned. Technology diligence tells you what it costs to keep earning it under your ownership. The two often differ, especially in carve-outs, where the systems may belong to someone else. Use this checklist before you sign, and use the findings to shape the plan in the first 100 days of technology integration. Our wider approach is on the technology integration after an acquisition page.

What is IT due diligence?

IT due diligence is a review of a target company's systems, contracts, data, security and people, done before you sign, to find what the deal will cost to integrate or run on its own. It is the technology counterpart to financial and legal diligence. The questions are practical: what does the company run on, who owns it, what happens to those systems and contracts when ownership changes, and what will it take to run the business under yours?

Done well, it changes the price, the structure or the plan. It is cheapest to do before the letter of intent is final, while those findings are still negotiable.

Why does the systems inventory come first?

You cannot judge risk in systems you have not found. Sellers are usually honest about the systems they remember. The trouble is what nobody remembers, or what someone else owns.

On a pro audio carve-out, the work to separate the business from its parent started with a count. It came to 179 systems and 15 entities, all owned by the parent, with a fixed deadline. A business that thought of itself as running a handful of core applications turned out to depend on a very long list. The price of the deal, the timeline and the stand-alone budget all depended on that list. Get the list early.

Ask the seller for, and then verify:

What should you check in contracts and licenses?

Read the agreements behind the systems, not just the systems.

Put the results in a table with the end date, the annual cost and the risk. You will use it again after closing.

What dependencies on a parent or a key person exist?

Two kinds of dependency cause the most trouble. The first is a parent company: shared systems, shared services, a shared network, shared licenses and shared people. In a carve-out, a transition services agreement may cover these for a while, but only for what is listed in it. The second is a key person: the one individual who knows how the order system works, holds the passwords or built the integration.

Ask who would be impossible to replace, and where their knowledge is written down. Ask what in the business stops if a named person leaves. A plan to retain and document that knowledge is a cheaper protection than any insurance.

Before the deal closes, you should also know how your own systems will handle another company. See where you stand.

Take the Systems Check

What should you check on security and backups?

You are buying the target's risk along with its revenue. Ask for plain evidence, not assurances.

For healthcare and other regulated targets, add the rules that apply to the data. An experienced reviewer can do a fast, practical pass without a full security audit.

How good is the data?

Data quality shows up later as integration cost. Sample it. Look at customers, items, vendors and open orders in the main system and ask how many are duplicates, out of date or incomplete. Ask whether numbers in the management reports can be traced to the underlying records. If the seller cannot reproduce a figure from its own system, the figure is an opinion.

What technical debt are you inheriting?

Technical debt is the cost of earlier shortcuts: old software that is no longer supported, custom code nobody understands, workarounds that have become the process. Ask which systems are at or near end of support, which customizations the company cannot maintain, and which processes depend on manual steps. List the items you would fix and give each a rough size: small, medium, large. Do not pretend to precision that the evidence cannot support.

What will it cost to integrate or stand alone?

Every deal ends up in one of two places. Either the target is integrated into your systems, or it stands alone on its own. Estimate both, in plain ranges, with the internal time included.

AreaIntegrate into your systemsStand alone
Finance and ERPMigrate to your platformKeep or replace the target's own
Licenses and contractsTerminate or reassignRenew, split or re-buy
People and knowledgeRetrain on your toolsRetain the key person, document the system
DataClean, map and mergeClean enough to report from
SecurityBring under your controlsBuild or buy your own
TimelineSequenced after day 100Set by any transition services deadline

A transition services agreement from a parent sets a clock. The consumer products team on the carve-out plan engagement used a three-week assessment to produce a twelve-month transition plan and budget, and the deal closed.

What do buyers find most often?

The same handful of surprises show up again and again, in our experience. Systems nobody listed because a parent or a department owns them. Contracts with change-of-control or assignment terms that let a vendor reprice or terminate. One person who holds the knowledge of how the order system works. Backups that exist but have never been restored, and administrator access nobody has reviewed. And data that two systems disagree about, so a reported figure cannot be traced to its source.

None of these is exotic. Each one is cheap to find before closing and costly to find after.

What belongs in an IT due diligence questionnaire?

Keep the questionnaire short enough that the seller answers it, and ask for documents, not assurances. Cover six groups: a full inventory of applications, spreadsheets and databases with their owners; every software and service contract with term, renewal and change-of-control language; who has administrator access and whether multi-factor authentication is on; backup and restore evidence; any security incident and what was done about it; and the IT team, outside providers and key people, with where their knowledge is written down.

Add questions on data: how many duplicate or stale customer, item and vendor records exist, and whether management reports trace back to the system. Then verify a sample yourself. The checklist above turns each group into specific requests.

How do you turn the findings into action?

Sort the results into three groups. Items that change the price. Items that change the timeline or the structure of the deal, such as a license that cannot be assigned. And items that go on the post-closing plan. Share the first two with the deal team before signing, and carry the third into the first 100 days. If the target runs on something like a multi-location operation, mismatched point of sale and accounting is one of the first things worth testing.

Common questions

How long should technology due diligence take?

It depends on the size of the target and how much access you get. A focused review of a company of this size can be done in a matter of weeks. The limit is usually how quickly the seller provides systems lists and contracts.

What is the most common thing missed in technology diligence?

Systems and contracts that sit outside the target's own IT team: tools owned by a parent, departments buying software on their own, and agreements that change when ownership changes.

What are change-of-control clauses?

Contract terms that let a vendor renegotiate, charge a fee or terminate when the company is sold. They are often found in software licenses and service agreements, so every key contract needs to be read for them.

Do you need technology diligence on a small deal?

Yes, scaled to the deal. Even a short review of systems, contracts, security and key people can change the price or the plan. The cost of a surprise after closing is usually far higher than the review.

Not sure where to start?

Take a free three-minute score. If a conversation makes sense, it will offer one.