User migration when replacing a PC: a step-by-step guide

What is usually lost when replacing a PC — and why it hurts

When a computer is replaced, everyone worries about files. In practice, something else is often worse: accesses, settings and the little familiar things that, if missing, bring the workday to a halt. So start migration not with copying folders, but with understanding what the person really uses.

A user's “personal data” is not just documents on the Desktop. It also includes saved passwords in the browser, bookmarks, email signatures, templates, autofill history, connected network drives, printer lists and shortcuts to shared folders. Sometimes there are local databases or program config files.

The problem is much of this doesn't live in obvious places. Documents can be copied, but access to accounting systems, crypto providers, digital signing, medical systems or government portals may depend on certificates, tokens, installed modules and machine permissions. As a result, “all files are in place,” but the employee can't sign a payment, submit a report or open a patient's record.

Most often what breaks or gets lost:

• passwords and sessions (browser, mail, messengers, corporate portals)
• bookmarks, browser extensions and proxy/certificate settings
• email signatures, archives, rules and templates
• connections to network drives, permissions on shared folders, “favorite” printers
• licenses and keys bound to a device or profile

You can tell a migration succeeded by a few simple signs. You don't need to check every program — just verify what's most likely to cause downtime.

Quick signs of a successful migration:

• the user logs into Windows and corporate services without lengthy password recovery
• required network drives and shared folders open and printing works
• the browser looks familiar: bookmarks are present and needed extensions work
• email can be sent and signed as before (signature, archive, rules)
• key work applications start and find required databases or folders

If at least one of these points fails, it almost always leads to a chain of support tickets and lost time for both the employee and IT.

Preparation: a short inventory before transfer

Before you start migration, spend 10–15 minutes on an inventory. It's the cheapest way to avoid lost files, missing bookmarks and a flood of tickets the next day.

First, determine the user type. Office staff usually need mail, documents and the browser. Accounting often has accounting systems and keys. Engineers have specialized apps and large local projects. Call-center agents need quick login, a headset, telephony software and strict settings.

Next, build a short picture of what applications are really needed and where they store data. Many programs keep files not only in Documents, but also in hidden profile folders, local databases or next to the executable.

Walk through a minimal checklist and record answers (in the ticket or a simple template):

• user's role and critical tasks (what must work in the first 30 minutes)
• list of applications and where their data lives (files, databases, templates, signatures, plugins)
• where work files reside: Desktop, Documents, local folders on C or D, cloud sync
• domain and policies: installation restrictions, login scripts, encryption, proxy
• replacement window and user contact (who will confirm everything works)

Example: for a finance user, “all files” might be on the Desktop, plus Excel templates, an email signature and a certificate for signing documents. Identifying this in advance reduces time and makes acceptance smooth.

The result of preparation is simple: you know what to transfer, from where, in which order, and who confirms the new PC is ready.

Accesses and keys: what to check before the old PC is turned off

The most painful losses when replacing a computer are not files but accesses. Documents can be recovered from a network folder, but if a certificate, token or 2FA binding is lost, the employee can be stuck for hours. Walk through critical logins in advance.

Which “keys” and accesses are most often at risk

Typically at risk are:

• digital signatures and certificates (in Windows store or on a device)
• USB tokens and smart cards
• VPN clients and profiles
• application licenses (especially device-bound)
• corporate mail and messengers with login confirmation

Quickly ask the user where access “lives”: in-browser with saved password, in a password manager, as a key file, or always via a token. Migrating a profile does not always move these keys.

Before shutting down the old PC, check five things:

• which services require digital signature, certificate or token (public procurement, bank, internal portals)
• if VPN exists and whether login works without the old device
• which applications are activated on this PC and how their transfer is performed
• which logins are protected by 2FA and which phone is linked
• whether there are accesses known only to the user (personal mail, third-party accounts)

How to record accesses without “leaking” passwords

Do not ask users to send passwords in chat or save them to a file. Collect a list of systems and login methods: “mail — password in manager”, “bank — token + PIN”, “VPN — login/password + 2FA”. If you must give access to an admin, use a temporary password reset and require change on first login.

Admin access should be precise: install VPN, token drivers, transfer a license, set up a printer. For regular work it often gets in the way: users change settings and support has a harder time troubleshooting.

User profile and files: what to move and what to avoid

In migration, the main goal is to take what is truly needed for work, not to copy the entire disk. The less unnecessary data you move, the lower the chance of errors, lack of space and odd problems on the new machine.

Usually a prioritized minimum of the Windows profile is enough:

• Documents and the user's work folders
• Desktop (often contains the most important items)
• Downloads (only what is needed)
• templates: Word/Excel, signatures, user forms
• project folders if the user habitually stores them in the profile

Separately check application data that is easy to miss: local mail archives (PST/OST), databases and catalogs of accounting software, crypto provider files and key containers (if stored locally), user note databases. A good question for the user: “Which program is most ‘special’ for you and where does it store data?” Often one important file surfaces that nobody remembered.

Don't copy everything. On a new PC this is almost never necessary and only brings problems:

• temporary folders and browser cache
• entire AppData (unless absolutely needed)
• old installers, duplicate movies and photos
• Recycle Bin and system folders

If space is limited, don't compress everything blindly. Agree on logic: what to transfer now, what to archive, and what can be re-downloaded or restored from shared resources.

At the end, check permissions. A common situation: files are copied but the new PC shows “access denied.” This happens due to folder ownership or inheritance. A quick check is to open transferred folders under the user's account and confirm they can read and modify files.

Bookmarks, mail and the small work items that are forgotten

Document loss is noticed immediately, but small things show up a day or two later: a needed site won't open, a signature is gone, autocorrect is missing, a messenger asks to be set up again. Migration often turns into a string of minor support tickets for these reasons.

Browser bookmarks and passwords

Often it's easier to restore sync access rather than browser files. If company browser accounts are allowed, bookmarks and extensions usually sync after sign-in.

If there's no sync, export bookmarks to a file and import them on the new PC. Passwords are harder: built-in password managers sometimes only transfer when sync is enabled. If the user uses a separate password manager, confirm they know the master password and recovery options.

Mail: accounts, signatures, rules

What is often forgotten with mail is not login credentials but the “peripherals”: signature, out-of-office, sorting rules, local archives. In Outlook some users have PST archives or personal folders that are not on the server. They must be found and moved separately or years of mail history will disappear.

Ask the user to show where the archive is and send a test message. Don't forget calendars and shared mailboxes if they were added manually.

Messengers and office habits

Teams, Slack and other corporate messengers usually restore chats after login, but local downloads, favorites, notification settings and pinned folders may not transfer. Check the Downloads folder and Desktop separately — important files often end up there.

To avoid losing templates and habits, gather the rarely-remembered items in advance:

• Word/Excel templates, macros and personal add-ins
• auto-corrections and custom dictionary
• email signatures and templates
• pinned folders in File Explorer, Quick Access
• important files in Downloads and on the Desktop

After transfer, do a short check with the user:

• log into mail and send a test message to themselves
• ensure signature appears and the From address is correct
• open the calendar and create an invite
• access key sites from bookmarks
• log into the messenger and check notifications

This closes most non-obvious issues at handover rather than during the workday.

Network drives, shared folders and printers after replacement

After a PC swap, it's usually not the files that break but the familiar paths: shortcuts pointing to Z: may not find that drive on the new machine, or it may be mapped differently. Migration should therefore include restoring network resources.

Network resources come in different forms:

• departmental shared folders (documents, templates, scans)
• user home folders on the server
• project catalogs with restricted access
• shared application storage (databases, exchanges, exports)

Rule of thumb: restore the same drive letters and paths the user is used to. If “Projects” opened as P: before, map them as P: again, not “however it's easiest.” Then existing shortcuts, Excel macros and program paths keep working.

After mapping, verify permissions. It's not enough that the folder opens. Ask the user (or test under their account): open a file, create a test folder, save into it and delete it. This quickly shows the difference between read access and full working access.

Don't rely on automatic installation for printers and scanners. Even if the device appears, perform a quick test: print a test page and verify printing from the actual work application. For scanning, ensure the usual scanning app runs and saves to the expected folder.

If a network resource opens in File Explorer but the application doesn’t see it, common fixes include:

• use a UNC path (\server\share) instead of a drive letter
• remap the drive after login and enable “Reconnect at sign-in”
• remove stored credentials and log in again
• check that the application is not running “as a different user”
• ensure the application has write permission, not just read

These checks take minutes but greatly reduce support tickets in the first days after a PC replacement.

Step-by-step PC replacement scenario: from start to acceptance

To prevent migration turning into a string of urgent calls, follow the same scenario every time. The logic is simple: agreements and accesses first, then data, then conveniences.

First, set expectations. Which tasks must the user complete on the replacement day (payments, reports, lessons, patient intake)? Agree that the old PC won't be wiped until the transfer is accepted.

Then follow these steps.

1. Agree the work window and acceptance criteria: what must work at the end (mail, 1C/ERP, VPN, printer, network drives).

2. Prepare the new PC in advance: updates, baseline settings, antivirus/EDR, timezone, keyboard layout, required policies. Create the account or verify domain login. This matters for both spot replacements and fleet refreshes.

3. Transfer by priority: first accesses and logins, then work files, and only afterward applications and minor settings. If in doubt, copy a bit more temporarily but don't mix old and new folders without checks.

4. Connect the environment: network, Wi-Fi (if needed), VPN, network drives, shared folders, printers. Immediately test login to 2–3 key systems the user opens daily.

5. Do a short acceptance with the user: 10–15 minutes at the workstation. Let them sign in, open mail, access a key folder, print a test page and run a work app. Record what remains unfinished and when it will be completed.

Only after that keep the old PC as a backup for an agreed period (usually 3–7 days). This provides a clear fallback if a rare program, token or template is remembered later.

Quick checks after transfer: a 10-minute checklist

After migration, don't hand over the new computer “as is.” Spend 10 minutes on a quick check — it catches most problems immediately and reduces urgent tickets on the first workday.

Checks to confirm "it works like before"

• Log into mail and 1–2 corporate portals, then open the main work system (accounting, CRM or ticketing). If second-factor, token or new password is requested, resolve it then.
• Open 2–3 typical files: a spreadsheet, a branded presentation and the most commonly printed file. Check fonts, logos and template availability.
• Verify network drives and shared folders: open a folder, create a test file, rename it and delete it.
• Do a test print on the required printer. If scanning is used, perform a test scan to the usual location.
• If digital signatures or certificates are used, perform a short test: sign a test document or log into the service. Make sure the certificate is visible and crypto-provider plugins work.

What to record so you don't roll back blindly

Even with a careful transfer, leave insurance and an audit trail:

• ensure a backup of critical folders was actually created and note where it is stored
• record 2–3 results of the checks ("mail logged in", "network verified", "printing OK") and list minor problems (what failed and what error was shown)
• in environments with strict requirements, ask the user to complete one real task: send an email with an attachment or print a standard document

Common migration mistakes and how to avoid them

Most post-replacement problems are not due to copying files but to surrounding details: accesses, certificates, network resources and lack of user acceptance.

• Transferred documents but forgot accesses, certificates and keys. Mail doesn't connect, digital signing fails, bank client won't run. Solution: list critical systems and login methods in advance, check certificate expiration and storage (PC, token, browser profile).
• Old PC was retired or wiped too early. A day later someone discovers a local template, database or saved password. Solution: keep the old PC as a backup for 3–5 working days or until acceptance, and make a backup from an agreed list.
• Copied the entire Windows profile without filtering. Along with needed data you get errors, junk, old drivers and broken settings. Solution: copy data and clear settings (Documents, Desktop, templates, necessary app folders) and reinstall programs from a controlled list.
• Didn't check network drives and permissions. On day one everything looks fine, later it's found there are no rights to a shared folder or shortcuts didn't restore. Solution: right after transfer open 2–3 key folders, test write/read and ensure drives are mounted the same way.
• No acceptance with the user. Technician leaves and the user later remembers things that don’t work. Solution: a short 10-minute acceptance: mail, printing, 1C/ERP, signature/certificate, network shares.

Another source of chaos is using one scenario for all users. Accounting needs certificates and bank clients, engineers need CAD and licenses, call-centers need headsets and telephony. Group users by roles and keep a mini-checklist for each role: replacements will be quieter and more predictable. Record exceptions in the ticket or workstation card rather than in people's heads.

A practical example: replacing a PC for a finance employee

Typical situation: a bookkeeper gets a new PC. Every day she uses mail, an accounting system (e.g. 1C), a bank client and several shared folders with primary documents. Any missing item becomes an urgent support request.

Before starting we inspected the old PC and found three risks: some documents were on the local Desktop, bookmarks pointed to portals (bank, e-invoices, internal instructions), and the signing certificate was stored in the Windows profile rather than on a token. Network shares were mapped to \server\fin and there was a separate archive folder.

We chose a simple order. First record exactly what to transfer and move local files to corporate storage. Then export bookmarks, locate and export the certificate, and only after that set up the new PC (standard office image and domain join).

Acceptance checks with the user included:

• necessary emails and attachments open and search works
• accounting system launches and authorizes, printing works
• the bank client sees the certificate and signs a test document
• network folders connect with read/write access
• a test page prints to the required printer

The whole process took about 70 minutes from shutting down the old PC to acceptance. One remaining task was to update a signing plugin in the browser later. The user started work without downtime and support didn't have to troubleshoot dozens of "missing files" or "Can't see the drive" tickets.

What to do next: standards, support and calm PC replacements

A one-off migration often becomes a fire. To make PC replacement routine, formalize it: one template, clear roles and uniform rules. Then transfers take less time and produce fewer surprises.

Create a short internal standard (1–2 pages) and assign responsibilities: who prepares the old PC, who configures the new one, who accepts it with the user. Include in the standard:

• an inventory template (accounts, printers, network drives, apps, special folders)
• rules for where work files must be stored (on network or corporate storage vs local)
• procedure for documenting exceptions (rare software, custom plugins, special permissions)
• minimum post-transfer checks and a feedback window (e.g. 3 working days)

Agree on standard software bundles by role: accounting, sales, engineers, managers. The fewer manual installs and “one more tool please” requests, the fewer tickets. Document exceptions in the ticket or workstation card.

To keep data safe, adopt a simple policy: work documents live not on the Desktop but in a backed-up, accessible location. This eliminates half of the risks even if the old device fails.

Planned fleet replacement also helps: maintain a schedule and a small reserve of spare machines. When buying new workstations, agree on compatibility and support requirements (drivers, service, unified images) in advance.

If fleet refresh coincides with infrastructure changes (workstations, servers, regional support), coordinate with a systems integrator. For example, GSE.kz (gse.kz) as a manufacturer and integrator in Kazakhstan supplies work PCs, all-in-ones and servers and supports deployment and maintenance, which helps make replacements more predictable for IT and users.