Moving to a new Windows 11 PC now requires a little more planning if you prefer to keep your files off the cloud. According to Windows Latest, Microsoft has retired PC-to-PC Migration, the built-in setup feature that transferred files and settings directly between computers over a local network. Windows Backup remains available, but its OneDrive-based file protection is not a like-for-like replacement.
The practical takeaway is straightforward: check your folders, storage requirements and application needs before starting the new computer. You can still move files locally without buying cloud storage; what has disappeared is the guided migration experience.
What Microsoft has removed
In a November 2 report, Windows Latest’s Abhijith M B cites Microsoft release notes stating that PC-to-PC Migration is no longer available. The publication traces the removal to the September optional update and its inclusion in the October 2026 cumulative update, while noting that Microsoft describes the change as a gradual rollout.
The retired feature paired the old and new computers using a PC name and a one-time code. It then transferred selected files over Wi-Fi or Ethernet during setup of the destination PC. That made it useful for people with substantial local collections or folders outside the usual Documents and Pictures locations.
This was not a complete computer clone. Windows Latest reports that installed applications, sign-in credentials, system folders and certain other data were excluded. Nevertheless, the ability to select folders across drives offered flexibility that a predefined cloud-backup workflow does not automatically reproduce.
Microsoft has not explained the reason for retiring the feature, according to the report. The change makes OneDrive more prominent in the migration experience, but that does not establish why Microsoft made the decision.
Windows Backup: useful, but different
Windows Backup combines supported settings and app information with OneDrive folder syncing. The consumer workflow described in the report requires a personal Microsoft account, rather than a work or school account.
For files, Windows Latest identifies five supported user folders: Desktop, Documents, Pictures, Videos and Music. Downloads and custom folders elsewhere on a drive therefore deserve a separate check. Do not assume that enabling backup means every personal file on the machine is covered.
Storage is another important distinction. A free OneDrive account provides 5GB, and existing cloud content consumes part of that allowance. A local transfer instead depends primarily on available destination storage, not a cloud subscription tier. Users who already pay for sufficient OneDrive space may find Windows Backup convenient; users with large offline collections may prefer another route.
App restoration also needs careful interpretation. Remembering an app or restoring its pin does not mean transferring its installed binaries, license activation and local databases. Plan to reinstall software and verify its data separately.
Choose the migration route that fits your files
There is no need to adopt one method for everything. A mixed approach can be sensible, provided you track what each method covers.
| Approach | Suitable use | Main check before starting |
|---|---|---|
| Windows Backup and OneDrive | Supported folders already kept in the cloud | Available quota, correct account and completed sync |
| External SSD or USB drive | Large local collections or an offline move | Capacity, encryption and an independently verified copy |
| Local network share | Two working PCs on a trusted network | Share permissions, connectivity and destination space |
For a network transfer, use a trusted private network and restrict access to the intended account. Avoid opening broad guest access merely to make discovery easier. Remove temporary sharing permissions once the transfer has been checked.
A practical checklist before retiring the old PC
Start with an inventory rather than the setup wizard. Include Downloads, folders on secondary drives, exported projects, local email archives and application-specific data. For development or creative work, check working directories and libraries that may sit outside your user profile.
Next, separate the migration into three jobs:
- Files: Identify every location, measure the required storage and decide how each folder will travel.
- Applications: Gather trusted installers, license details and any vendor-supported export or migration instructions.
- Access: Confirm password-manager access, multifactor authentication and recovery options before wiping anything.
After copying, open representative documents, photos and project files on the new computer. Compare folder contents and investigate skipped-file warnings. For particularly important archives, checksum comparison can provide additional confidence that copies match.
Cloud users should verify that synchronization has actually finished, rather than treating the presence of a folder or icon as proof. If you need offline access, test it explicitly. Only erase, sell or recycle the old PC after validating the migration and retaining a separate backup.
What IT teams should change
Help-desk instructions that refer to the retired transfer option should be reviewed. A missing setup button should not become an invitation to install unverified migration utilities or disable security controls.
For managed devices, follow the organization’s approved deployment and data-transfer procedures. A consumer backup workflow tied to a personal Microsoft account is not automatically appropriate for business information. The retirement is a reason to update migration guidance, not to bypass identity, retention or data-handling policies.
The bottom line: Windows still supports ordinary local file copying. What users have lost is a convenient guided path. Choosing a transfer method in advance—and verifying files, applications and access separately—remains the safest way to make the next PC feel like a working replacement.