Tech integration risk register and common failure modes in M&A
Most integration failures are predictable. A risk register makes them visible early, with an owner and a mitigation each.
Keep one register for the whole integration. For each risk record what could go wrong, how likely and how costly it would be, who owns it and what you will do. The ratings below are our illustrative planning judgement for a typical small or mid-size deal. Replace them with your own as soon as you have the inventory.
Google Workspace
Microsoft 365Salesforce
NetSuiteShopify
Likelihood by impact
Impact
Likelihood (illustrative ratings)
What are the most common failure modes?
Losing access, losing customers or revenue records, and losing people. Technology problems rarely sink a deal; unowned decisions do.
- No single owner for the integration.
- Migrating too many systems at once.
- Changing systems around a close or a peak sales period.
- Decisions made by seniority instead of fit.
How should the register be used?
Review it weekly in the first months, move risks as they change, and close them only with evidence.
- Assign one owner per risk.
- Rate likelihood and impact using your own judgement.
- Review the top risks in the weekly integration meeting.
- Record what you did and the result.
Questions on this topic
Are the ratings facts?
No. They are illustrative starting points from our planning experience, not measured statistics. Rate your own.
How many risks should we track?
Enough to cover each workstream, with the top few reviewed weekly. A short, current register beats a long stale one.
Who owns the register?
The integration lead, with a named owner for each risk.
Vendor documentation to check against
Product details change. Confirm current options in each vendor's own documentation. Consultants in a Box is an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.
Related guides
Technical due diligence
Before the deal closes, build one inventory of what the target runs, who owns it, what it costs and what it is tied to. Every later decision, keep, merge, bridge or retire, starts from that list.
Read the guideDay 1, 30 and 100 plan
Integration goes wrong when everything is urgent. Split the work into three checkpoints: keep the business running on Day 1, make the decisions by Day 30, and complete the moves by Day 100.
Read the guideKeep, merge, bridge or retire
Every system in the inventory ends up in one of four places. Three questions decide which: is it still used, does the other company have an equivalent, and can you switch safely now?
Read the guideAll M&A tech stack guides
The full playbook, from diligence to synergy capture.
See the hubMerging two stacks?
Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.
