To migrate a user to a new computer, prepare the new PC with Windows updates and the staff member's account, record what their old PC relies on (mapped drives, printers, email data, signatures and bookmarks), move their files and settings, then let them sign in and check everything before the old PC is wiped. Doing it the same way every time is what makes it fast and stops things going missing.
This guide is for small businesses without a dedicated IT team, or with one person who looks after the PCs. It gives you a repeatable process you can use for every PC swap.
Before you start: what to record on the old PC
The files are rarely the problem. What staff notice on day one is the small stuff: a missing drive letter, a printer that is not there, an email signature that has vanished. Spend a few minutes recording these on the old PC while the staff member is signed in.
| Item | How to find it |
|---|---|
| Mapped network drives | Run net use in Command Prompt to list drive letters and their paths |
| Printers and the default printer | Settings > Bluetooth & devices > Printers & scanners |
| Outlook data files | Outlook (classic): File > Account Settings > Account Settings > Data Files; often in Documents\Outlook Files |
| Email signatures | C:\Users\Name\AppData\Roaming\Microsoft\Signatures |
| Office templates | C:\Users\Name\AppData\Roaming\Microsoft\Templates |
| Moved folders | Right-click Documents and Desktop, Properties > Location |
| Local work folders | Check This PC for other drives and folders such as C:\Scans |
| Installed software and licenses | Settings > Apps > Installed apps, plus your license records |
Ask the staff member too. "Is there anything you open every day that is not in Documents?" turns up more than any checklist. License keys are worth gathering early; see how to find software license keys on the old computer.
How to migrate a user to a new computer, step by step
- Prepare the new PC. Run Windows Update, install drivers, and join it to your domain or work account system if you use one.
- Create or sign in to the staff member's account. Have them sign in once so their profile is created. Settings like signatures and wallpaper belong to a user account, so the account must exist first.
- Install their programs. Use your software list and install from the publisher or your licensing portal. Leave sign-ins for the staff member.
- Move the files. Copy Documents, Desktop, Pictures, Downloads and any local work folders, using the real paths you recorded.
- Move email data. For Outlook (classic) with local PST files, copy them across and attach them with File > Open & Export > Open Outlook Data File. Microsoft 365 or Exchange mailboxes re-sync when the user signs in.
- Recreate drives and printers. Map each drive with This PC > Map network drive using the paths from
net use, and add the network printers. - Restore bookmarks and signatures. Export and import bookmarks in each browser, and copy the Signatures folder into the same place on the new PC.
- Hand over and check. Have the staff member sign in to their apps and open the files and shared folders they use most.
- Keep the old PC unchanged for an agreed period, then wipe it.
What do staff most often lose on a new PC?
- Mapped drives. The share still exists but the drive letter does not, so shortcuts and linked spreadsheets break.
- Printers. Especially the default printer, and USB printers that need their driver installed.
- Email signatures and templates. They live in hidden AppData folders, not in the mailbox.
- Bookmarks. Particularly if browser sync was never turned on.
- Desktop files. Many people keep live work on the desktop.
Saved passwords and two-factor authentication apps also need attention. Make sure staff can sign in to their authenticator on a new device before the old one is wiped.
How long does a staff PC migration take?
It depends mainly on how much data the person has and the connection used. A wired network or a fast USB drive keeps the copying short. The parts that take longest are usually manual: hunting for folders, re-mapping drives and setting up printers. Recording everything up front and following the same order each time is what saves the most time.
Keep a record of each migration
Write down the date, the old and new PC names, what was moved, and anything that failed. If someone says weeks later that a folder is missing, you can check the record instead of guessing. Also agree how long the old PC is kept before wiping. When it is time, use Settings > System > Recovery > Reset this PC > Remove everything with the clean-drive option. Our guide on what to do with the old PC covers this.
Doing it with Computer Copier
Computer Copier turns most of the steps above into one transfer you can repeat for each staff member. Install it on both PCs, sign in to the new PC as the staff member, and run it there. It asks for administrator permission once when it starts, so have admin credentials ready. Settings are applied to the Windows account that runs it on the new PC, while Wi-Fi networks and printers are machine-wide.
- Files from Documents, Desktop, Pictures, Downloads and other folders, including folders moved to D: or into OneDrive, plus any folder you add.
- Outlook PST files, Thunderbird profiles, Microsoft Office templates and signatures, and browser bookmarks.
- Mapped network drives, network printers and the default printer, saved Wi-Fi networks and regional settings, each ticked individually.
- A Programs page listing everything installed on the old PC, flagging programs that usually need a license key.
- A transfer report you can save as PDF for your records, a migration checklist, and an undo for files and settings if needed.
The old PC is only read from, so nothing changes on it until you decide to wipe it. For a full walkthrough, see the quick start.
Frequently asked questions
How long does it take to migrate a user to a new PC?
It depends mainly on how much data they have and the connection used. A wired network or fast USB drive keeps it short.
What do staff most often lose when they get a new PC?
Mapped drives, printers, email signatures, browser bookmarks and files saved on the desktop.
Should IT keep a record of each migration?
Yes. A transfer report showing what moved and anything that failed helps if a user later says something is missing.
