A new computer that feels like yours by lunchtime

We start by inventorying the old machine rather than the new one: installed applications, mapped drives, printers, VPN profiles, saved Wi-Fi networks, browser profiles and extensions, and the specific line-of-business software that runs the business. Then we look in the places files actually hide. Outlook data files that were never moved to the server, mail archives sitting in a folder from a machine two computers ago, Sticky Notes stored in a small database rather than as documents, license and activation files for niche software, scanner and label printer configurations, and QuickBooks company files parked in an application directory instead of Documents.

Email and cloud storage, done in the right order

Email is the single most common source of migration pain, and almost all of it is avoidable by sequencing correctly. For Microsoft 365 and Exchange accounts the mailbox lives on the server, so a new machine builds a fresh local cache and everything reappears, but the signatures, autocomplete list, rules stored locally, and any PST archives do not come with it unless someone brings them. For POP accounts, which still exist in small businesses more often than anyone admits, the mail exists only on the old machine, and getting that wrong loses years of correspondence permanently. We identify the account type before anything is wiped.

Cloud storage has its own trap. OneDrive and similar clients show files in Explorer that may exist only in the cloud, or may exist only locally and not yet be uploaded. Wiping or disposing of the old machine before sync has genuinely completed is a real way to lose data, and the sync status icon is not a substitute for checking. We confirm sync completion, set up Known Folder Move so Desktop, Documents and Pictures are protected going forward, and make sure the new machine has finished pulling down what the user actually needs offline before they travel.

Debloating, and what to keep

Consumer machines arrive carrying trialware: security suite trials that nag and interfere with the protection you actually use, manufacturer content apps, preinstalled games and shopping shortcuts, and duplicate utilities for functions Windows already performs. All of it gets removed, along with the taskbar and Start menu clutter. This is worth doing carefully rather than with a blunt removal tool, because some vendor software genuinely earns its place.

Keep the manufacturer's update utility, because it delivers firmware and driver updates far more reliably than Windows Update, and keep the vendor's power and battery management tool, which is how you set charge thresholds and thermal profiles. On business machines keep the docking and display management components. Remove the rest. The result is a machine that boots faster, has fewer background processes competing for resources, and stops nagging its owner within the first week.

For businesses we increasingly do none of the above by hand. New machines are enrolled with Windows Autopilot or a comparable Apple deployment program so the device ships directly to the user, who signs in with their work account and watches the machine configure itself: applications delivered by Intune, security policy applied, drive encryption enabled with the recovery key escrowed to your tenant, printers mapped, VPN configured. No technician unboxes it, remote staff are served identically to office staff, and every machine ends up the same. That approach is covered further on our Windows 11 deployment page.

Where a standard image is the better fit, typically for shared machines, specialized workstations or environments with heavy line-of-business software, we build and maintain one for you. A single reference build with the applications, settings and configuration your business needs means a replacement machine is deployed in under an hour rather than assembled from memory, and every machine in the fleet behaves the same way. That consistency is what makes support fast, and it is one of the standing recommendations that comes out of an IT roadmap review.

The last step is the one most setups skip: securing the machine before it goes into service. Drive encryption enabled with a recovery key stored somewhere you can retrieve it, the day-to-day account made a standard user rather than an administrator, endpoint protection installed and confirmed reporting in, Windows fully patched to current before handover, and the machine joined to your management platform so it is visible from day one. Doing that at setup takes minutes. Retrofitting it across a fleet a year later takes days. There is more on the process at newpc.orcait.io.