When you acquire a company, you also acquire its mobile devices, its device management platform, its carrier contracts, and its repair arrangements, usually with very little documentation. The deal team rarely looked at any of it.
If you’ve just been handed integration of the acquired company’s devices, the first 90 days decide whether this becomes a clean consolidation or a second fleet you’re still running separately in three years.
This post covers what you’re really inheriting, how to find out what’s there, which risks to fix first, and how to decide between standardizing now and running both fleets for a while.
What you’re actually inheriting
The devices are the visible part. Behind them sits everything that keeps them working, and each piece has its own owner, contract, and renewal date.
Expect a mobile device management (MDM) platform you may not use, administered by someone who may not be staying. Expect carrier accounts on different plans and terms, a repair vendor or two, a drawer of spares, and apps that only work on the devices they already have.
The most valuable thing you inherit is often the knowledge of how it all fits together. That usually lives with one or two people, and acquisitions are exactly when those people leave.
Days 1 to 30: find out what you have
Discovery comes before any decision. You can’t plan an integration around a fleet you haven’t counted, and the acquired company’s own records will rarely match reality.
- Count the devices. Export the device list from their management console and compare it with purchase records and a physical check at each site.
- Find the administrators. Identify who holds admin access to the MDM platform, carrier portals, and Apple and Google enrolment accounts, and whether they’re staying.
- Pull every contract. Carrier agreements, MDM licences, repair and support contracts, and leases, with renewal and termination dates.
- List the apps. Note which business apps run on the devices and which ones depend on a specific device model or operating system.
- Map the support path. Find out who frontline staff call today when a device breaks, and what happens next.
Carrier lines need their own reconciliation, covered in the piece on telecom inventory management. For the devices themselves, the guide to getting a handle on fleet inventory walks through matching records on serial number.
Talk to the people who ran the fleet
The fastest way to understand an inherited fleet is to sit down with whoever ran it. An hour with them will tell you more than a week of reading exports.
Ask what breaks most often, which sites struggle, what workarounds staff rely on, and which devices or apps are close to end of life. Ask what they would have changed if they’d had the budget. Those answers point straight at the risks and the quick wins.
Do it early. If those people are leaving as part of the transaction, their knowledge leaves with them, and you’ll spend months rediscovering it.
Fix the risks that can’t wait
Some problems need attention before the integration plan is finished. They’re the ones where a departure or an expiry date could cut you off from devices you’re now responsible for.
Start with access. Admin credentials, certificates, and enrolment accounts that sit under a departing person’s name should move to shared, role-based accounts in the first weeks. If they lapse, you may lose the ability to manage or wipe those devices remotely.
Then look at exposure. Devices that aren’t enrolled in management, devices running unsupported operating systems, and devices still held by people who left during the transaction are all risks you now own. If they hold personal information, accountability under PIPEDA comes with them, so lock or recover them early.
Carrier contracts and lines need their own plan
Carrier accounts are often the slowest part of a device integration, because they’re governed by contracts rather than IT decisions. Moving lines too early can trigger fees, and leaving them too long means paying for two sets of plans.
Start by listing every account, its plan, its term, and any early termination or minimum-commitment clauses. Then decide which lines move to your agreements, which wait for their term to end, and which can be cancelled because nobody is using them. That last group is often larger than expected after an acquisition.
Standardize now or coexist for a while?
The biggest decision is whether to bring the acquired fleet onto your standard immediately or let both run until a natural refresh point. There’s no universal answer, but the options are clear.
| Approach | Fits best when | Trade-off |
|---|---|---|
| Standardize now | The acquired devices are old, unsupported, or failing, or the business is being fully absorbed | Upfront cost and a rollout during an already busy integration |
| Coexist, then converge at refresh | The acquired devices are healthy and have years of support left | Two platforms and two sets of procedures to run until the refresh |
| Coexist long term | The acquired business runs separately with different workflows and devices | Permanent duplication of effort and cost |
Most organizations land in the middle. They move management onto one platform early, keep healthy devices in service, and replace them on the parent company’s standard when they reach end of life. The device lifecycle management guide covers how to plan that kind of staged convergence.
Days 30 to 90: one record and one support path
Whatever you decide about hardware, get to one asset record and one support path quickly. Two inventories and two help desk routes mean every problem takes longer to solve.
Bring the acquired devices into your asset record with the same fields as your own fleet. The asset tagging FAQ for device fleets covers how to tie each device to its record. Then route support so frontline staff at the acquired sites call the same place as everyone else.
Watch for Canadian specifics. An acquisition that adds Quebec sites brings French-language obligations for workplace tools and support, and carrier contracts signed in one province may carry terms that don’t match yours. Check early termination fees before you plan to move lines.
Where outside help fits
Integrations land on IT teams that are already busy, and device work is easy to push down the list until something breaks. That’s when outside help is worth considering.
Through lifecycle management, our in-house Canadian team can take on the physical side of an integration, including inventory, repairs, spares, and asset tracking, while your team focuses on the systems and people decisions. Just know that for a small acquisition with a handful of devices, a careful internal checklist will usually do the job.
Questions we hear about device fleets after an acquisition
What should IT do first with an acquired company’s mobile devices?
Secure admin access first, moving MDM, carrier, and enrolment accounts held by individuals to shared, role-based accounts before anyone leaves. Then count the devices, pull every contract with its renewal date, and find out how staff currently get support. Decisions about standardizing hardware come after that discovery.
Should we replace an acquired company’s devices right away?
Only if they’re old, unsupported, failing, or blocking the integration. Healthy devices with years of support left can usually stay in service while you move them onto your management platform and support process. Replace them on your standard when they reach a natural refresh point.
Can we run two MDM platforms after an acquisition?
You can, but it doubles administration, policy work, and the chance of gaps between the two. Many organizations run both briefly, then migrate the acquired devices to one platform within the first year. The right timing depends on licence terms, device health, and how quickly the businesses are combining.
Where to start
This week, find out who holds admin access to the acquired company’s device platform and carrier accounts, and move those accounts somewhere they can’t walk out the door. Then count what you have. Every other integration decision gets easier once you know exactly what came with the deal.