Microsoft has quietly introduced a local PC-to-PC migration feature directly inside the Windows Backup app, letting users move files and personalization settings from an old computer to a new Windows 11 device over a local network during initial setup. The update, first spotted in Windows 11 version 2024 and later builds, revives the spirit of the long-departed Windows Easy Transfer—but with modern security and a focus on user files rather than full system cloning.

This new transfer path eliminates the need to upload large libraries to OneDrive or purchase third-party migration tools, though it comes with specific limitations that every user should understand before starting. Here’s exactly how it works, what gets moved, and how to avoid common pitfalls.

Background

For years, migrating to a new PC has been a fragmented experience. OneDrive sync covers Documents, Pictures, and Desktop for those with enough cloud storage, but anyone with larger local libraries had to resort to external drives, File History, or paid software. Enterprise environments use tools like the User State Migration Tool (USMT), but nothing comparable existed for consumers since Microsoft retired Windows Easy Transfer after Windows 7.

The refreshed Windows Backup app changes that. During the Out-of-Box Experience (OOBE) when you set up a new Windows 11 PC, a new option appears: “Do you want to transfer information from another PC?” Selecting it initiates a local network transfer that pulls files and selected settings from the old machine, provided both are signed into the same Microsoft account and meet the requirements below.

What you need before you start

Minimum system and account requirements

  • The old PC can run Windows 10 or Windows 11, and must have the latest Windows Backup app (update through Settings > Windows Update).
  • The new PC must run Windows 11, version 2024 or later; earlier builds do not offer the local transfer option.
  • Both machines must be signed in with the same Microsoft account during setup. Importantly, that account must not already contain an existing Windows cloud backup—if one is detected, the OOBE flow will default to cloud restore and skip the local pairing screen.
  • Both PCs must be on the same local network (Wi-Fi or wired Ethernet), and they must be on the same subnet so Discovery can locate the source machine.
  • Use a wired Gigabit Ethernet connection for speed and reliability. Large transfers over weak Wi-Fi can stall or take many hours.
  • Plug both devices into power to prevent sleep interruptions.
  • Temporarily disable VPNs and aggressive firewalls that might block local device discovery.
  • Decrypt any BitLocker-encrypted drives you plan to transfer—BitLocker-protected volumes are automatically excluded from the local transfer. Decryption can take significant time depending on the drive size, so plan ahead.

Exactly what moves (and what doesn’t)

Understanding the scope of the transfer will prevent surprises after the migration.

Files and settings that do transfer

  • All personal files located in your user folders—Documents, Pictures, Videos, Desktop, Downloads, Music—across all non-BitLocker encrypted drives.
  • Personalization settings such as wallpaper, themes, taskbar configuration, and many system preferences that make the new PC feel familiar.

Items explicitly excluded

  • Installed third-party programs (classic Win32 apps) are not transferred. You must reinstall those manually on the new PC. Some Microsoft Store apps may be restored through your Microsoft account library, but most traditional desktop applications need fresh installation.
  • System and OS files (Program Files, ProgramData, Temp, and Windows folders) are skipped.
  • Saved passwords and sign-in credentials are deliberately omitted for security. Browser sync or password-manager cloud services remain the recommended way to carry those across.
  • OneDrive-stored files are skipped because they are intended to sync from the cloud once you sign back into OneDrive on the new PC. Keep in mind that the free OneDrive tier is limited to 5 GB, so if you have a large library, a paid Microsoft 365 plan may be required to restore everything from the cloud.
  • BitLocker-encrypted drives—even if unlocked—are excluded until fully decrypted.

If your primary goal is to move installed applications and their licenses intact, consider full-disk cloning with tools like Macrium Reflect or Acronis, or use a commercial migration utility such as PCmover. Note that cloning across significantly different hardware can cause driver and activation issues, and commercial tools often require license reactivation after transfer.

Step-by-Step: Moving Files from an Old PC to a New Windows 11 PC

Follow this sequence carefully. The transfer pairing flow is only available during the initial Windows setup (OOBE) or when you first add your Microsoft account to a fresh install. If you’ve already set up the new PC, you may need to reset it to see the prompt.

On the old PC (source)

  1. Update Windows and the Windows Backup app: Go to Settings > Windows Update > Check for updates. Install all pending updates; the transfer option may not appear on older builds.
  2. Open Settings > System > Backup > Windows Backup, or launch the Windows Backup app directly. Select “Transfer to a new PC” (or “Transfer information to a new PC”).
  3. Note the PC name displayed. You’ll use this to identify the source machine during pairing. Keep this screen open.

On the new PC (target) during setup

  1. When the OOBE asks “Do you want to transfer information from another PC?”, choose the option to transfer. Sign in with the exact same Microsoft account used on the source, and confirm that account has no existing cloud backup—otherwise you won’t see the local transfer path.
  2. The new PC will display a one-time pairing code.
  3. Back on the old PC, enter that code to establish a secure connection. The devices will pair over the local network.
  4. After pairing, the new PC shows a selectable list of folders and settings available for transfer. Expand the tree to review what’s included. A storage gauge warns if the destination lacks free space; deselect large folders if necessary.
  5. Click “Start transfer.” A progress bar and estimated time appear. Windows attempts to resume interrupted transfers automatically, though a stable wired connection is best.
  6. Wait for the completion summary before moving on.

After the transfer

  • Sign back into OneDrive on the new PC to re-sync your cloud files.
  • Reinstall desktop applications and restore licenses. To speed this up, export an app list from the old PC with winget export (Command Prompt) and use winget import on the new PC to batch-install available packages. Many apps will still require re-authentication.
  • Verify critical files by opening a few samples. Keep a fallback copy of the source data on an external drive until you’re satisfied the transfer was complete.

Performance and reliability: how fast is it?

Transfer time depends entirely on the amount of data and network throughput. Real-world scenarios show:
- Wired Gigabit Ethernet: ~100–110 MB/s sustained. A 100 GB transfer finishes in 15–20 minutes, assuming no other network congestion.
- Wi‑Fi 5/6: Throughput varies greatly—anywhere from 10 MB/s to 50 MB/s in typical home environments. The same 100 GB could take 30 minutes to over an hour, and intermittent drops may cause pauses.
- Weak Wi‑Fi or public hotspots: Not recommended; transfers often stall and fail to resume cleanly.

For libraries exceeding several hundred gigabytes or terabytes, copying to an external SSD or HDD first is often faster and more reliable. Format the external drive as exFAT or NTFS to avoid the 4 GB file-size limit of FAT32.

Troubleshooting common problems

  • Transfer option missing during setup: Confirm both PCs have the latest updates, and the new PC is running Windows 11 version 2024 or later. Check that your Microsoft account doesn’t already hold a cloud backup (manageable via account.microsoft.com). If all else fails, reset the new PC and try again.
  • Pairing fails or code not accepted: Ensure both devices are on the same private network and not isolated by guest network settings, VPNs, or strict firewall rules. Temporarily disable VPNs and third-party security suites during pairing (re-enable them afterward).
  • Transfer stalls or interrupts: Switch to a wired connection. In extreme cases, restart the process and break the migration into smaller batches by manually copying the largest folders with an external drive before running the transfer for the rest.
  • BitLocker drives excluded: You’ll need to decrypt the drive before the transfer app will recognize it. Decrypt via Settings > Privacy & Security > Device encryption or BitLocker Drive Encryption. Be patient; decryption can take hours on large drives.

Security and privacy analysis

The transfer flow introduces several safeguards:
- The one-time pairing code displayed on the new PC must be manually entered on the old PC. This prevents rogue devices on the same network from impersonating a legitimate target.
- Both machines must sign in with the same Microsoft account, tying the transfer session to a known identity.
- Data moves directly over the local network; files are not routed through Microsoft’s cloud. However, metadata about the backup (folder structure, settings) is associated with your Microsoft account to enable future restores.
- Saved passwords and credentials are intentionally omitted, reducing the risk of sensitive data exposure during migration.

For users with strict privacy requirements, the fully offline external-drive method (copying files to a USB drive without any Microsoft account interaction) provides complete isolation from online services.

Alternatives and when to use them

Windows Backup’s local transfer isn’t the only option. Choose based on your data size and app migration needs:
- OneDrive cloud sync: Ideal if you already have a Microsoft 365 subscription and your critical files fit within your storage quota. The restore is seamless during OOBE, but you’ll hit limits quickly with the free 5 GB tier.
- External drive copy: Best for very large libraries (hundreds of GB or more) and full control. Manually drag folders to an exFAT/NTFS drive, then copy them to the new PC. No network dependency, and it’s faster for massive data sets.
- Disk cloning (Macrium Reflect, Clonezilla, Acronis): Clones everything—OS, apps, settings—perfect for replacing a drive in the same machine. When moving to dissimilar hardware, a clone may result in driver conflicts or Windows activation problems.
- Commercial migration tools (Laplink PCmover, Zinstall): Attempt to move installed applications automatically. Results vary by application complexity; many programs still require license reactivation. Always test with a verified backup first.

Practical checklist before you begin

Run through these every time to avoid losing data or hitting dead ends:
1. Create a verified backup of essential files on an external drive (and optionally a second copy in the cloud).
2. Decrypt any BitLocker- or device-encrypted drives you want to transfer.
3. Update both PCs and confirm the new PC is on Windows 11 version 2024 or higher.
4. Plug both machines into power and prefer a wired Ethernet link.
5. Export an application list with winget export and gather installers/licenses for apps that need manual reinstall.
6. Verify that your Microsoft account has no existing backup if you intend to use the local OOBE transfer path.

Strengths, weaknesses, and final assessment

The local transfer feature brings genuine convenience: it’s baked into Windows setup, avoids cloud uploads, and preserves the look and feel of your old desktop. For non-technical users, the wizard dramatically lowers the barrier to upgrading.

Yet, it’s not a universal solution. The exclusion of installed apps, passwords, BitLocker drives, and system files means you’ll still need to reinstall software and reconfigure some services. The dependency on a Microsoft account and a specific Windows 11 build may frustrate users on older versions or those who prefer local accounts. And while the network transfer works, it demands a stable connection—unstable Wi-Fi can turn a quick migration into a troubleshooting ordeal.

Independent reports and early user experiences highlight that the feature is being rolled out gradually, and some devices may not see the option even when on supported builds. As with any new functionality, treat the local transfer as a powerful convenience tool, not a complete replacement for a careful, multi-pronged migration plan.

Conclusion

Windows Backup’s PC-to-PC transfer is the simplest first-party migration method Microsoft has offered in over a decade. It shines when you’re moving from a Windows 10 or 11 machine to a brand-new Windows 11 device and your data lives in user folders rather than complex application ecosystems. Used alongside an external backup, an app reinstallation list, and a wired network, it can slash the time and effort of setting up a new PC.

For mission-critical data, always verify the results and keep a secondary copy until you’re certain. Despite its limitations, this built-in flow marks a welcome return of a user-friendly, local migration path—one that finally reduces dependence on paid utilities or cloud bandwidth for the most common upgrade scenario.