Merging two teams fails on people, not process. The three things that decide it are communication, shared systems, and whether both sides feel equally involved in decisions. If one team experiences the merger as being absorbed by the other, no amount of planning recovers it.
Integration is also where deal value is lost. Cross-border acquisitions frequently fail to increase market value, and the cause is rarely the price paid. Last updated September 2026.
| Gets it right | Gets it wrong |
|---|---|
| One set of tools, everyone trained | Two systems, data that will not reconcile |
| Both sides in decisions | One side told what has been decided |
| Problems surfaced early | Tension noticed at the exit interview |
| A plan that adapts | A roadmap defended past its usefulness |
| Customers still served | Everyone busy integrating |
What are the best practices for merging teams?
Merging teams takes longer than the deal does, particularly when the two were competitors.
Watch for tension early. The signals appear weeks before anyone raises them: effort narrowing to job descriptions, reluctance to commit to long-term work, withdrawal from anything beyond immediate tasks.
Communicate the plan, then listen. People need time to absorb what is happening and a route to give feedback that visibly goes somewhere.
Keep the roadmap, but hold it loosely. No merger runs as it does on paper. A plan defended past its usefulness causes more damage than no plan.
Support people properly. Mergers are stressful in ways that are easy to underestimate from the side that initiated them.
Standardise the technology. Two teams on different systems means incompatible data and duplicated work. Pick one and train everyone on it, including the side that is switching.
Do not drop the customers. You are still running a business while restructuring it, and customers notice integration before they are told about it.
Why does communication decide the outcome?
Because in the absence of information, people assume the worst, and they are often right to.
New processes have to be disseminated, progress has to be visible, and problems need to surface faster than usual. If there are barriers to that, remove them deliberately.
Start with the obvious one. If one side uses Slack and the other uses Teams, that is a real barrier and a cheap fix. The same applies to document storage: one accessible location beats two well-organised ones.
Use surveys and polls to find out what people actually think, then act on what comes back. Asking and doing nothing is worse than not asking, because it confirms the suspicion that consultation is theatre.
Transparency matters more than usual here. Things left unsaid during a merger become entrenched problems, and the window for addressing them cheaply is short.
How do you get both sides genuinely involved?
By making decisions jointly rather than announcing them.
The worst outcome is one side feeling that the other is in control. That perception forms early, it is difficult to reverse, and it drives exactly the people you most wanted to retain.
Practical steps:
Appoint champions on both sides. People who relay management thinking outward and workforce concerns back, with enough standing that both directions are taken seriously.
Flatten the structure during integration. Hierarchy slows information and discourages people who are not yet sure where they fit from speaking.
Assign responsibilities on merit. If every significant role goes to the acquiring side, you have answered the question about who is in control regardless of what you say.
Integrate processes rather than imposing them. The acquired team often does some things better. Finding out which is part of what you paid for.
What changes when the teams are in different countries?
Everything above, plus two things that are structural rather than cultural.
Time zones and language. Meetings scheduled only for headquarters hours signal whose convenience matters. Rotate them, and record what people cannot attend.
You may not be able to employ the people you just acquired. This is the one that surprises companies. If the acquisition brings staff in countries where you have no legal entity, you cannot put them on payroll, and the transaction may complete before any entity could be registered.
An Employer of Record resolves it by employing them locally on your behalf from day one, with compliant contracts and correct local benefits. It removes the gap between completion and having a legal structure in place, which is otherwise weeks or months of uncertainty for people already unsettled by a merger.
The same applies to divestitures, where staff need to move the other way. We handled exactly this for VMware during its separation from Dell, completing global transfers ahead of schedule with individual support for each employee.
Work with Global Expansion
We employ people on your behalf across 214 countries and territories, including during acquisitions, divestitures and restructures where the legal entity does not yet exist.
Country requirements are in CountryPedia, and the expansion routes are compared in six methods of international expansion.
Talk to our team about the transaction you are planning.
Frequently asked questions
Why do team mergers fail?
Almost always for people reasons rather than operational ones: one side feeling absorbed rather than merged, communication that stops after the announcement, and tension that nobody surfaces until people start leaving.
How long does it take to merge two teams?
Longer than the transaction. Systems and reporting lines can be combined in weeks, but genuine integration, where people work as one team rather than two under one name, generally takes many months.
What should you do first after a merger is announced?
Communicate the plan and give people a route to respond that visibly leads somewhere. The period between announcement and clarity is when speculation does the most damage.
How do you combine two different sets of software?
Choose one and train everyone, including the team that is changing. Running both indefinitely produces data that will not reconcile and duplicated effort that nobody owns.
Can we employ acquired staff in countries where we have no entity?
Not directly. You would need to incorporate first, which takes months. An Employer of Record employs them on your behalf immediately, with compliant local contracts, which is why it is commonly used to bridge the period around completion.
How do you keep customers through a merger?
Assign clear ownership of customer relationships for the duration, so nobody assumes the other side is handling it. Integration consumes attention, and customers notice the gap before anyone tells them about it.
