After the Acquisition: Getting Laptops Back From a Remote Team You Just Inherited

An acquisition closes on a Friday. By Monday, IT owns a fleet it has never seen: laptops bought by another company, enrolled in another company’s tools, and sitting in home offices across the country. Some of those people will stay and move to your hardware. Some will leave during the transition. Either way, a lot of devices need to come back, and the asset list you were handed is probably not as accurate as it looked in the data room.

This piece is for IT and HR leads at US companies absorbing a remote or hybrid team. The core idea: treat the inherited fleet as its own return project, with its own inventory, owner, and finish line, instead of folding it into normal offboarding and hoping it sorts itself out.

Why inherited fleets are harder than your own

Your own laptops come with history. You know who ordered them, where they shipped, and which tool they report into. An acquired fleet usually arrives with gaps:

• The asset list is a snapshot, not the truth. It was exported weeks before close. People have moved, swapped machines, or kept a second device nobody wrote down.
• Two sets of rules apply at once. The acquired company had its own equipment policy. Until the new one is signed, people may not know which rules they are under.
• Nobody on your side knows the employees yet. A return request from a stranger at the parent company is easier to ignore than one from a manager someone has worked with for years.
• Departures cluster. Transition periods bring role eliminations and voluntary exits close together, so returns pile up exactly when your team has the least context.

None of this is unusual. It is just what happens when hardware changes hands faster than relationships do.

Step 1: Rebuild the inventory before you ask for anything

Before the first return request goes out, reconcile the asset list against reality. Pull the list from the acquired company’s records, then compare it with what their device management and identity tools actually show as active.

For each device, you want four things:

1. Serial number and model, so you can match what arrives against what left.
2. Assigned person and their current shipping address, confirmed recently, not copied from an old HR export.
3. Status after the deal: staying on this device for now, moving to new hardware, or leaving the company.
4. Owner on your side: the one person responsible for closing that device out.

Anything that does not match goes on a short exceptions list. That list is where most of the lost laptops would have come from, and now you can work it on purpose.

Step 2: Sort people into return waves

Not every inherited laptop needs to come back at once, and trying to do it all in one push confuses people who are already nervous about the deal.

A simple way to sequence it:

• Wave 1, departures. Anyone leaving during the transition. These returns are time-sensitive and tie directly to final-day offboarding.
• Wave 2, hardware swaps. Staying employees who will move to your standard laptops. The return happens once the new device is set up and working.
• Wave 3, stragglers and spares. Extra devices, old machines found during reconciliation, and anything from the exceptions list.

Each wave gets a clear window and a named owner. That keeps a single overloaded IT inbox from becoming the whole plan.

Step 3: Let a familiar voice make the ask

The person who should request the laptop is usually the employee’s current manager or the acquired company’s former IT contact, not a generic address at the parent company. A short message from someone they know gets read.

Keep the message plain:

• What is happening and why (the move to the new company’s equipment, or offboarding).
• Exactly which device or devices need to come back.
• What they will receive to send it, and that shipping is prepaid.
• Who to ask if something does not fit or is missing.

Tone matters during a deal. People are already reading every email for signals about their job. A calm, specific return request reads as routine. A vague one reads as a threat.

Step 4: Remove every excuse in the packaging

During a transition, the most common reason a laptop does not come back is not refusal. It is friction. The employee has to find a box, buy tape, print a label, and get to a carrier, all while worrying about the rest of their job.

Sending a prepaid kit to their door removes those steps. A service like ReRoutd ships custom-fit packaging with a prepaid label, a tamper-evident seal, and tracking you can watch from a dashboard, plus automated notifications to the employee so the reminders are not all coming from your team. A laptop kit is $89, or $79 each for five or more, and it fits laptops up to 17 inches. Tablet kits are $69 ($64 for five or more) for devices up to 12 inches, and phone kits are $59 ($54 for five or more) for devices up to 7 inches. Optional insurance up to $5,000 is available, and there is no subscription, which suits a one-time project like an acquisition.

Whatever you use, the goal is the same: the employee should be able to pack and send the device without buying or printing anything.

Step 5: Close each device on the serial, not on a promise

“I shipped it” is not a closed return. A device is done when the serial number on your reconciled list is the serial number that arrived. Mark it received, note its condition, and hand it to your security process for whatever your policy requires before reuse or disposal.

Keep the exceptions list visible until it is empty. Review it weekly with HR and the managers involved. If a device is still missing after your agreed window, that becomes an HR conversation guided by the equipment policy, not another round of reminders from IT.

A short checklist for the first 30 days

• Reconcile the inherited asset list against live device and identity records.
• Confirm current shipping addresses for everyone with a company device.
• Tag every device as staying, swapping, or leaving, with one owner each.
• Publish the equipment policy that now applies, in plain language.
• Run returns in waves: departures first, swaps second, stragglers last.
• Have a familiar manager or former IT contact send each request.
• Ship prepaid kits so nobody needs to find packaging or print a label.
• Close each return only when the serial number is received.
• Review the exceptions list weekly until it is empty.

The takeaway

An acquisition hands you hardware before it hands you trust. The fix is not more reminders. It is a clean inventory, a sequence people can follow, a message from someone they know, and packaging that makes sending the laptop back the easiest thing on their list.

Do that, and the inherited fleet stops being a loose end in the integration plan and becomes one more project with a finish line.

The ReRoutd team