Replacing a business laptop or desktop is not simply a hardware swap. The user depends on applications, accounts, files, peripherals and working arrangements that may have developed over time. If the IT team focuses only on issuing the new device, the missing dependency often appears after handover, when the old machine has already been collected. A practical replacement process treats the user's working environment as the thing being transferred.
Confirm the user and business requirement
Establish who will use the replacement, the work they need to perform and any relevant location or peripheral requirements. Avoid copying every historical application automatically if the organisation has a defined standard build and software approval process. The goal is to provide the current authorised working environment, not preserve years of accumulated clutter.
Identify application and access dependencies early
Check the applications, accounts and specialist services needed for the role and determine how they are provisioned. Some access follows the user's identity while other software may require separate licensing or configuration. Keep licence, security and approval decisions within the organisation's established processes rather than bypassing them to make the handover faster.
Plan data transfer through approved storage routes
Determine which business data genuinely needs migration and where the authoritative copy should reside. Use approved storage, backup and transfer procedures. A device replacement should not become an opportunity to move sensitive files through personal media or informal cloud accounts simply because they appear convenient.
Test the working journey, not just the hardware
A successful boot and sign-in prove very little about whether the user can work. Verify representative tasks relevant to the role, such as reaching required applications, approved shared resources and necessary peripherals. Where specialist software needs competent configuration or testing, involve the appropriate owner rather than assuming a generic IT check is sufficient.
Keep the old device controlled during transition
Decide when the previous device can be collected, retained temporarily or moved into the organisation's disposal or reuse process. Do not erase or reassign it before the approved transfer and verification steps are complete. Equally, avoid leaving an old configured device indefinitely with unclear ownership after the replacement has been accepted.
Record exceptions at handover
If a non-critical application, accessory or access request remains outstanding, tell the user what is pending and assign the action. This is more useful than delaying every replacement until every minor preference is resolved, and safer than declaring the job complete while known blockers remain undocumented.
Close the replacement with asset and support records aligned
Update the relevant asset, ownership and support information according to the organisation's processes. The service desk should be able to identify the user's current device if a ticket arrives later. A controlled replacement finishes when the new working environment is usable, outstanding actions are owned and the previous equipment has a defined next state—not merely when a new box reaches the desk.