---
title: "Post-acquisition integration of teams and systems | QMates"
source: https://qmates.tech/en/services/engineering-transformation/software-delivery-assessment/post-acquisition-integration
description: "The longer post-acquisition integration waits, the further the teams drift apart and the more knowledge of the acquired system walks out. Do it in stages."
updated: 2026-11-21
---

Post-acquisition integration

# We acquired a company, and the two teams still work separately

After an acquisition the first instinct is to migrate everything onto the acquirer’s stack, the most visible difference, and a rushed migration breeds resistance and scatters the knowledge held in the acquired system. Meanwhile the two ways of working stay unknown, the acquired system’s debt hasn’t been mapped, the two systems have no clear boundaries and the teams stay divided by company of origin.

## Does this sound familiar?

-   The two teams work on different stacks and only collaborate when a deadline forces them to.
-   The two systems don’t talk to each other, and the same data lives in two places with different values.
-   The acquired company’s technical debt has turned out bigger than what came up in due diligence.
-   The acquired company’s developers are starting to leave, and the knowledge of the system goes with them.
-   Nobody has yet decided what to unify, what to keep separate and what to retire.

## Where does the stall after signing come from?

After signing, everyone looks at the stack first, and the plan starts from there. You unify in a hurry, before knowing how the two sides work, where the boundaries between the systems run and how much debt the acquired one carries. The consequence that lasts longest shows in the teams, still organised as they were before signing.

1.  ### Two ways of working nobody has seen up close

    Code, practices, release process and team structure differ from one company to the other, and the integration plan gets decided by looking only at the code. Before choosing what to unify you need to know how each of the two organisations works and where its work stops.

    Feeds into

    -   

    [

    Handled by

    Software Delivery Assessment](https://qmates.tech/en/services/engineering-transformation/software-delivery-assessment)

2.  ### Everything unified, and straight away

    Migrating everything onto the acquirer’s stack without a plan creates resistance and scatters the knowledge held in the acquired system. Merging in stages, one part at a time and protected by tests, keeps the product running while it changes.

    Feeds into

    -   

    [

    Handled by

    Legacy Code Refactoring](https://qmates.tech/en/services/engineering-transformation/legacy-code-refactoring)

3.  ### No clear boundaries between the two systems

    When the same word, customer or contract, means different things in the two systems, every integration becomes a translation done by hand. Starting with the domain boundaries and with clear interfaces between the systems lets you get them talking early and decide later which parts to merge.

    Feeds into

    -   
    -   

    [

    Handled by

    Domain-Driven Design and EventStorming](https://qmates.tech/en/services/engineering-transformation/domain-driven-design-event-storming)

4.  ### Two companies, still two org charts

    After the acquisition the teams stay divided by company of origin, and every feature that touches both systems needs them coordinated. Uncertainty about roles and responsibilities does the rest, and the people who know the acquired system best are often the first to look around.

    [

    Handled by

    Engineering Team Design](https://qmates.tech/en/services/engineering-transformation/engineering-team-design)

5.  ### The acquired system’s debt hasn’t been mapped

    Nobody has yet looked at the acquired system as a whole, and without a map of its technical debt every unification is risky: you don’t know which parts can take a migration and which would make it expensive. Knowing where debt holds back changes lets you choose what to unify first.

    Feeds into

    -   

    [

    Handled by

    Technical Debt Assessment](https://qmates.tech/en/services/engineering-transformation/technical-debt-assessment)

- [The service that tackles it](https://qmates.tech/en/services/engineering-transformation/software-delivery-assessment)

## What changes when the two companies start working as one

The two systems talk to each other through clear interfaces, and what to unify is decided part by part, on the basis of what the data shows. The product keeps growing while the integration goes ahead.

Every new feature finds a team that owns the part of the product it touches, and the answer no longer depends on which company people came from. People who know the acquired system work inside one of those teams, with a clear role in the plan.
