It is not, however, evidence that the tool has disappeared from every retail or general-release Windows 11 installation. The reviewed material establishes the removal notice for the three named Release Preview builds, but does not establish feature availability across every retail/general-release installation. Microsoft’s support material also sends mixed messages about whether the experience can still be used.
The immediate practical issue is not merely the disappearance of a setup convenience. Microsoft directs affected users toward Windows Backup, yet Windows Backup is a consumer-oriented, account-and-OneDrive-based restore service rather than a like-for-like local transfer replacement. Understanding that distinction matters for anyone buying a PC, planning a refresh, or supporting relatives and small organizations through a migration.
What Microsoft has actually removed
The explicit removal notice applies to Windows 11 Release Preview builds 26100.9539, 26200.9539, and 26300.9539, for versions 24H2, 25H2, and 26H2 respectively. Microsoft states that PC-to-PC Migration is no longer available and points users to Windows Backup instead.
That wording is definitive for the documented Release Preview builds, but the scope should not be overstated. The reviewed material does not establish the feature’s state across every retail or general-release Windows 11 installation. A user who still sees migration pages should not assume the documentation is wrong; equally, a user following older setup instructions should not assume the feature will appear just because a support page describes it.
The important point is simple: the release documentation is a clear record of removal for its three named builds. It is not, by itself, a complete map of every Windows 11 installation in use.
A short-lived and incomplete-looking rollout
Microsoft first announced the new PC-to-PC Migration experience in the Beta Channel on May 23, 2025. At that point, the rollout initially exposed landing and pairing pages inside Windows Backup. Microsoft also said that transfer support during the new-PC setup process would arrive in a future update.
The later removal notice characterizes the experience as one that transferred files and settings directly during new-PC setup. That suggests the intended destination was the out-of-box experience: pairing an old and new PC, then carrying selected material across as the replacement machine was configured.
What the public removal record does not say is just as significant. Microsoft provides no explanation for withdrawing the feature. It does not attribute the decision to reliability, security, engineering complexity, customer feedback, or adoption. It also does not promise that PC-to-PC Migration will return under a new name, in a revised form, or on a stated timetable.
It would therefore be premature to portray this as a temporary pause, a technical failure, or proof of a broader strategy to force all migrations into the cloud. Those may be tempting narratives, but the documented facts do not support them.
Direct transfer was never a full-PC clone
The lost feature has a potentially misleading name. Historical guidance for the direct-transfer workflow shows that it was designed to move files along with settings and preferences, not to duplicate an entire Windows installation.
Several important categories were excluded:
- Installed applications were not transferred.
- Saved passwords and sign-in credentials were not transferred.
- Files already stored in OneDrive were excluded.
- System and operating-system locations were excluded.
- BitLocker-encrypted drives were excluded unless they were decrypted.
The prior workflow also required the two computers to be on the same network. If a transfer was interrupted, it was designed to attempt to resume, which complicates any simple claim that a cloud-based alternative is automatically more dependable.
These limitations mean PC-to-PC Migration was not a substitute for a tested recovery plan or a managed business deployment process. Users would still have needed to reinstall software, authenticate into services again, and account for protected or unusually stored data. Nevertheless, direct movement of local files and settings during initial setup could have removed a significant amount of friction for ordinary household upgrades.
Why Windows Backup is not an equivalent replacement
Microsoft’s recommended alternative, Windows Backup, can preserve useful information. It can remember supported Windows settings, installed-app entries, Wi-Fi networks and passwords, and selected user folders. On a replacement PC, files are restored through OneDrive after sign-in.
That makes it a reasonable convenience service for a particular kind of user: a consumer who already uses a personal Microsoft account and is comfortable placing selected folders in OneDrive.
It is not the same model as a direct PC-to-PC handoff. The differences are concrete:
- Account dependence: Windows Backup is aimed at consumer devices with personal Microsoft accounts. Work and school accounts are not supported by the consumer app.
- Cloud-backed file restore: Selected folders are synchronized to OneDrive and restored after OneDrive sign-in, rather than copied directly from the old PC over a local network.
- Application limits: Windows Backup can restore entries for supported apps, but non-Microsoft-Store applications may still require manual reinstallation.
- Data planning: Files that are not in the selected backed-up folders need separate attention. So do material on encrypted drives and data held in system locations.
There are benefits to the backup approach for people who already have their data synchronized and want a replacement PC to recover familiar settings and application links. It may be especially helpful when the old computer is unavailable at setup time. But that should not obscure its constraints: a user who relied on an offline local transfer, does not want selected data in OneDrive, or signs in with an organizational account has different needs.
The two experiences also differ in what they ask users to understand. Direct transfer required awareness of network pairing and which local content could move. Windows Backup requires awareness of account type, OneDrive folder synchronization, cloud-restored files, and the distinction between an app entry and the app itself. Neither is a comprehensive system image, and neither eliminates the need to prepare for software reinstallation and account sign-in.
Microsoft’s documentation currently conflicts
The removal itself is clear, but the surrounding support estate is not. Microsoft’s general backup and recovery overview still says that PC-to-PC transfer helps move files, settings, and preferences. Its screen-reader migration guide goes further, saying that the experience is “currently available” for qualifying Microsoft accounts and offering pairing and transfer instructions during new-PC setup.
For users, this is more than an editorial inconsistency. The general backup/recovery overview can lead a reader to expect a migration option as part of Windows’ normal recovery guidance. The screen-reader migration guide is even more consequential because it functions as a practical, step-by-step resource at the exact moment someone needs a migration process to work. A screen-reader user who reaches setup expecting the described options may find that the relevant controls do not exist on their build.
Until Microsoft reconciles the pages or adds clear build, version, or regional qualifications, the safest conclusion is that those instructions cannot be treated as a guarantee of present availability. The Release Preview removal notice controls for builds 26100.9539, 26200.9539, and 26300.9539; the conflicting general backup/recovery overview and screen-reader migration guide create uncertainty outside that documented scope.
This is also why support teams and technically confident family members should avoid saying simply, “Use the transfer feature in setup.” That instruction is now conditional. The relevant Windows installation, account type, data location, and actual setup screens all matter.
What to do before replacing a Windows 11 PC
Anyone preparing a migration should plan around the data and applications that matter, rather than around the assumption that a single Windows wizard will move everything.
First, identify where important files live. Separate files already synchronized with OneDrive from local folders that may need to be selected for Windows Backup or handled through another approved process. Pay particular attention to data outside standard user folders, as well as material on BitLocker-protected drives. The historical transfer guidance specifically identified protected drives as a limitation unless decrypted.
Second, make an application list before retiring the old PC. Windows Backup may remember supported app entries, but non-Microsoft-Store programs can require manual installation. License details, installers, product keys where applicable, and sign-in methods should be available before the old device is wiped, traded in, or becomes inaccessible.
Third, expect to sign in again. The retired direct-transfer process did not move saved passwords or credentials, and a new device should not be treated as ready until essential accounts can be accessed normally.
Fourth, check eligibility for Windows Backup early. It is built around a personal Microsoft account and does not support work or school accounts in its consumer form. A person moving between employer-managed, school-managed, or otherwise organizational devices should not plan on it as a universal migration route.
Finally, if a setup guide refers to PC-to-PC Migration, treat it as a feature to verify rather than a feature to depend upon. The current documentation conflict means the option may be absent even where a guide describes it.
The larger lesson for Windows migrations
PC-to-PC Migration was positioned as a bridge between the familiar local-computer model and a modern Windows setup flow. Its removal from the documented Release Preview builds for 24H2, 25H2, and 26H2 leaves Windows Backup as Microsoft’s named alternative there. Yet the replacement emphasizes account-backed synchronization and restore rather than a direct local handoff.
For consumers already invested in OneDrive and personal Microsoft accounts, that may be an acceptable transition. For users with large local collections, privacy preferences that limit cloud synchronization, protected drives, organizational accounts, or a need to prepare a new machine without relying on an old setup feature appearing at the right moment, it is a narrower answer.
Microsoft may eventually clarify its rollout plans or reconcile its contradictory support pages. At present, it has done neither in the reviewed material. The prudent response is to plan a Windows 11 migration as a deliberate process of preserving files, reinstalling applications, and restoring access—not as a one-click PC clone, and no longer as a direct-transfer feature that can be assumed to exist during setup.