I was a Notion power user for three years. I built dashboards, project trackers, reading lists, and a personal wiki that spanned hundreds of interconnected pages. I loved the database blocks, the linked views, and the feeling that my entire life was organized in one colorful workspace. Then one afternoon I tried to load a critical meeting note while on a spotty train connection, and Notion sat there spinning for forty seconds. The note was text. Plain, simple text. But it was locked inside a web app that needed a strong internet connection, a fast device, and patience. That moment planted a seed of doubt that eventually grew into a complete migration. This is the story of why I left Notion, how I rebuilt my knowledge base with plain Markdown files, and what I gained and lost in the process.
The Notion Years: What Worked Beautifully
I fell in love with Notion for the same reasons many people do. The block editor made it easy to mix text, code, images, and embedded content on the same page. The database feature let me turn any collection of pages into a structured table, a kanban board, or a calendar. I built a task manager that synced with my project tracker, a content calendar for my blog, and a personal CRM that reminded me when I last contacted a friend. Everything was linked. A single wiki page for a programming concept could be referenced from my daily notes, my project docs, and a reading list. The interconnectedness felt like building a second brain.
For a long time, the friction was minimal. I used the desktop app at work and on my laptop, and the mobile app for quick captures. The search was fast, the templates saved me time, and the aesthetic flexibility let me make pages that felt personal and inviting. I convinced several colleagues to try it. I was an evangelist. But the cracks were forming, and I ignored them because the system was so deeply embedded in my daily life.
The Cracks That Became Dealbreakers
The first crack was performance. On a brand new MacBook, Notion was fine. On my older Linux desktop, it was sluggish. On my phone, it was nearly unusable for anything beyond a quick note. The app loaded a full web environment for every interaction, and the latency accumulated over a day of switching between pages. I found myself avoiding the app for small captures because the load time was too high. Instead, I jotted things in random text files or a physical notebook, which defeated the purpose of a centralized system.
The second crack was ownership. My knowledge base was stored in Notion’s proprietary cloud, and while there was an export feature, it produced a mess of Markdown files with broken internal links and orphaned attachments. I felt a low-level anxiety that the service could change its pricing, its features, or its entire existence, and my data would be held hostage. The knowledge I had accumulated over years was not truly mine. It lived in a rented apartment, and the landlord had the keys.
The third crack was complexity. I spent an increasing amount of time curating dashboards, tweaking database views, and organizing pages into hierarchies that made me feel productive but rarely produced real output. The tool had become a hobby. I was managing my knowledge more than I was using it. When I sat down to write an article, I often got lost in the surrounding notes, clicking through linked pages, admiring the structure, and never actually putting words on a page. The system was optimizing for organization, not creation.
The Tipping Point: A Lost Note and a Long Train Ride
The final straw was the meeting note that refused to load. I was on a train with weak cellular service, and I needed to review the decisions from a client call. I had typed the notes in Notion the day before, but the mobile app could not access them without a connection. The notes were plain text, maybe two hundred words. There was no reason they should require a server round trip. I sat there, frustrated, unable to retrieve my own thoughts. I remembered a developer I respected who kept his entire life in a folder of plain text files synced with Git. He never lost a note to a loading spinner. He could open his knowledge base on any device with any text editor. That memory turned into a plan.
That evening, I exported my entire Notion workspace as Markdown and CSV files. The export was a disaster of broken links and empty database dumps. I realized I was not going to migrate smoothly. I would have to rebuild, and that was probably a good thing.
Building the New System: Markdown, a Folder Structure, and Git
I decided on a minimal stack. The core of my knowledge base would be a single folder on my laptop containing Markdown files. No database. No web app. Just files and folders, with a naming convention that made sense to me. I chose VS Code with a Markdown preview extension as my primary editor, which gave me syntax highlighting, link navigation, and a rendered preview. For search, I relied on ripgrep, a command line tool that scans thousands of files in milliseconds. I synced the folder between my devices using a private Git repository, which gave me version history, backups, and the ability to work offline everywhere.
The folder structure was deliberately simple. A daily folder for journal entries and meeting notes, each file named with the date. A projects folder for active work. A reference folder for durable knowledge about programming, tools, and concepts. An ideas folder for half-formed thoughts. A people folder for notes on conversations and contacts. I did not try to replicate Notion’s database features. I accepted that my notes would be a graph of linked text files, not a relational database. That acceptance was liberating. I stopped trying to model my knowledge as structured data and started treating it as a web of prose.
What I Gained: Speed, Ownership, and Focus
The first thing I noticed was speed. Opening a Markdown file in VS Code is instantaneous. Editing is instant. Searching with ripgrep is faster than any cloud search. I no longer waited for anything. The friction of capture dropped to near zero. I started writing more notes because the barrier was so low. The second gain was ownership. Every file in my knowledge base is a plain text document I can open, edit, and back up with any tool. The repository lives on my laptop, my backup drive, and a remote Git server. I am not dependent on any company. If VS Code disappears tomorrow, I will use Vim. If Git vanishes, I will copy the folder. The data is mine in a way it never was with Notion.
The third gain was focus. Markdown is a deliberately limited format. There are no colored backgrounds, no nested columns, no database views. I can still link between notes using wiki-style links, which my editor supports via a plugin. But the links are intentional, created when I write them in the text, not generated by a template. The act of writing a link is an act of connecting ideas, and that manual process makes me think about the connection more deeply. Without the temptation to tweak the layout, I spend more time writing and less time organizing. The system serves creation, not curation.
What I Lost: Databases, Collaboration, and Visual Polish
The migration was not without sacrifices. I lost the ability to create structured databases with filtered views. My old project tracker, which used a Notion database with statuses and deadlines, does not exist anymore. I replaced it with a simple Markdown file in each project folder that lists tasks as checkboxes. That is less powerful but more than sufficient for my solo work. If I needed heavy project management, I would need a dedicated tool. For now, the simplicity is worth the trade.
I also lost the ease of sharing. In Notion, I could share a page with a client or a collaborator with a single link, and they could view or edit it in their browser. My Markdown system is local. I can push the repository to a public or private Git host, but that requires the recipient to be comfortable with text files and possibly Git. For a team environment, a plain text system would need additional tooling. For my solo work, I am the only reader, so sharing is rarely needed.
The visual polish is gone, and I miss it less than I expected. My notes are now monochrome text. There are no icons, no cover images, no color coded tags. The aesthetics were part of the Notion appeal, but I found that they were also a distraction. The blank white page of a Markdown file is a blank canvas for thought. I do not need my thoughts to be pretty. I need them to be accessible.
The Unexpected Joy of Plain Text
About a month after the migration, I noticed a change in my writing. I was writing more, and the writing was messier and more honest. Without the structure of a database template, my daily notes became stream-of-consciousness journals that often surfaced ideas I had not planned to explore. The lack of formatting options meant I could not procrastinate by choosing a header color or rearranging columns. I opened the file, typed my thoughts, and closed it. The process was so fast that it became a habit. I now have a daily writing practice that emerged naturally from the tool’s simplicity.
I also started scripting small utilities that worked directly on my Markdown files. I wrote a tiny script that extracts all the unchecked todo items from my daily notes and compiles them into a single file. Another script searches for all broken links and reports them. These scripts are possible because the data is just text, with a predictable format. I built my own lightweight task manager on top of my notes, without a single database query. The composability of plain text opened doors that a proprietary app kept closed.
What I Would Do Differently
If I could replay the migration, I would make three changes. I would have started with a smaller subset of notes instead of trying to migrate everything. The Notion export was a tangled mess, and I wasted days trying to clean it up. A better approach would have been to archive the Notion workspace and begin the new system fresh, manually porting only the notes I actively needed. That would have saved me a week of frustration.
I would also have chosen a linking convention earlier. I experimented with several wiki link formats, both standard Markdown links and double bracket syntax, before settling on a simple scheme. That inconsistency still lingers in older notes. Standardizing the link style from day one would have made the graph more cohesive. Finally, I would have set up an automated backup from day one instead of relying on manual Git pushes. A simple cron job that commits and pushes every hour gives me peace of mind without extra effort.
Is a Markdown System Right for You?
My move to plain text was not a rejection of Notion. It was a recognition that my needs had changed. Notion is excellent for teams, for structured databases, and for people who value visual organization. My needs are simpler: I want to write, link, and search with minimal friction and maximal ownership. Markdown and a folder of files give me exactly that. The system will never win a design award. It will never impress a client with a shared dashboard. But it opens in a fraction of a second, works offline everywhere, and will outlast every note taking app that exists today.
If you are feeling weighed down by your current tool, consider this: your notes are thoughts, and thoughts do not need rich text. They need to be captured, connected, and retrieved. Plain text does all three with a durability that no web service can match. The migration cost me a few weeks of effort and a few lost features. It returned something far more valuable: the confidence that my knowledge is mine, forever.
