Mergers and acquisitions

Merge two tech stacks without breaking the business

When two companies merge, their systems have to as well: identity and email, CRM, finance, data, online stores, integrations and security. This hub is a practical playbook for buyers, sellers, private equity firms and operators: what to inventory before you sign, what must work on Day 1, what to decide by Day 30, how to merge each layer and how to decide, system by system, whether to keep, merge, bridge or retire it.

Book a call about your merger

Open the calendar in a full page
Guides in this playbook12One per layer of the stack, plus the plans
Systems and platforms covered28Each shown with its logo
Plan tasks, Day 1 to Day 10018Counted from the plan page
Starter risks in the register13Illustrative ratings, to replace with yours
Who it is for

What each side needs from the tech

The same playbook, a different starting point depending on where you sit in the deal.

The stack

Two stacks, six layers to merge

Every acquisition brings the same layers together. Each row links to the guide for that layer.

Decision framework

Keep, 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 run an equivalent, and can you switch safely now?

  • Retire what is no longer used, after archiving its data.
  • Keep what has no equivalent on the other side.
  • Merge when both do the same job and switching is safe.
  • Bridge when switching is risky for now: connect, name an owner, set a review date.
Try the decision tool
KEEPNo equivalent on the other sideBRIDGESame job, risky to switch nowMERGESame job, safe to switchRETIRENo longer used: archive the data, then switch offOverlap with the other company's system →Cost and risk of switching →NoneSame job
Systems low on use go to Retire wherever they sit. Illustrative framework, not a measurement.

Where integration effort tends to concentrate, by layer

Illustrative score, 1 (light) to 5 (heavy). A planning judgement by Consultants in a Box, not measured data.

Show as table
ItemWhere integration effort tends to concentrate, by layer
Identity and email4
CRM4
Finance and ERP5
Data and analytics4
E-commerce4
Integrations3
Security4

Tasks in each checkpoint of the integration plan

Counted from the plan page

Show as table
ItemTasks in each checkpoint of the integration plan
Day 16
Day 306
Day 1006
Checkpoints

Day 1, Day 30, Day 100

Keep the business running first, decide second, move third. These are common checkpoints, not promises about how long your merger will take.

  1. Day 1

    Nothing breaks, and everyone knows where to go

    Confirm who can approve spend, access and system changes on both sides. Freeze non-urgent changes to core systems.

  2. Day 30

    A decision for every system

    Finish the stack inventory with an owner for every system. Mark each system keep, merge, bridge or retire, with the reason.

  3. Day 100

    The high-value moves are done

    Complete the identity and email moves agreed at Day 30. Cut over the first merged system and confirm users are on it.

See the full plan

Guides

The M&A tech stack playbook

One guide per topic, each with a chart, a table and the systems it covers.

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.

  • Google Workspace
  • Microsoft 365
  • Salesforce
  • HubSpot
  • NetSuite
Read the guide

Day 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.

  • Google Workspace
  • Microsoft 365
  • Microsoft Teams
  • Slack
  • Salesforce
Read the guide

Identity, email and tenants

Identity decides who can reach everything else, so it comes first. Pick a tenant strategy, then move mail, files and chat in an order that never leaves people locked out.

  • Google Workspace
  • Microsoft 365
  • Microsoft Entra ID
  • Okta
  • Microsoft Teams
Read the guide

CRM merge

A CRM merge is mostly a data-quality and ownership project. Merging records is the easy part; deciding what a customer is, who owns them and which fields survive is where the time goes.

  • Salesforce
  • HubSpot
  • Microsoft Dynamics 365
  • Make
  • Zapier
Read the guide

ERP and accounting

Finance cannot pause. Keep both sets of books running through the first closes, agree one chart of accounts for reporting, and move to a shared system only when the close process is stable.

  • NetSuite
  • QuickBooks
  • Xero
  • Sage Intacct
  • Stripe
Read the guide

Data and analytics

The warehouse is rarely the hard part. Agreeing what a customer, an order and revenue mean in both companies is.

  • Snowflake
  • Google BigQuery
  • Databricks
  • Amazon Redshift
  • Fivetran
Read the guide

E-commerce platforms

Merging stores risks the two things that are hard to rebuild: search rankings and customer trust. Plan redirects, accounts and payments before the first product moves.

  • Shopify
  • WooCommerce
  • BigCommerce
  • Stripe
  • NetSuite
Read the guide

Integration patterns and iPaaS

You will not merge everything on Day 1, so you will bridge. A bridge you design (owners, logging, an end date) is an asset. One built from forgotten zaps is a risk.

  • Make
  • Zapier
  • MuleSoft
  • Workato
  • Boomi
Read the guide

Security and compliance

An acquisition changes the scope of what you must protect and prove. Carve the new company in on purpose: close the access gaps first, then extend the programme.

  • Okta
  • Microsoft Entra ID
  • Google Workspace
  • Microsoft 365
Read the guide

Synergy capture

Tech savings are real but smaller and slower than deal models often assume. Count the one-time cost to capture them, and size them with your own contract numbers.

  • Google Workspace
  • Microsoft 365
  • Slack
  • Microsoft Teams
  • Salesforce
Read the guide

Risk register

Most integration failures are predictable. A risk register makes them visible early, with an owner and a mitigation each.

  • Google Workspace
  • Microsoft 365
  • Salesforce
  • NetSuite
  • Shopify
Read the guide

Keep, 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?

  • Salesforce
  • HubSpot
  • Shopify
  • WooCommerce
  • QuickBooks
Read the guide
Bridging

Platforms that connect the two stacks while you decide

Read the integration guide before choosing one. See also our workflow automation and Migrate to Make pages.

  • Make
  • Zapier
  • MuleSoft
  • Workato
  • Boomi
FAQ

Questions about merging tech stacks

What does it mean to merge tech stacks?

Bringing two companies' systems into one working environment: sharing identity and email, one view of customers and finance, connected data, and one security baseline. Not every system has to become one; some are kept or bridged.

What should happen before the deal closes?

Technical due diligence: an inventory of systems, owners, contracts, data and access, with the red flags that change the price or the plan. Counsel handles the legal questions.

Should we merge everything onto the buyer's systems?

No. Choose the system that fits the combined company. The decision framework on this hub helps you decide system by system.

How long does an integration take?

It depends on the size of the companies and the number of systems. Day 1, Day 30 and Day 100 are common checkpoints, not promises. Plan the first moves, and put a dated plan on everything else.

Do you give legal, tax or accounting advice?

No. We plan and run the technology side. Bring your own lawyers, accountants and auditors for deal terms, tax, accounting treatment and audit scope.

Are the numbers on these pages statistics?

No. Charts that show effort or priority are illustrative planning scores, and each says so. We have not published studies or client results here.

Consultants in a Box is an independent consultancy. This hub is not published or endorsed by any vendor named, and names and logos are trademarks of their owners. It is general planning guidance, not legal, tax or accounting advice. Last reviewed . Illustrative scores are labelled as such; we have not published client results or statistics here.

Merging two companies' systems?

Start with the free business analysis, or book a call and we will talk through both stacks 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.