You double-click a .one file, or open a notebook you have not touched in years, and OneNote responds with a variation on “this section was originally created in an older version of OneNote”. Sometimes the phrasing is “this file is from a different version of OneNote”, sometimes it arrives as a sync error about a section being incompatible with a cloud notebook. They are all pointing at the same family of causes.

Nothing in that message says your notes are damaged. Take it as a compatibility notice rather than a loss notice, and work through the causes in order.

Do this first, before anything else. Copy the .one file — and the whole notebook folder if there is one — somewhere separate, and work only on the copy. Several of the fixes below convert the file in place, and a conversion cannot be undone. This one habit turns a risky afternoon into a safe one.

Cause 1 — it is a standalone section, not part of a notebook

This is the most common cause by a wide margin, and it surprises people because the file looks perfectly normal.

OneNote expects a section to live inside a notebook folder, alongside its siblings and a table-of-contents file. A .one sitting on its own on the Desktop or in Downloads — pulled off an old backup drive, emailed by a colleague, salvaged from a dead laptop — is a standalone section, and modern OneNote does not treat standalone sections as a normal way of working. Rather than refusing outright, it shows the older-version message.

Microsoft's documented fix is this sequence, in the OneNote desktop app on Windows:

  1. In File Explorer, right-click the .one file and choose Open with › OneNote. Do not try to open it from inside the app's File menu; the right-click route is the one that works here.
  2. The section appears in OneNote under a heading called Opened Sections — a holding area, not a notebook.
  3. Create a new notebook (File › New) to be its permanent home.
  4. Right-click the section's tab and choose Move or Copy.
  5. Select the new notebook and click Copy. Copy rather than Move leaves your original file untouched.

Repeat for each loose section. If you have dozens, that is tedious, and it is a fair reason to look at other options — but for a handful of files this is free, official, and gives you a proper working notebook at the end, which no text-extraction route can match.

Cause 2 — you are trying it in the wrong OneNote

There is more than one OneNote, and only one of them can do this job.

  • OneNote for Windows (the desktop app) — the only version that works with notebooks stored on a local drive. This is where the repair above has to happen. It is available as a free standalone download and does not require an Office subscription.
  • OneNote on the web — works with notebooks in OneDrive or SharePoint. It cannot take a loose local .one, and it will not offer you a conversion.
  • The app that shipped with Windows 10 — also cloud-oriented, and it reached end of support on 14 October 2025.
  • OneNote for Mac — documented as working with notebooks hosted on OneDrive or SharePoint rather than local ones. See opening a local .one file on a Mac.

If you have been fighting this in a browser, that alone may be the whole problem.

Cause 3 — the file really is in the OneNote 2007 format

Sometimes the message is literal: the section was made by OneNote 2007 and never upgraded.

Modern desktop OneNote can open and view 2007-format notebooks, but editing them needs an upgrade to the newer format. Microsoft exposes that as a Convert to 2010-2016 action, reached through the notebook's properties. If the button is available, the notebook is convertible.

Two things Microsoft is explicit about, and they matter:

  • Upgrading from 2007 does not happen automatically. That is deliberate, so that people still on the old version can keep collaborating.
  • OneNote 2007 cannot read files in the 2010-2016 format. Conversion is a one-way door.

Some features — maths equations and linked notes among them — need the newer format to work at all, which is why the conversion exists rather than everything simply staying backwards-compatible forever.

Cause 4 — it is a OneNote 2003 file, which is the hard case

The modern desktop app does not support the original OneNote 2003 format. Not “opens it awkwardly” — does not support it.

The historical route was a two-step upgrade: open the 2003 file in OneNote 2007 (or 2010), which could read and upgrade it, then convert forward again. That chain worked well in 2012. In 2026 it means sourcing a licensed copy of software Microsoft no longer distributes, which for most people is not a realistic plan.

If you have 2003-era files, be prepared for the answer to be a text-extraction route rather than a full restoration. Getting the words back is achievable; getting the original notebook experience back may not be.

Cause 5 — a sync conflict rather than a version problem

A related message says a section is incompatible with your cloud notebook. That is usually a sync issue, not a format one, and it responds to different treatment: check OneDrive or SharePoint version history for a healthy earlier copy of the section, and look in the OneNote backup folder — by default %LOCALAPPDATA%\Microsoft\OneNote\16.0\Backup on Windows — for a recent local snapshot. Deleted pages and sections also sit in the Notebook Recycle Bin, which Microsoft documents as retaining them for 60 days.

When none of that works

You have run out of official road when all of the following are true: the file will not open in a desktop OneNote, there is no Convert button, there is no cloud copy or backup, and installing an obsolete version of Office is not something you are going to do.

At that point the honest question changes. It stops being “how do I restore this notebook?” and becomes “how do I get the words out?” Those are different problems with different answers.

Two routes remain, and both are run from a command line. Several open-source parsers read .one files directly and emit XML or JSON — we name them in how to open a .one file without OneNote; turning that output into something readable is work you do yourself. OneNote Rescue is built for exactly this leftover case and takes one command: it reads your own section file locally, read-only, and writes page titles and note text out as plain text, a readable HTML notebook and a JSON report of what it found and what it could not.

Honest scope, so you can judge whether it is worth your time. OneNote Rescue recovers page titles and note text. From a OneDrive-format section it also writes the embedded images out as real files next to the notebook — along with any other embedded file whose type it recognises by its file signature — each with its SHA-256 recorded in the report. From a classic desktop revision store, embedded files are noted in the report but not extracted in this pass. Ink and handwriting strokes are noted, not converted to text, and any object it cannot identify is listed as present and not extracted rather than guessed into a file. Rich formatting and the exact page hierarchy are simplified into readable text. Nothing is ever decrypted or bypassed: password-protection markers are flagged in the classic revision store, and are not detected in the OneDrive-format container in this pass. Your original file is copied to a temporary location and only the copy is read, so its bytes and timestamp are unchanged.

Supported operating systems: Windows 10 and 11 (64-bit), and macOS 10.15 or later. One purchase covers both, so you can recover the files where they already are — no copying them to another machine first.

And to be plain about the trade-off: if the free routes above will open your section, they will give you more back than we will. Try them first.