In nearly every acquisition we have worked through, the pattern is the same. The deal team spends months in diligence. Legal, finance, and operations are all at the table. The integration planning begins in earnest. And HR is brought in — if they are brought in at all — somewhere around the week the deal closes.
By that point, the decisions that will define the People integration have already been made. Organizational structure has been sketched. Reporting lines have been assumed. Retention packages for key talent have been negotiated without input from the people who actually know who the key talent is. And the timeline — always too aggressive — is already locked.
This is not a failure of HR competence. It is a failure of People infrastructure.
Why M&A breaks People operations
Acquisitions do not break HR teams. They expose the brittleness that was already there. When your People operating model is already operating at capacity, adding the complexity of an integration — new employees, new systems, new culture, new compliance requirements — does not create problems. It reveals them.
The most common failure points we observe are:
- No integration playbook. The organization has never written down how it integrates an acquired company’s People infrastructure. Every deal starts from scratch, at speed, with whoever happens to be available.
- Systems misalignment. The acquiring company’s HCM platform was not designed to onboard an entire acquired workforce simultaneously. What should be a configuration problem becomes a crisis.
- Retention blind spots. Without clean workforce data, you cannot identify your highest-risk attrition targets in the acquired company until it is too late to retain them.
- Culture collision without a plan. The organizational cultures are different. Everybody knows this. Nobody has a structured approach for managing the collision.
- Compliance exposure. The acquired company operates in states, countries, or labor categories you have not previously managed. Your compliance infrastructure does not automatically extend to cover them.
“The People integration does not begin on Day 1. It begins the moment you know the deal is likely to close. Every week of preparation you miss becomes a month of recovery.”
What a People integration playbook actually looks like
A functional integration playbook is not a checklist of HR tasks. It is a structured decision framework that answers three questions before Day 1: What do we need to know? What do we need to decide? And what do we need to build?
What do we need to know?
Before integration planning begins in earnest, you need a clear picture of the acquired company’s People infrastructure: headcount by location and function, compensation architecture, HCM systems and data quality, existing HR operating model, open roles and talent gaps, and any outstanding compliance or labor relations issues. This is diligence, and it should happen before the deal closes — not after.
What do we need to decide?
Integration involves a series of structural decisions that have long-term consequences. These include: which HCM platform will be the system of record? What happens to acquired employees’ benefits and compensation on Day 1 vs. over a defined transition period? What is the organizational structure of the integrated entity, and who holds each role? Which HR policies apply immediately and which have a transition period?
These decisions cannot be made by the integration team alone. They require C-suite alignment before Day 1, because the acquired employees will ask these questions on Day 1 and the answers need to be consistent and clear.
What do we need to build?
The infrastructure that does not exist before the deal closes needs to be built in the integration sprint: onboarding workflows for the acquired workforce, manager communication toolkits, an integration-specific HR help desk, data migration scripts, and a 90-day check-in framework for retention risk monitoring.
The Pre-Flight Principle
An aircraft does not wait until it is on the runway to check its systems. The pre-flight inspection happens before the engines start. People integration works the same way. The playbook, the decisions, and the infrastructure need to exist before Day 1 — not because Day 1 is the hard part, but because Day 1 sets the conditions for everything that follows.
What good looks like: a 90-day integration framework
The organizations that integrate acquisitions well share a common pattern. They treat the People integration as a parallel workstream to the deal process — not a follow-on activity. They have a standing integration playbook that gets activated when a deal enters late-stage diligence. And they measure integration success not by whether they hit their Day 1 milestones, but by 90-day retention rates, productivity metrics, and employee experience scores in the acquired population.
The first 90 days break into three distinct phases:
- Days 1–30: Stabilization. The acquired employees need to feel secure. Benefits, payroll, and reporting structure must be clear and functioning. HR must be reachable and responsive. Every open question left unanswered becomes an attrition risk.
- Days 31–60: Integration. Systems consolidation, policy alignment, and cultural onboarding. This is the heaviest lift and where most integrations stall. It requires dedicated capacity — not people doing integration work on top of their existing jobs.
- Days 61–90: Optimization. Retention risk assessment, leadership identification in the acquired population, and the first real measurement of integration health. Are the right people staying? Are they engaged? What does the data say?
If your organization is planning an acquisition — or if you are in the middle of one and the People integration is already behind — the HCM Pre-Flight Diagnostic is a 30-minute session designed to assess exactly where you are and what needs to happen next.