Proprietary note-taking applications are digital sharecropping. You spend years tilling the soil—inputting research, drafting ideas, and organizing your life—only to realize you don’t own the land. Your intellectual property is held hostage by subscription models, opaque databases, and the whims of VC-backed startups. To future-proof your ‘second brain,’ you must migrate notes to markdown. This isn’t just a format change; it is an act of data sovereignty.
Markdown is the industry standard for portable, human-readable documentation. It is not a proprietary black box. Because it is essentially plain text with a few decorative symbols, it is readable by any text editor created in the last forty years and likely any created in the next forty. By moving to a local-first markdown system, you eliminate the risk of a service shutdown or a sudden 300% price hike cutting you off from your own history.
The Hidden Fragility of Proprietary Note Apps
Most popular note apps, like Notion or Evernote, store your data in complex databases or specialized JSON structures. These formats enable features like real-time collaboration and embedded widgets, but they are notoriously difficult to export cleanly. When you rely on a cloud-based database, you are merely renting space for your ideas. If the company changes its terms of service or pivots its product roadmap, your notes become a tangled mess of code that is impossible to navigate without their specific interface.
This is vendor lock-in by design. The convenience of a polished UI masks the reality that your files are not actually files—they are entries in someone else’s SQL table. When the servers go down, your productivity halts. When the privacy policy changes, your personal reflections are suddenly subject to new data-mining algorithms.
Markdown files, by contrast, are file-system native. You can open them in Notepad, VS Code, Obsidian, or Logseq. They are easily indexed by your operating system’s native search (Spotlight or Windows Search) and can be backed up using standard tools like Git, rsync, or a simple external drive. Moving to a file-first architecture ensures that your data remains yours, regardless of which software you prefer to use this year or next.
Technical Strategies to Migrate Notes to Markdown
There is no ‘universal export’ button. Every platform has its own quirks, and a clean transition requires a combination of official tools and community-developed scripts.
Evernote to Markdown
If you are escaping Evernote, export your notebooks as .enex files. These are XML wrappers around HTML. Do not use Evernote’s native ‘Export to PDF’ or ‘Export to HTML’ for bulk moves; they lose metadata. Instead, use Yarle (Yet Another Repo Lender). Yarle is the gold standard for this conversion because it handles the ‘Evernote-specific’ quirks, such as converting web clips into readable markdown and preserving tags as YAML frontmatter. It also allows you to define templates so that every note arrives in your local folder with a consistent header structure.
Notion to Markdown
Notion is a database-first tool, making it the hardest to leave. The official markdown export is notoriously messy, often appending long, random alphanumeric strings (UUIDs) to every filename. To fix this, use the Notion-to-Obsidian converter or specialized Python scripts found on GitHub. These scripts strip the UUIDs and attempt to maintain the hierarchical relationship between pages by creating nested folders. Be prepared: Notion’s ‘blocks’ (like callouts or synced blocks) often require manual cleanup because they don’t have a direct 1-1 markdown equivalent.
Apple Notes to Markdown
Apple Notes is a walled garden. On macOS, the best tool is the ‘Exporter’ app (available on the Mac App Store) or the AppleNotesToMarkdown script. These tools use AppleScript to programmatically ‘read’ your notes and write them into .md files. Without these, you are stuck copying and pasting manually, as Apple provides no bulk export feature for non-proprietary formats.
Sanitizing Content and Cleaning Up Metadata
Automated conversion is never 100% perfect. Once the raw files are on your machine, you must sanitize them. This is the time to implement YAML frontmatter. Frontmatter is a block of metadata at the very top of your markdown file, wrapped in triple dashes. It allows your notes to be searchable and filterable by database-like tools without breaking the plain-text nature of the file.
Example of a robust YAML block:
---
title: "Deep Work Analysis"
created: 2023-10-24
updated: 2023-11-01
tags: [productivity, research]
status: permanent
---
Standardizing this metadata is critical. If you use date: in some files and created_at: in others, your future self won’t be able to sort your archive. Use a bulk-renaming tool like PowerRename (Windows) or NameChanger (Mac) to fix filename inconsistencies. For internal content cleanup, learn basic Regular Expressions (Regex). For example, if your export tool left behind messy HTML line breaks like <br>, a simple find-and-replace across your entire folder using /<br\s*\/?>/g will save you hours of manual deletion.
Managing Attachments and Internal Link Structures
One of the most common points of failure in a migration is the handling of images and internal links. Proprietary apps often store images on their own CDN. When you export, you must ensure these assets are downloaded to a local /attachments folder. If your markdown file contains a link like https://s3.amazonaws.com/notion-static/image.png, that link will eventually break. You need to convert these to local paths like ![[image.png]] or .
Internal links are equally fragile. If you had a link in Notion that pointed to another page, the exported markdown link might still point to a web URL. To fix this, adopt Wikilinks syntax ([[Note Name]]). Most modern markdown editors support this. If your export tool didn’t convert these, use a tool like Obsidian’s Importer plugin, which can often scan your files and fix broken internal links by matching them against your new local filenames.
Adopting a File-First Workflow for Longevity
Successfully moving your data is only half the battle; the other half is changing your workflow. In a local-first environment, you are no longer limited by a single app’s feature set. You can use Obsidian for linking and graphing, Zettlr for academic writing, and VS Code for bulk editing—all on the same set of files. This modularity is the ultimate benefit of markdown.
For security, use Git. By initializing a Git repository in your notes folder, you get a granular history of every change you’ve ever made. If you accidentally delete a chapter or mess up a file’s formatting, you can roll back to the exact state it was in three hours ago. This is far superior to the ‘version history’ offered by cloud apps, which is often limited to 30 days and controlled by the provider.