On October 14, 2025, Microsoft’s OneNote for Windows 10 will flip into a read-only state. After that date, you can glance at your notebooks but you won’t be able to edit a single word, sync changes, or receive updates. The move marks the final chapter for the Universal Windows Platform (UWP) version of the app, pushing all users toward the unified OneNote on Windows client—a shift that carries real benefits but also introduces genuine risks of data loss for the unprepared.

Microsoft confirmed the end-of-support timeline in a Tech Community blog post, and the company has begun rolling out in-app prompts urging users to switch. The timing isn’t accidental. October 14 is also the day Windows 10 itself reaches end of support, creating a synchronized deadline that forces organizations and individuals to plan dual migrations.

What Microsoft Announced

The official announcement leaves no room for ambiguity. OneNote for Windows 10 will be placed in a permanent read-only mode on October 14, 2025. Viewing notebooks will remain possible, but editing, synchronization, and updates will cease. Microsoft’s support documentation and a detailed migration FAQ spell out the consequences: unsynced local content could vanish, and the legacy app’s per-user sandbox backups may become inaccessible if the app is uninstalled without proper exports.

The company is steering everyone toward OneNote on Windows—the modern Store and Microsoft 365 app. This client is free for personal, education, and enterprise use, and Microsoft claims it’s the only OneNote that will receive ongoing feature development, including AI-powered Copilot Notebooks and enterprise controls like sensitivity labels.

A “Switch now” banner has already appeared inside the legacy app, and Microsoft provides a WinGet package for scripted enterprise deployments. The message is clear: migration isn’t optional.

The Windows 10 Connection: A Strategic Crunch

It’s impossible to separate the OneNote retirement from Microsoft’s broader push to leave Windows 10 behind. The same October 14 date marks the end of technical support, feature updates, and security patches for Windows 10 itself. Microsoft’s official support page recommends upgrading to Windows 11 or enrolling in the paid Extended Security Updates (ESU) program, which buys time until October 12, 2027.

By aligning the OneNote cutoff with the Windows 10 end-of-support, Microsoft creates a powerful incentive for users to adopt Windows 11 and its associated ecosystem. Critics have labeled this an artificial nudge toward AI-enabled PCs and Copilot+ devices. A recent lawsuit, reported by Windows Central, alleges that Microsoft is ending Windows 10 support to sell new hardware. Regardless of the legal arguments, the practical outcome is a hard deadline that pressures both IT departments and everyday note-takers to act.

What This Means for Everyday Users

If you regularly capture meeting notes, journal entries, or project plans in OneNote for Windows 10, the single most important action you can take is to start migrating now. Waiting until mid-October risks losing edit and sync capability overnight—and if you have notebooks stored only locally on your device, those changes could be locked behind a read-only wall forever.

Immediate Steps to Take Now

  1. Verify sync status for every notebook. Open OneNote for Windows 10, right-click each notebook, and choose “Sync This Notebook.” Confirm the status reads “Synced.” Any notebook showing “Saved offline” or a sync error needs attention.
  2. Export unsynced local content. The legacy app sandbox isn’t directly accessible, but you can use the UWP backup protocol (onenote-uwp://backup:) or manually copy the app’s sandbox folder to a safe location. Validate that the exported files open correctly.
  3. Install OneNote on Windows. Click the “Switch now” banner if available, or search the Microsoft Store for “OneNote.” Sign in with the same Microsoft account.
  4. Check for missing notebooks. Most OneDrive- or SharePoint-stored notebooks should appear automatically. If content is missing, use File > Open Backups inside the new app or import the sandbox backups you exported earlier.
  5. Keep the legacy app installed until you’ve verified all data is editable in the new client across your devices. Uninstalling prematurely can purge sandboxed backups permanently.

Step-by-Step Migration Guide for Individuals

A structured checklist minimizes disruption:
- Sync all notebooks: Right-click each notebook → Sync This Notebook. Resolve any sync errors.
- Locate offline sections: In the notebook list, look for a “Saved offline” banner. Move or copy that content into a synced notebook, or export it manually.
- Create a manual backup of the UWP sandbox: Before installing the new app, navigate to the hidden sandbox folder (the path varies; %localappdata%\Packages\Microsoft.Office.OneNote_8wekyb3d8bbwe) and copy it to a backup drive.
- Install OneNote on Windows: From the Microsoft Store. Sign in with your Microsoft account.
- Validate: Open every notebook, verify sync, and test editing. If data is missing, use File > Open Backups and point to your exported files.
- Cross-device check: Log into the same account on a secondary device (web, mobile) and confirm notebooks appear fully synced.

Enterprise and Education: Planning for Orchestrated Rollouts

Large organizations can’t treat this as a one-click per-user migration. The UWP sandbox model introduces specific risks that demand project-level planning.

Key Administrative Considerations

  • Inventory and discovery: Use Intune, SCCM, or Powershell to identify devices with the AppId Office.OneNote. Build a phased rollout plan based on department or risk profile.
  • Forced sync and backup automation: Script a final sync and collect logs (UWPBackUpStatus.json, UWPSyncStatus.json). Any local-only content must be exported to network storage before uninstalling the legacy app.
  • Deployment tooling: Microsoft recommends WinGet for scripted installs of the modern OneNote app. The Store for Business or Microsoft 365 deployment channels are alternatives.
  • Per-user uninstall discipline: Do not run mass uninstalls until backup integrity is confirmed. The legacy app’s sandbox is tied to the user profile; removing the app without exporting can erase data permanently.
  • Now–September 2025: Pilot migrations with a sample user group. Test backup scripts, validate restore procedures, and communicate the plan to stakeholders.
  • September–early October 2025: Staged rollouts with increased support staffing for sync and missing-notebook reports.
  • By October 14, 2025: Critical users must be fully migrated or have archived backups. Leave the legacy app installed for viewing if needed.

The AI Imperative: Why Microsoft Is Pushing You to the Modern Client

Microsoft frames the consolidation as an efficiency play. Maintaining one actively developed client simplifies patching, enables modern compliance features, and—crucially—unlocks AI capabilities that the legacy UWP architecture cannot support. The company has explicitly tied future investment, including Copilot Notebooks, to the modern OneNote client.

Copilot Notebooks, available now in OneNote on Windows, integrate context from your notes, files, and chats to generate summaries, action items, and even audio overviews. The legacy app lacks the required extensibility and enterprise controls for these features. From a security standpoint, the modern client supports sensitivity labels via Microsoft Information Protection, Group Policy, and Intune management—capabilities absent in the UWP version.

For organizations already committed to Microsoft 365, the migration delivers immediate gains: a single update channel, better compliance telemetry, and access to AI tools that are becoming integral to the productivity suite.

Risks, Unresolved Questions, and Caveats

No migration of this scale is risk-free. The following concerns are rooted in Microsoft’s own documentation and community reports:

  • Data loss from unsynced content: Microsoft’s migration guide warns that unsynced local sections will not transfer automatically. Community threads and IT analyses have confirmed that improper uninstallation can delete sandboxed backups irreversibly.
  • Staged degradation before cutoff: Administrators have observed sync infrastructure upgrades in mid-2025 that caused temporary read-only behavior and slower sync in older OneNote clients. These throttling measures increase the urgency to migrate early.
  • Workflow parity gaps: Certain pen and touch workflows, as well as integrations with Immersive Reader or Microsoft Lens, may differ in the modern client. Organizations that rely on these exact workflows must validate parity during pilot deployments.
  • Reputational and legal headwinds: A lawsuit filed in early 2025, covered by Windows Central, claims Microsoft is ending Windows 10 support to force AI PC purchases. While the complaint focuses on the operating system, it fuels skepticism about the OneNote timeline. Treat these legal claims as context, not technical fact.
  • Unconfirmed AI feature dates: Microsoft bills Copilot Notebooks and other AI tools as shipping or rolling out, but specific release dates for every promised capability are not guaranteed. Roadmap language should be interpreted as planned, not committed.

A Balanced Look at the Strengths

The consolidation isn’t solely a hassle—it brings real advantages:
- Reduced fragmentation: One client means one codebase to secure, test, and update. This concentrates engineering resources and accelerates bug fixes.
- Enterprise-grade controls: The modern client supports policy and telemetry settings that regulated industries require.
- Access to AI innovation: Copilot features rely on cloud-first integration points that the legacy app can’t support; by migrating, users gain access to productivity tools that are quickly becoming standard.

For IT leaders, a well-executed migration positions the organization to take advantage of these benefits while mitigating the risks above.

Practical Checklist and Timelines

  • This week: Force a full sync for every notebook and export local backups. Screenshot sync status as proof.
  • Next 2–4 weeks: Install OneNote on Windows on one device and validate all notebooks are editable. Begin a small pilot group if you’re an admin.
  • By end of September 2025: Complete staged deployments, resolve outstanding sync errors, and finalize user communications.
  • Critical date - October 14, 2025: Legacy app enters read-only. Ensure all critical users are migrated and backups are archived.

Final Assessment

The retirement of OneNote for Windows 10 is a calculated product rationalization. Microsoft is concentrating engineering effort, strengthening security, and unlocking AI features that the legacy UWP architecture cannot support. Technically, the change is defensible; operationally, it requires deliberate planning.

The hardest truth is this: if you wait until October 14 to act, you may find your notes frozen in time. The legacy app’s sandbox won’t negotiate. Sync your notebooks today, install the modern client, and verify your data—then you can safely leave the legacy app behind.

For IT leaders, the migration is a project that demands inventory, scripting, and pilot testing. For everyone else, the path is simple: back up, sync, switch, and validate. Treat October 14, 2025 not as a suggestion but as a firm deadline. The tools are free, the guidance is published, and the alternative—lost notes—is a price no one should pay.

Reference links used in this article are listed in the reference_links section.