Laptop Replacement Checklist for IT Support

The short version: a laptop replacement is not just “hand over a new machine.” Confirm the reason for the swap, back up the right data, capture required apps and peripherals, enroll the device, test sign-in, transfer user settings where appropriate, document the asset change, and keep the old laptop recoverable until the user is truly working.

Laptop swaps are deceptively easy tickets. The user wants a newer machine, the manager wants the ticket closed, and the help desk wants one less device on the bench. Then someone discovers the browser profile did not sync, the VPN certificate stayed on the old laptop, or the accounting app needs a license move.

Use this checklist for replacement laptops, hardware refreshes, warranty swaps, damaged-device replacements, and “this laptop is possessed” rebuilds. Adjust the tooling to your environment, but keep the workflow boring: scope, backup, prepare, migrate, test, document, hold, wipe.

The laptop replacement checklist

Step	What to check	Why it matters
1	Confirm the replacement reason and deadline	Separates normal refresh from urgent outage
2	Identify the user, device, asset tag, and ownership	Prevents swapping the wrong asset
3	Back up or verify synced user data	Avoids the worst kind of “oops”
4	Capture required apps, licenses, printers, VPN, and peripherals	Keeps the user from reopening the ticket tomorrow
5	Build, patch, encrypt, and enroll the replacement laptop	Makes the device supportable before handoff
6	Sign in and test the user’s real workflows	Proves the replacement actually works
7	Update inventory, ticket notes, and old-device status	Keeps asset records and audits sane
8	Hold the old laptop briefly, then wipe or retire it	Gives you a safety net without hoarding ewaste

1. Confirm why the laptop is being replaced

Start by separating the request type. A refresh laptop, a broken laptop, and a suspected compromise should not follow the exact same path.

Ask:

Is this a scheduled hardware refresh, warranty replacement, performance issue, break/fix ticket, or lost/stolen device?
Is the current laptop usable long enough to back up data?
Is the user remote, onsite, traveling, or about to leave the company?
Is there a required deadline, meeting, payroll run, travel day, or project launch?
Is the old device damaged, missing, locked, or possibly compromised?
Who approved the replacement and who owns the cost center?

That last part matters. Help desk should not become a vending machine with USB-C ports. If your company has a hardware refresh policy, link the ticket to it. If the laptop is being replaced because it is slow, make sure nobody expects the old one to go back into inventory as “fine.”

If the replacement is part of a new hire flow, connect it to the new employee IT onboarding checklist. If it is part of an exit or role change, sanity-check the employee offboarding checklist so you do not accidentally preserve access that should be removed.

2. Capture the current device details before touching anything

Before imaging, wiping, or shipping hardware, record what you are replacing.

Capture:

Current laptop hostname
Serial number and asset tag
Assigned user
Department and location
Warranty status if relevant
Docking station, monitors, charger, keyboard, mouse, headset, smart card reader, or other peripherals
Operating system version and management status
Encryption status and recovery-key location
MDM, RMM, antivirus, EDR, or endpoint protection status
Any open incidents tied to the device

This is asset management, not paperwork theater. When a user says “the old laptop had a special adapter,” you want to know whether that adapter existed, belonged to IT, or was purchased with a department card and disappeared into the drawer dimension.

3. Verify user data before the swap

Do not assume everything syncs. Actually check.

Common places to verify:

OneDrive, Google Drive, Dropbox, or other cloud sync folders
Desktop, Documents, Downloads, Pictures, and local project folders
Browser profiles, bookmarks, saved profiles, and extensions if your environment allows them
Outlook signatures, PST files, archives, or local mail caches
VPN profiles, certificates, Wi-Fi profiles, and saved remote desktop entries
SSH keys, developer config, scripts, and local repositories for technical users
App-specific local data, like accounting exports, label-printer templates, scanner software profiles, or weird line-of-business folders

A good rule: if the user says “all my stuff is in the cloud,” still check the Desktop and Downloads folder. Important files love hiding there.

If the laptop is failing, prioritize business data first. Do not spend an hour migrating wallpapers while the drive is clicking.

4. Build the replacement laptop the standard way

The replacement should be boring and repeatable.

Before handoff, confirm:

Correct hardware model and accessories
OS installed from the approved image or provisioning workflow
Device enrolled in Intune, Jamf, Workspace ONE, RMM, or your management tool
Hostname follows your naming standard
Full disk encryption is enabled and the recovery key is escrowed
Endpoint protection is healthy
Required patches are installed or queued
Local admin policy matches company standard
Remote support tool is installed and reachable
Power settings, lock screen policy, and compliance profile are applied

If you have a standard provisioning process, use it. If every laptop swap is a hand-built snowflake, the laptop is not the only thing that needs replacing.

For software, do not install “whatever the old machine had” blindly. Start with the role profile, then add approved exceptions. The software install request checklist is useful when the user asks for one more app during the swap.

5. Migrate access, apps, and peripherals

The device is only useful if the user can do their actual work.

Check the common misses:

Microsoft 365 or Google Workspace sign-in
MFA registration and authentication prompts
VPN client and internal DNS access
Required browser profiles and SSO extensions
Email signatures and shared mailbox access
Department file shares, SharePoint libraries, or Teams channels
Printers, label printers, scanners, badge printers, or specialty devices
Docking station and monitor layout
Audio device, camera, headset, and conferencing apps
Password manager extension or desktop app
Line-of-business apps and license activation

Do not test only the Windows login. That proves the laptop turns on. It does not prove the user can work.

If the user relies on a shared inbox, validate that separately with the shared mailbox access checklist. Shared mailbox permissions are exactly the sort of thing that looks fine until Outlook decides to have opinions.

6. Test with the user before closing the ticket

A laptop swap should end with user-confirmed testing, not “device delivered.”

Have the user verify:

They can sign in with their normal account.
MFA works.
Email opens and sends.
Calendar opens.
Browser bookmarks or profiles are usable.
VPN connects if they work remotely.
Core apps launch and license correctly.
Needed files are present or reachable.
Printers and specialty devices work.
Camera, microphone, speakers, and headset work.
Docking station and monitors behave normally.
The old laptop is not still needed for an obvious missing item.

If the user is remote, schedule a short screen-share session or provide a clean test list. “Let me know if anything is missing” is not a test plan. It is how you get a ticket reopened at 4:55 PM.

7. Leave ticket notes the next tech can use

Document the replacement clearly.

A solid closure note looks like this:

Replaced laptop for Jordan P. due to scheduled hardware refresh. Old asset LAP-1842, serial ####, replaced with LAP-2907, serial ####. Confirmed OneDrive sync complete, copied local Desktop and Downloads business files, enrolled new laptop in Intune, verified BitLocker recovery key escrow, installed approved Sales app bundle, configured VPN, tested Microsoft 365, CRM, Teams audio, printer mapping, and dock/monitors with user. User confirmed required files and apps are available. Old laptop held in IT storage for 14 days before wipe.

That note answers the questions people actually ask later: what changed, what was tested, where the old device is, and whether the user confirmed it.

For more copyable formats, use the help desk ticket notes examples instead of writing “done” like a goblin with a closing-code quota.

8. Hold, wipe, retire, or redeploy the old laptop

Do not immediately wipe the old laptop unless policy or security requires it. Also do not keep it forever because “maybe.” Use a defined hold period.

A common approach:

Normal refresh: hold old laptop 7-14 days, then wipe and return to inventory or recycle.
Damaged laptop: recover data if possible, document condition, process warranty or disposal.
Lost/stolen laptop: mark lost, revoke sessions as needed, confirm encryption and remote wipe status.
Security incident: follow incident response, preserve evidence if required, and do not casually rebuild over it.
VIP or high-risk role: confirm data migration and access with extra care before wipe.

Before wiping, verify:

Data migration is complete or old drive is no longer needed
Recovery keys and device records are updated
Asset status is changed in inventory
User is no longer assigned to the old laptop
Licenses tied to the old device are released if needed
The device is removed from shipping, loaner, or repair limbo

The goal is not to keep a museum of sad laptops. The goal is to protect the user for a short window, then clean up properly.

Laptop replacement mistakes that create repeat tickets

Assuming cloud sync handled everything

Cloud sync is great until the user saved the board presentation in C:\Temp\final-final-really-final. Check the obvious local folders before the swap.

Forgetting specialty apps and peripherals

Printers, scanners, label makers, smart card readers, and old desktop apps are where laptop swaps get messy. Ask what the user physically plugs in before you take the old machine.

Closing before the user tests real work

“Laptop delivered” is not the same as “user can work.” Close after core workflows are tested or after you document exactly what is still pending.

Losing track of the old asset

If the old laptop is sitting on someone’s desk, in a shipping box, or under the help desk counter with no ticket note, you have an asset problem waiting to become an audit problem.

FAQ

How long should IT keep the old laptop after replacement?

Follow company policy, but 7-14 days is a practical hold window for normal refreshes. Keep it shorter if security policy requires immediate wipe. Keep it longer only when there is a documented reason.

Should IT copy personal files during a laptop replacement?

Business data should be handled according to company policy. Personal photos, tax files, music, and random downloads are a policy call, not a “be nice and copy everything” default. Be clear with users before the swap.

What if the old laptop will not boot?

Treat it like a recovery ticket. Check whether data is already synced, attempt drive recovery if policy allows, document what could not be recovered, and avoid promising miracles. If it might be a security incident, stop and follow incident response.

Should every laptop replacement use a fresh image?

Usually yes. A fresh, managed build avoids dragging old problems forward. Exceptions happen, but cloning a broken laptop because it feels faster often gives the user a shiny new container for the same old mess.

Final checklist before you close

Before closing a laptop replacement ticket, confirm:

If you want more practical help desk templates like this, join the This Is an IT Support Group newsletter. We send the kind of IT career and support advice that sounds like it came from someone who has actually closed tickets before.