Windows Backup Local PC-to-PC Migration: What Moves, Tips, and Limits

Microsoft’s refreshed Windows Backup now offers a built‑in, local PC‑to‑PC migration path that makes moving your personal files and many settings from an old Windows PC to a new Windows 11 machine far less painful than past upgrades — but it is not a silver bullet, and there are important limits, prerequisites and practical tips every upgrader should know before they begin.

Background​

Microsoft has been iterating on first‑party migration options for years. The new flow appears inside the Windows Backup app and adds a local transfer mode that pairs two nearby PCs over the same local network and moves user folders and personalization during Windows 11 setup (OOBE) or from Settings after setup. This is intended as a consumer‑friendly analogue to older utilities such as Windows Easy Transfer and as an alternative to uploading large libraries to OneDrive or buying third‑party migration tools.
The headline appeal is obvious: avoid long cloud uploads and OneDrive storage limits by copying files directly across your LAN. For many home users and small offices this reduces time, cost and complexity — but the migration’s behavior, exclusions and rollout status are important to understand so you don’t lose time or data during a critical upgrade.

---

What you need before you start​

Minimum system and account requirements​

• The source (old) PC must be running Windows 10 or Windows 11 and have the Windows Backup app available and updated.
• The target (new) PC must be running Windows 11 (version 2024 or later) to expose the local transfer path during setup. If your new PC is on an older Windows 11 build, the pairing option may not appear.
• Both machines must be on the same local network (same subnet) and reachable by each other — wired Ethernet or the same private Wi‑Fi network. Wired Ethernet is strongly recommended for large transfers.

Account and cloud preconditions​

• You must sign in with the same Microsoft account on both devices during the pairing/restore. If your Microsoft account already contains an existing Windows cloud backup, the setup flow may prefer the cloud restore path instead of the local-only pairing. Plan accordingly.

Optional but strongly recommended​

• Plug both PCs into power and prefer wired Gigabit Ethernet for the transfer. Using Wi‑Fi 5/6 can work but is less predictable. Pause VPNs and aggressive firewalls that can block local discovery.
• If any drives are encrypted with BitLocker or device encryption, decrypt them first. Encrypted volumes are excluded from the transfer unless decrypted.

---

What Windows Backup will — and will not — move​

Understanding the scope of the migration is the single most important planning step.

What will move​

• Personal files in user folders — Documents, Desktop, Pictures, Videos, Music and similar user folders (on volumes that are not BitLocker‑encrypted).
• Many personalization and Windows settings — wallpaper, themes, some system and personalization preferences that make the new PC feel familiar.

What will not move​

• Classic Win32 desktop applications (Program Files, ProgramData, installed binaries) are not transferred; you must reinstall them on the new PC. Microsoft Store apps may be restored separately through your Microsoft account library.
• System/OS files and system partitions — the transfer is not a full disk clone or image restore.
• Saved passwords and many credentials — for security reasons, many sign‑in credentials are not migrated; browser/service password sync depends on each service’s cloud sync.
• OneDrive‑stored content is not copied by the local transfer; those files sync back when you sign in on the new PC, but relying on the cloud requires adequate OneDrive quota (free tier is limited).

If you need a 1:1 replica of the old machine including installed programs and drivers, consider disk cloning/imaging or a commercial migration tool — both approaches have tradeoffs and are discussed later.

---

The step‑by‑step migration (local PC‑to‑PC transfer)​

Below is the practical sequence you’ll follow to move files and settings using Windows Backup’s local transfer flow. Use these numbered steps during a planned migration to keep the process predictable.

• Update Windows on both PCs: Settings > Windows Update > Check for updates. The transfer option can be missing on older builds.
• On the old PC (source): open Settings > System > Backup > Windows Backup, or launch the Windows Backup app directly. Select “Transfer to a new PC” and note the PC name that appears; you’ll use it during pairing. Keep this screen visible.
• On the new PC (target) during OOBE (Out‑of‑Box Experience) or in Settings after setup: sign in with your Microsoft account and choose the option to restore or transfer information from another PC when prompted. If you already completed setup, you can open Settings > System > Backup > Windows Backup to initiate restore.
• The new PC will display a one‑time code. Back on the old PC, enter that code to pair the devices (or, in some flows, enter the old PC’s name on the new PC). This pairing authenticates the session.
• Once paired, the new PC shows a selectable list of folders and settings available to transfer. Expand the categories, check/uncheck items, and ensure the target machine has enough free storage. The wizard will warn you if space is insufficient.
• Click Start transfer and wait. A progress indicator and estimated time appear. Windows will attempt to resume interrupted transfers automatically.
• When complete, review the backup summary, spot‑check critical files (open a few documents and photos), sign into OneDrive on the new PC to re‑sync cloud files, and reinstall desktop applications. Keep the old PC or backup copy until you’ve fully verified the migration.

---

Performance expectations and network guidance​

Transfer time varies significantly with dataset size and network bandwidth.

• On wired Gigabit Ethernet you can expect ~100–110 MB/s real‑world throughput; under ideal conditions, a 100 GB transfer may finish in roughly 15–20 minutes. This is the fastest consumer scenario if both endpoints and the network support gigabit speeds.
• On Wi‑Fi (Wi‑Fi 5/6) practical throughput is much more variable — expect slower speeds and more variability, and plan for transfers to take minutes to hours depending on signal strength and interference. For large libraries, wired is usually faster and more reliable.
• For very large datasets (several hundred GB or TB), an external SSD/HDD copy (USB 3.x or NVMe enclosure) is often faster and less error‑prone: copy locally, verify, then plug into the new PC and restore.

Practical network tips

• Use a direct wired connection where possible; if both PCs have gigabit Ethernet, connect them via the same router or, for even faster direct speeds, connect via a switch or a direct cross‑over capable cable if available.
• If you must use Wi‑Fi, put both devices close to the router, disable background downloads/updates, and avoid congested channels. Pause VPNs that tunnel traffic off the LAN.

---

Safety checklist and pre‑migration tasks​

Before you start any transfer, do the following to avoid surprises.

• Make a verified backup: copy the most important files to an external drive or cloud as a fallback. Never rely on a single copy during a migration.
• Decrypt BitLocker or device encryption for any volumes you want included. Encrypted volumes are excluded from the local transfer.
• Export an app inventory: run winget export on the old PC to create a manifest of installed packages you can later import on the new machine with winget import. This won’t reinstall everything but speeds up reinstallable packages that support winget.
• Note license keys and installer URLs for paid software. Many commercial apps need reactivation after reinstall.
• Clean up: delete unwanted files, clear temporary folders and browser caches to reduce transfer size. Consolidate scattered files into standard folders to make selection easier.

---

Reinstalling apps: realistic options and automation tricks​

Because classic desktop apps aren’t migrated automatically, consider these approaches to reduce reinstall pain.

• Use winget export on the old PC to capture a list of UWP and supported Win32 packages, then use winget import on the new PC to reinstall what’s available from repositories. This automates many common tools but won’t cover custom installers or licensed binaries requiring manual activation.
• For apps not available via winget, gather installers and license keys before wiping or decommissioning the old PC. Keep a secure copy of serials and vendor accounts.
• If you need a near‑complete migration of installed programs, commercial tools like PCmover or service‑level cloning may be used — but results vary and license reactivation is often required. Always test on a non‑critical app first and have a verified backup.

---

Troubleshooting common problems​

• Transfer option missing during setup: make sure both PCs have the latest updates and that the new PC runs the required Windows 11 version. Rollout is phased; the feature may not be present on every device immediately.
• Pairing fails or devices don’t discover each other: confirm both devices are on the same private network/subnet, disable VPNs and temporarily turn off firewalls that may block local discovery.
• Transfers stall or drop mid‑way: switch to wired Ethernet if possible; check cables and network hardware; verify no background process (antivirus, update services) is saturating the network. Windows will try to resume a stalled transfer but having a wired connection reduces risk.
• OneDrive quota errors: if you selected the cloud path and run out of OneDrive space, the cloud restore can fail. Either purchase additional OneDrive storage, use the local transfer path, or copy large media via external drive.

---

Security and privacy considerations​

• The pairing process uses a one‑time code to authenticate the two endpoints; keep the code private and perform the transfer on a trusted, private network to avoid interception.
• Encrypted volumes are excluded — this protects data but also means you must decrypt temporarily to include those files. Only decrypt if you fully control the environment and remember to re‑enable encryption afterward.
• Saved passwords and credentials are typically not migrated. Use each application’s secure sync (for example, browser sync or a password manager) to restore credentials safely.

---

Alternatives to the Windows Backup local transfer​

If the built‑in flow doesn’t meet your needs, consider these established options.

• External drive copy (recommended for very large libraries): Plug in a USB 3.x / USB‑C / Thunderbolt drive, copy folders to it, and restore them on the new PC. Format as exFAT or NTFS to avoid FAT32’s 4 GB file size limit. This is fast, reliable and under your control.
• Full disk cloning/imaging: Use tools like Macrium Reflect, Acronis or Clonezilla to make an image of the old disk and restore it to the new one. This preserves apps and system state but can create driver and activation issues on different hardware. Use when you need an identical environment.
• Commercial migration tools: PCmover and similar products attempt to move installed programs and settings. They can save time but are paid products and cannot guarantee success across all apps or licensing scenarios. Test and keep backups.

---

When the built‑in flow is the best choice — and when it isn’t​

Use Windows Backup local transfer when:

• You primarily need to move personal files, photos and documents and want a guided, in‑place migration during OOBE.
• You want to avoid OneDrive upload bandwidth or paid cloud storage for large libraries.

Avoid relying on the built‑in flow (alone) when:

• You must preserve installed legacy applications and driver configurations exactly as they were; cloning or commercial migration may be necessary.
• A target machine’s build or patch level does not yet include the receiving code — the feature is rolling out in phases and availability can vary by channel and device. If you’re on a tight schedule, have an external drive fallback ready.

---

Pro tips from power users​

• Use Robocopy for precise, resumable local copies to an external drive: robocopy "C:\Users\OldUser\Documents" "E:\Backup\Documents" /MIR /ZB /R:3 /W:5 /LOG:C:\Logs\robocopy.log. Robocopy is robust for large transfers and allows scripted migrations.
• Keep the old PC as a fallback (offline) until you’ve fully verified that everything you need is on the new PC. Don’t wipe or donate the old machine immediately.
• Export a winget manifest before you start and use it to re‑provision many common apps quickly on the new device. This avoids hunting down dozens of installers manually.

---

Known rollout and support caveats​

Microsoft’s migration experience is being deployed in phases. Some users may see the source UI before the receiving code is available on certain devices or Windows channels, causing confusion if the new PC can’t be discovered during setup. If you run into inconsistent availability, update Windows, check your Windows 11 build, and prepare a reliable external backup as a fallback. Treat the built‑in local transfer as a powerful convenience — but not yet a universal guarantee for every device and scenario.

---

Final assessment and recommended workflow​

Windows Backup’s PC‑to‑PC migration is a solid, user‑friendly addition to the Windows toolbox. For the majority of users who primarily want to move documents, photos, and personalization to a new Windows 11 machine, this reduces friction and removes the need for paid migration apps in many cases. Its strengths are integration into setup (OOBE), local network transfers that avoid OneDrive limits, and a simple pairing code that authenticates the session.
However, important limitations remain: classic desktop applications, encrypted volumes, saved credentials and some specialized app data are not moved. The feature is rolling out in phases and requires the new PC to be on a recent Windows 11 build. Anyone planning a migration should follow a pragmatic, three‑step approach:

• Prepare: update both machines, decrypt BitLocker volumes you plan to transfer, export app manifests, and make a verified external backup.
• Use Windows Backup local transfer: pair the devices over a private network, select folders and settings, and run the transfer — preferably over wired Ethernet for large datasets.
• Verify and finish: spot‑check files, sign into OneDrive and services, reinstall and reactivate desktop apps (use winget where possible), and only then retire the old PC after keeping a fallback copy for a short period.

If you follow that checklist, the built‑in Windows Backup migration will handle the tedious parts while you keep control of the parts that require manual attention. Use the local transfer for convenience, pair it with an external verified backup for safety, and plan to reinstall and reactivate legacy desktop applications manually. When done carefully, this approach will get you using your new PC quickly and confidently without spending extra on third‑party migration services.

---

Windows upgrades rarely require perfect solutions; they need practical, reliable workflows. The updated Windows Backup gives most users a clear, safe path to move their data locally — but it’s most effective when used as part of a deliberate migration plan that includes backups, decryption of encrypted volumes when needed, and a pragmatic strategy for reinstalling apps.(Note: specific availability, UI wording and exact behavior may vary by Windows 11 build and Microsoft’s phased rollout. If you encounter an unexpected result in your environment, check for the latest Windows updates and retain an external backup before proceeding.)

---

Source: Mint How to use Windows Backup to move data to new Windows 11 PC effortlessly | Mint