A new computer can look finished because email opens, the desktop is clean, and the user can sign in. That does not prove the old machine is ready to be wiped, returned, recycled, or placed on a shelf nobody will check again.
The retirement decision comes after migration, not during the excitement of setup. Before the old computer leaves the recovery path, verify that the work—not just the obvious files—made the move.
Treat the old computer as evidence
The old machine may contain local documents, application settings, browser data, templates, fonts, saved exports, scanner software, label-printer utilities, or a scheduled task nobody remembered to mention. It may also reveal which account owns a subscription, which peripheral needs an older driver, or where a line-of-business application stores its working data.
That is why our pre-purchase office-computer inventory starts before hardware is ordered. After migration, use that inventory as a verification list rather than assuming the transfer utility understood the business.
Record what the old computer did, who used it, which systems depended on it, and what was intentionally left behind. If something cannot be identified, pause before erasing it.
Verify the new working environment
Have the actual user perform representative work on the new computer. Opening an application is not the same as completing the task it supports.
Check a small but meaningful set of activities:
- open current and older working files;
- send and receive email from the correct account;
- print, scan, label, or connect to specialty equipment;
- reach shared folders, cloud storage, and approved remote systems;
- confirm bookmarks, templates, signatures, and required browser extensions;
- verify licensed applications are activated under business-controlled accounts;
- test any export, upload, or reporting step used in normal work;
- confirm an authorized administrator can support and recover the new machine.
Write down problems and resolve them while the old environment is still available for comparison. This is a handoff, not a guessing contest.
Test recovery before removing the fallback
A copied folder is not necessarily a complete recovery path. Confirm what protects the new computer, which information is included, who receives failure notices, and whether a useful restore can be performed. Our Field Note on testing a backup restore explains the difference between seeing a successful backup message and proving the information can come back.
If the migration created a new account, changed a device name, or moved data to a different location, verify that backup rules followed the change. Keep the old computer available for an agreed verification period when the business can do so safely, but do not let “temporary” storage become an undocumented archive.
Close the retirement deliberately
Assign one person to approve retirement. Record the device, serial number, assigned user, migration date, verification date, disposition, and who authorized the final step. Remove the device from business accounts and management tools only when doing so will not disrupt records or recovery. Handle data erasure, return, donation, recycling, or storage according to the business’s requirements and the sensitivity of the information involved.
We help small businesses plan workstation transitions, verify the handoff, and document what remains through our business technology services. If several computers or a complicated workflow are changing, request a Technology Checkup before the old machines disappear.
Leave a comment