Microsoft is pulling the plug on its Universal Windows Platform (UWP) OneNote app on October 14, 2025. After that date, OneNote for Windows 10 will become read-only, cutting off all editing, creation, and syncing capabilities. The move is part of a larger consolidation effort to unify the fragmented OneNote experience on Windows under a single desktop application.

A Decade of OneNote Confusion

For years, Microsoft maintained multiple OneNote clients: the classic desktop OneNote (historically branded OneNote 2016), the UWP OneNote for Windows 10 preinstalled on many devices, and web/mobile versions. This split bred confusion among consumers, IT administrators, and educators, who often struggled to determine which app offered the features they needed. Microsoft finally settled on a unified path in August 2025, announcing that the desktop OneNote—now simply called “OneNote on Windows”—would be the sole client going forward.

What’s Changing on October 14, 2025

The retirement is absolute: the UWP app will not merely stop receiving updates; it will enter a frozen state. Users will be able to open and view existing notebooks stored on their device, but they won’t be able to create new notes, edit existing ones, or sync changes to OneDrive or SharePoint. Microsoft will cease shipping bug fixes, feature updates, and security patches for the app, making it a security liability over time.

This isn’t a silent deprecation. Microsoft has baked in an in-app migration experience, complete with a banner urging users to “Move to the newest version of OneNote.” The target is the free OneNote on Windows desktop app, available from the Microsoft Store or as part of a Microsoft 365 subscription.

Why Microsoft Is Consolidating

Three reasons stand out. First, consolidation slashes development overhead—no more maintaining parallel codebases for what should be one product. Second, it centralizes feature development, allowing Microsoft to deliver AI-powered tools like Copilot integrations faster and more consistently. Third, the desktop OneNote offers deeper enterprise capabilities, including richer compliance features and integration with Microsoft Purview sensitivity labels—something the UWP app lacked.

Yet consolidation comes at a cost: short-term migration pain for users and IT teams, and the risk of data loss for those who act too late.

How to Identify Your OneNote Version

Before migrating, determine which OneNote you’re running. The simplest test: look for a File menu at the top-left. A standard File menu and a full ribbon indicate the desktop OneNote (the one that will survive). If there’s no File menu and you see a single-line simplified ribbon with vertical section tabs on the left, you’re on the UWP app. The UWP version also often says “OneNote for Windows 10” in the title bar or search results. When in doubt, check the app’s About or Account pane.

Migration Checklist for Everyday Users

If you rely on OneNote, don’t wait. Follow these steps now:

  • Sync everything to the cloud. Right-click each notebook in the UWP app and select “Sync This Notebook.” Ensure synchronization completes. Local-only notebooks are the single biggest data-loss risk—they won’t appear in the new app.
  • Install OneNote on Windows. Download the free app from the Microsoft Store or via Microsoft 365. Sign in with the same Microsoft account you used for syncing.
  • Click the in-app migration banner. The retiring app shows a banner (often labeled “Move to the newest version of OneNote” or “Switch now”). Click it and verify your notebooks appear in the new app.
  • Validate your content. Open each notebook in the desktop app. Check that pages, ink, attachments, and search work correctly. Use File > Open Backups to recover older material if needed.
  • Export critical notebooks. If you have local-only content or must preserve material outside OneDrive/SharePoint, export pages or notebooks as PDFs or OneNote packages, or copy backup files to external storage.
  • Update shortcuts and integrations. Any scripts, add-ins, or Windows shortcuts pointing to the UWP app must be redirected to the desktop OneNote. Adjust your default app settings in Windows accordingly.

Enterprise and Education: Treat This as a Project

For IT administrators, October 14 isn’t just about OneNote—it’s a date when Windows 10 editions and several Office products also reach end of support. That makes coordination critical.

Key actions for organizations:

  • Set a hard deadline. Complete migrations before October 14 to avoid disruption. Pilot first, then roll out.
  • Deploy the desktop OneNote at scale. Use Microsoft Endpoint Manager (Intune), Configuration Manager, or standard software distribution. Confirm which installation channel fits your environment.
  • Manage default app settings. Windows might prompt users to choose a default OneNote. Preconfigure defaults via Settings > Apps > Default apps or deploy them through policy.
  • Mind compliance and data protection. OneNote on Windows supports sensitivity labels and conditional access. Ensure your desktop app version aligns with your organization’s labeling and security policies.
  • Education-specific concerns. Class and Staff Notebooks need special care. Follow Microsoft’s migration documentation to preserve permissions and links used in learning management systems.
  • Communicate clearly. Provide users with a simple checklist: sync, click the banner, verify. Offer support channels for those who encounter issues.
  • Audit after migration. Check for orphaned local notebooks and lingering UWP app instances. Consider restricting the old app through app control policies.

Risks, Pitfalls, and Edge Cases

No migration is risk-free. Here are the top dangers to watch:

  • Local-only notebooks: The most common cause of data loss. If a notebook was created locally in the UWP app and never synced, it won’t magically appear in the new app. Export or manually copy such content before the deadline.
  • Third-party add‑ins and legacy integrations: Some workflows built around the UWP app may break on the desktop version. Inventory integrations and test critical scripts early.
  • User experience friction: The UWP app’s minimalist interface has loyal fans. The desktop OneNote’s ribbon and layout differ; expect some retraining or user pushback.
  • Feature roadmap uncertainty: Microsoft has teased Copilot-powered summarization, richer voice integration, and enhanced media handling—but these are forward-looking statements, not guarantees. Treat them as aspirational until official release dates appear.
  • Voice and AI feature dependency: Microsoft is upgrading backend services for Read Aloud, Transcription, and Dictation; older Office clients will lose these features in January 2026 unless updated. Even if users migrate OneNote, they must keep the rest of their Office apps current to retain voice tools.
  • Unsupported OS risks: Running the desktop OneNote on an outdated Windows 10 build after October 14, 2025 means no OS security patches. That’s a compliance and security hazard—plan to move to Windows 11 or stay on an Extended Security Updates (ESU) program if necessary.

Troubleshooting Common Migration Problems

  • Notebook doesn’t appear in the new OneNote: Verify the notebook fully synced in the UWP app to OneDrive or SharePoint. Sign in with the exact same account. In the new app, go to File > Open > Open from OneDrive and search manually. If you see the notebook files in OneDrive’s web interface, OneNote can open them.
  • Ink or audio recordings missing: Large multimedia files may fail to sync if the process is interrupted. Re-sync from the old app and check OneDrive’s web view for attachments. Use File > Open Backups in the desktop app if local cache exists.
  • Read-only notebooks in the new app: After October 14, the UWP app is naturally read-only, but synchronized notebooks in the desktop app should be editable. If a notebook is marked read-only in OneDrive/SharePoint due to permissions, update the sharing settings.
  • Bulk installs failing: Verify the desktop OneNote package version and update channel compatibility with your deployment tools. Microsoft’s enterprise migration documentation and a pilot ring can catch snags early.

Recommendations by User Profile

Casual and home users:
- Sync all notebooks to OneDrive immediately.
- Install OneNote on Windows and confirm notebooks appear.
- Export any local-only notebooks as an insurance policy.

Power users and heavy ink users:
- Test ink rendering, ink replay, and pen shortcuts; behavior may differ.
- Back up notebooks before importing large media or making mass edits.

Educators and students:
- Coordinate with school IT to ensure Class Notebooks migrate cleanly.
- Share a simple guide with students: sync, click the banner, verify.

IT admins and enterprise teams:
- Build a migration project plan with inventories of users, notebooks, integrations, and compliance needs.
- Standardize OneNote on Windows deployments via group policy or Intune.
- Evaluate sensitivity label support and conditional access compatibility.
- Overcommunicate deadlines and provide pilot/help resources.

The Bigger Microsoft Timeline

October 14, 2025, is a seismic date in Microsoft’s lifecycle calendar. Alongside OneNote’s retirement, multiple Windows 10 editions and Office 2016/2019 lose support. Then, at the end of January 2026, Microsoft flips a switch on voice feature backends, rendering older Office clients incapable of Transcription, Dictation, and Read Aloud. Government cloud tenants get a short grace period into March 2026. These converging deadlines demand coordinated planning—you can’t move OneNote in isolation.

Long-Term Outlook: One Note to Rule Them All

Microsoft’s consolidation signals a desire to infuse OneNote with cloud and AI capabilities at a faster clip. Copilot, richer multimedia handling, and cross-platform parity are on the aspirational horizon. For users, a single client means a cleaner feature set and better support. For admins, less fragmentation simplifies management—after the migration dust settles.

But any promises about AI features or delivery dates are subject to change. Organizations that hang their workflows on those promises should track Microsoft 365 roadmaps and pilot preview builds before broad rollout.

Final Assessment: Strengths, Trade-Offs, and What to Watch

Strengths:
- One supported OneNote client ends confusion.
- Consolidated engineering should accelerate feature delivery.
- Desktop app aligns with enterprise security and compliance.
- A clear, supported migration path exists.

Trade-offs and risks:
- Users who love the UWP simplicity face a learning curve.
- Unsynchronized local notebooks risk permanent data loss.
- Legacy integrations may require rework.
- Timing collides with other critical lifecycle deadlines, raising the coordination bar.

What to watch next:
- Adoption metrics and user sentiment post-migration—will there be backlash over the UI shift?
- The actual arrival of Copilot-powered OneNote features, and whether enterprise customers get parity with consumers.
- Any additional tools or assisted migration services Microsoft might roll out if demand swamps IT teams.

The clock is ticking. Microsoft’s message is unambiguous: sync, switch, and secure your notes before October 14. Failure to act means a frozen app and a scramble to recover content that was never synced. The future is cleaner, but only if you move.