A client may ask an MSP to replace a laptop because it is slow, damaged, unsuitable for a new role or approaching an internal refresh point. The request sounds simple, but replacing a managed device can involve approval, specification, data, access and asset records. A structured process keeps those activities connected.
Confirm why replacement is being requested
Record the operational reason rather than assuming every performance complaint requires new hardware. The support team may need to distinguish a device fault, capacity issue, role change or client-led refresh decision before the appropriate next step is clear.
Check that the request is authorised
Follow the MSP's agreed client approval route for purchasing or replacing equipment. A user's preference for a different device should not automatically become an order if the client requires another person to approve expenditure or specification.
Define the user's current requirements
Confirm the business applications, connectivity and other relevant needs that the replacement must support. Avoid copying an old specification without checking whether the user's role or the client's current technology standards have changed.
Keep procurement separate from unsupported promises
If the MSP supplies equipment, communicate availability and timing based on confirmed information. Do not promise a particular delivery or setup date before the relevant stock, supplier and scheduling position is known.
Plan the migration and handover
Identify the technical work needed to prepare the replacement and move the user to it through the provider's approved process. Account configuration, managed applications and business data should be handled according to the client's authorised environment rather than improvised during handover.
Track the old device explicitly
Replacement does not end responsibility for the previous asset. Record whether it is being returned, retained, reassigned or handled through another approved client process. The asset record should reflect the actual outcome.
Verify the replacement before closing the ticket
Confirm that the agreed technical setup has been completed and that any known outstanding item remains visible. Avoid closing the request merely because the new device has physically arrived at the client site.
Update service and asset records
Once the handover is complete, make sure current support records identify the correct managed device. Accurate records reduce confusion when the user later raises a fault and help the MSP avoid troubleshooting against obsolete hardware information.