TL;DR
Post merger IT integration plans are usually organised around systems. Identity, email, finance, the customer database. All necessary and all visible. The device fleet is treated as a detail to sort out later, which it is right up until somebody discovers the acquired company has no asset register, a different operating system standard and forty machines nobody can account for.
- Treat the acquired fleet as a fresh baseline, not a register to merge.
- Do not force a hardware standard early. Replace at refresh instead.
- Find out what management tooling the other side used before promising a date.
- Devices held by people who will leave are the urgent half.
- Two sanitisation standards means the weaker one is now yours.
- Budget for a discovery phase. The information you were given will be optimistic.
What post merger IT integration usually gets wrong
The plan is built around systems because systems are visible, expensive and have obvious owners. That is reasonable.
Devices get a line saying align the fleet, scheduled for some later phase. The problem is that two of the device workstreams are genuinely urgent and sit in the early phase whether the plan says so or not.
Security posture is urgent, because you have just acquired a population of machines holding your combined data under somebody else’s standards. And recovery from departing staff is urgent, because an acquisition is followed by departures and those devices leave with them.
What can genuinely wait
Hardware standardisation. Making everybody use the same model is a multi-year outcome achieved through normal refresh, not an integration task, and attempting it early wastes money replacing working machines.
Treat the acquired fleet as a new baseline
The instinct is to merge the two asset registers. In practice the acquired register is usually incomplete, differently structured, and optimistic about what exists.
Merging a clean record with an unreliable one produces one unreliable record, and you lose the ability to tell which half is trustworthy.
A better approach is to treat the acquired fleet as something to be discovered rather than imported.
- Enrol what you can reach, and record what enrolment actually finds.
- Compare that against whatever register you were given, as a reconciliation rather than an import.
- Investigate the difference in both directions before merging anything.
The gap is informative. A large difference tells you something useful about how the acquired company operated, and it is far better to find out during integration than during an audit two years later.
Our note on running an IT asset audit covers the reconciliation mechanics.
The security half is the urgent one
Two fleets means two sets of standards, and after the transaction the weaker one is effectively yours.
Four things worth establishing in the first weeks rather than the first year.
| Question | Why it is urgent |
|---|---|
| Is disk encryption on, and are keys escrowed | A lost device is now your incident |
| What management tooling exists | Decides whether you can act at all |
| Who has local administrator rights | Frequently everybody, historically |
| What happens to devices at exit | Departures start immediately |
ISO/IEC 27001 on information security management is the usual reference frame for the wider question, and the practical point is narrower: you cannot inherit a control you cannot verify.
NIST Special Publication 800-88 on media sanitization matters for the fourth row. If the acquired company’s offboarding wiped devices informally or not at all, any machine already returned to their store may still hold data, and that stock is now yours.
Devices with people who are about to leave
Acquisitions are followed by departures, both voluntary and planned. That is normal and it is also a device recovery problem arriving at speed.
The complication is that the acquired company’s recovery process may be weak, undocumented, or dependent on people who are themselves leaving.
Three practical moves.
Establish the recovery mechanism before the first wave. Not the policy, the actual courier and collection arrangement, per market.
Get the device list per person early, even if it is imperfect, because reconstructing it after somebody has gone is much harder.
Do not rely on their offboarding checklist unless you have read it. The equipment line is weak in most checklists and weaker in one nobody owns any more.
For markets where neither company has a presence, RemoAsset handles collection from departing employees and storage of recovered stock, which matters most in exactly the period when internal capacity is stretched.
The decision table
Integration effort should follow risk and overlap, not the size of the acquisition.
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Small acquihire | Under 20 people | Mixed personal devices | Nothing is managed | Issue new devices, retire theirs |
| Similar size, same platform | Any | Both managed | Two consoles | Consolidate tooling, keep hardware |
| Different operating system standard | Any | Two platforms | Support and policy diverge | Run both, converge at refresh |
| Acquired company fully remote | Any | No office, no register | Cannot physically audit | Enrol to discover, then reconcile |
| Carve-out from a larger group | Any | Devices belong to the parent | Assets may not transfer | Confirm ownership before planning |
Row five catches people out. In a carve-out the devices people are using may legally belong to the seller, with a transition period attached, which turns the fleet question into a contractual one before it is an operational one.
Row one is worth the opposite note. On a small acquihire, issuing new managed devices and retiring whatever people were using is frequently cheaper than assessing, enrolling and remediating a mixed population of personal machines, and it resolves the security question in a single step rather than over several months.
Budget for discovery
The single most useful adjustment to a post merger IT integration plan is to add an explicit discovery phase for devices before committing to dates.
The information supplied during diligence is produced under time pressure by people who want the transaction to complete. It is rarely dishonest and frequently optimistic, particularly about asset records, which are the least glamorous thing to tidy before a sale.
Two to four weeks of enrolling, counting and reconciling before publishing a plan avoids committing to a timeline built on numbers that do not hold.
What to converge, and when
Identity and security posture early, because they carry risk. Management tooling next, because it determines whether anything else is possible. Hardware standard last, through refresh, because replacing working machines to achieve uniformity is the most expensive way to buy a small amount of consistency.
Our piece on IT asset management implementation covers building the record once both fleets are visible.
The people who know where things are
In most acquired companies the device knowledge lives with one or two individuals rather than in a system. They know which machines were bought outside the process, who has the spare stock, and which supplier actually delivers.
Those people frequently leave early, because integration roles are uncertain and they are usually employable. Capturing what they know in the first few weeks is worth more than any tooling decision made in the same period.
The practical version is an hour of conversation with a list of questions, recorded, rather than a request to document everything. Asking somebody to write up two years of informal knowledge during a merger produces nothing.
Running two management consoles for a while
Consolidating tooling immediately is tempting and often wrong. Migrating device management is itself a risky change on a population you have not yet enrolled or verified, and doing it during the most disruptive period of an integration compounds two risks that would each be manageable alone.
Running both for a quarter costs licence money and buys the ability to act on either fleet while you learn what you actually acquired. Set a date for consolidation, and set it after the discovery phase rather than during it.
RemoAsset recovers and stores devices across markets, which matters most when internal capacity is stretched. More at PeopleOpsHQ.
Frequently asked questions
What gets missed in post merger IT integration?
The device fleet, because the plan is organised around systems that are visible and have obvious owners. Two device workstreams are genuinely urgent regardless of what the plan says: security posture, since you have acquired machines holding your combined data under somebody else’s standards, and recovery from departing staff, since an acquisition is followed by departures and the devices leave with them.
Should we merge the two asset registers?
Not directly. The acquired register is usually incomplete, differently structured and optimistic, and merging a clean record with an unreliable one produces one unreliable record where you can no longer tell which half to trust. Treat the acquired fleet as something to discover: enrol what you can reach, record what enrolment finds, and compare that against the supplied register as a reconciliation rather than an import.
How quickly should we standardise hardware after an acquisition?
Through normal refresh rather than as an integration task. Replacing working machines to achieve uniformity is the most expensive way to buy a small amount of consistency, and it is rarely what makes the integration succeed or fail. Converge identity and security posture early because they carry risk, management tooling next because it determines what is possible at all, and hardware last over two or three years.
What security questions matter first?
Whether disk encryption is enabled and keys are escrowed, what management tooling exists and whether you can actually act through it, who holds local administrator rights, and what happens to devices when somebody leaves. After the transaction the weaker of the two standards is effectively yours, and you cannot inherit a control you have not verified. The last question is urgent because departures begin immediately.
Why are departures a device problem after a merger?
Because they arrive at volume during the period when the acquired company’s own recovery process is weakest, often depending on people who are themselves leaving. Establish the actual collection mechanism per market before the first wave rather than relying on a written policy, and get the device list per person early even if imperfect, since reconstructing it after somebody has gone is considerably harder.
How much time should be allowed for device discovery?
Two to four weeks of enrolling, counting and reconciling before committing to dates. Information supplied during diligence is produced under time pressure by people who want the deal to complete, and it is rarely dishonest but frequently optimistic, particularly about asset records which are the least glamorous thing to tidy before a sale. Publishing a plan built on those numbers tends to produce a plan that slips.
What is different about a carve-out?
Ownership may not transfer with the people. In a carve-out from a larger group, the devices staff are using can legally belong to the seller, often with a transition services period attached, which makes the fleet a contractual question before it is an operational one. Confirm what actually transfers before planning anything, because the answer sometimes means equipping the acquired population from scratch on a deadline.
RemoAsset recovers, stores and ships devices across markets during integrations and exits.