M&A tech stacks

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.

Short answer

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 365
  • Salesforce
  • NetSuite
  • Shopify

Last reviewed . General planning guidance, not legal, tax or accounting advice.

Risks in the starter register, by category

Counted from the register below.

Show as table
ItemRisks in the starter register, by category
Identity2
Customers2
Finance2
Commerce2
Data1
Contracts1
People1
Integration1
Security1

Likelihood by impact

Impact

1risk
8risks
0risks
0risks
1risk
2risks
0risks
0risks
1risk
LowMediumHigh

Likelihood (illustrative ratings)

HighMediumLow

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.

  1. Assign one owner per risk.
  2. Rate likelihood and impact using your own judgement.
  3. Review the top risks in the weekly integration meeting.
  4. Record what you did and the result.
FAQ

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.

Merging two stacks?

Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.

Book a free consultation

Tell us about your team and the software you need help with. We'll follow up to schedule a time to talk.

Open the form on its own page

Talk to a person

The fastest way is to pick a time. Prefer to write? Leave a message and we will email you back, usually the same business day.

Book a free call

By sending this you agree to our Terms and Privacy Policy.