<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Joplin on PeteMahon.net</title><link>https://petemahon.net/tags/joplin/</link><description>Recent content in Joplin on PeteMahon.net</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Wed, 29 Apr 2026 10:00:00 +0400</lastBuildDate><atom:link href="https://petemahon.net/tags/joplin/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating OneNote to Joplin</title><link>https://petemahon.net/posts/migrating-onenote-to-joplin/</link><pubDate>Wed, 29 Apr 2026 10:00:00 +0400</pubDate><guid>https://petemahon.net/posts/migrating-onenote-to-joplin/</guid><description>&lt;h2 id="getting-your-notes-out-of-onenote"&gt;Getting your notes out of OneNote&lt;/h2&gt;
&lt;p&gt;Getting data out of OneNote is the part of this migration where Microsoft makes you work for it. Unlike OneDrive - where the desktop client will happily sync the entire tree to disk on demand - OneNote has no equivalent &amp;ldquo;export everything&amp;rdquo; command. The native export options are notebook-by-notebook, section-by-section, and the formats they offer (&lt;code&gt;.one&lt;/code&gt; proprietary, &lt;code&gt;.docx&lt;/code&gt;, &lt;code&gt;.pdf&lt;/code&gt;, &lt;code&gt;.mht&lt;/code&gt;) are either useless to Joplin or lossy on the way through. The route I took was OneNote desktop on Windows exporting to &lt;code&gt;.one&lt;/code&gt; files, then Joplin&amp;rsquo;s native OneNote import on the other side.&lt;/p&gt;</description></item></channel></rss>