When two companies combine, the first real question leadership asks is usually some version of: where do we have duplication, where are the gaps, and who are we at risk of losing. That sounds like a planning question. In practice, it's a data problem, because the answer lives in two different HRIS systems, under two different sets of job titles, pay bands, and org structures, and nobody has reconciled them yet.
Why HR gets asked for answers before it has the data to give them
Deal close happens fast. The people workstream usually doesn't start in earnest until after signatures, which means HR is often handed the combined organization and a tight timeline at the same moment. Leadership wants an early read on redundancy, cost synergies, and retention risk within weeks, not the months it would take to do it properly by hand.
Research from firms that advise on these deals, like Aon and WTW, consistently flags retention of key talent as one of the biggest risks in the months after close. That's exactly the window when integration teams are still figuring out who the key talent even is across both organizations, because the two companies never defined "key talent," "manager," or "high performer" the same way to begin with.
The real work is reconciliation, not reorganization
An org chart in a slide deck isn't the hard part. The hard part is getting every person, role, and cost center from both companies into one consistent structure you can actually query, when the two sides likely ran different HRIS platforms, different job architectures, and different fiscal calendars. Until that reconciliation happens, any answer about overlap or risk is really just someone's best guess dressed up as an insight.
Three questions integration teams get asked that a spreadsheet can't answer fast
Most teams start with a shared spreadsheet and a few weeks of manual cross-referencing between HRIS exports. It works, for a while. Then one of these comes up:
Where do the two organizations actually overlap in skills and headcount?
Which roles become redundant once the combined structure is finalized?
Who are the people we can't afford to lose, and are they showing any flight risk right now?
A static export answers the first version of each question. It's wrong again within days, because integration decisions keep changing the underlying org, and nobody wants to rebuild the same manual reconciliation every time something shifts.
What changes when the data is unified instead of just collected
The difference isn't having more data. Most integration teams already have more HR data than they can use, just split across two systems nobody has fully connected. The difference is having one live, reconciled view that both HR and finance can query the same way, so a question about headcount overlap or retention risk gets answered in minutes instead of becoming its own mini-project.
That's the gap Illoominus sits in during an integration: bringing both companies' HRIS, finance, and operational data into one place, with consistent definitions across both sides, so the people actually doing the integration work can spend their time acting on what they find instead of reconciling spreadsheets to find it. If your team is in the middle of this right now, we'd be glad to compare notes on what we're seeing with other integrations.
FAQ
How long does it typically take to reconcile HR data after a merger?
There's no fixed timeline, but when it's done manually across two HRIS exports with different job codes and definitions, it commonly runs weeks to months, and the result is often out of date again shortly after it's finished.
What's the biggest mistake companies make when combining workforce data mid-merger?
Treating it as a one-time reporting exercise. Integration decisions keep changing the underlying organization, so a static report answers today's question and is wrong again the next time leadership asks.
Who should own workforce data reconciliation during an integration, HR or IT?
Usually both, and that's often where it stalls. HR knows which questions are worth asking and what "key talent" or "redundant role" actually means in context. IT or a data team owns the pipes connecting the systems. Reconciliation needs both, with one side clearly accountable for the combined definitions, not just the data transfer.
Does this only matter for large, complex mergers?
No. Mid-market mergers run into the exact same reconciliation problem, arguably more acutely, since they rarely have a dedicated integration management office to absorb the manual work.
