<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration on PeteMahon.net</title><link>https://petemahon.net/tags/migration/</link><description>Recent content in Migration 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/migration/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><item><title>Moving OneDrive Files to Proton Drive</title><link>https://petemahon.net/posts/moving-onedrive-files-to-proton-drive/</link><pubDate>Tue, 28 Apr 2026 03:30:00 +0400</pubDate><guid>https://petemahon.net/posts/moving-onedrive-files-to-proton-drive/</guid><description>&lt;h2 id="getting-the-onedrive-tree-onto-disk"&gt;Getting the OneDrive tree onto disk&lt;/h2&gt;
&lt;p&gt;Getting every file out of OneDrive and onto local disk is the foundation step; Proton Drive&amp;rsquo;s client needs to see real files, not placeholders to files only in the cloud. The OneDrive client allows you to set your top folders to &lt;em&gt;Always keep on this device&lt;/em&gt;, which will pull all your files down. If you have huge local diskspace, you might select them all at once for downloading.&lt;/p&gt;</description></item><item><title>Migrating Multiple M365 Mailboxes to Proton with One License</title><link>https://petemahon.net/posts/multiple-m365-mailboxes-one-proton-license/</link><pubDate>Mon, 27 Apr 2026 08:00:00 +0400</pubDate><guid>https://petemahon.net/posts/multiple-m365-mailboxes-one-proton-license/</guid><description>&lt;p&gt;&lt;em&gt;If you&amp;rsquo;ve arrived here from a search engine looking specifically for the shared-mailbox question, the short version is: yes, you can migrate two M365 mailboxes onto one Proton license, and you do it by temporarily moving the license between users in M365 rather than buying a second seat anywhere. The longer version assumes you&amp;rsquo;ve already done the basic Proton setup - both custom domains added and verified, MX records pointing at Proton, your primary mailbox already imported via Easy Switch. If any of that isn&amp;rsquo;t true, the &lt;a href="https://petemahon.net/posts/migrating-inbox-from-m365-to-proton/"&gt;previous post&lt;/a&gt; covers the standard single-mailbox flow first.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Migrating Your Inbox from Microsoft 365 to Proton</title><link>https://petemahon.net/posts/migrating-inbox-from-m365-to-proton/</link><pubDate>Sun, 26 Apr 2026 17:00:00 +0400</pubDate><guid>https://petemahon.net/posts/migrating-inbox-from-m365-to-proton/</guid><description>&lt;p&gt;&lt;em&gt;This is where data actually moves. &lt;a href="https://petemahon.net/posts/proton-mail-custom-domain/"&gt;Post 3&lt;/a&gt; got Proton set up on your custom domain and your DNS records trusted; this post is the cutover itself - pulling mail across from M365. If you&amp;rsquo;ve arrived here from a search engine, note that the earlier posts aren&amp;rsquo;t prerequisites if you already have Proton on a custom domain with MX records created but not yet live.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="before-you-start"&gt;Before you start&lt;/h2&gt;
&lt;p&gt;So far, your incoming email should have started appearing in your Proton mailbox, and you should have been able to send emails from Proton as well. Let&amp;rsquo;s just double-check you have everything in place.&lt;/p&gt;</description></item></channel></rss>