Migrating to Obsidian from Other Tools

Migrating your note-taking system is more than a technical transfer; it's an opportunity to reevaluate and revitalize your personal knowledge management. Obsidian offers a powerful, local-first, and link-centric approach, but a successful migration hinges on careful planning around data export, link preservation, and adapting your organizational habits to a new, graph-based paradigm.

Planning Your Migration Strategy

Before you run any conversion tool, you need a strategy. A haphazard import can leave you with a disorganized vault that obscures Obsidian's strengths. Start by asking a critical question: should you migrate everything or be selective? A blank-slate migration, where you only bring over notes you actively use and value, is often the most effective. It forces you to declutter and prevents you from carrying forward outdated or irrelevant information. Conversely, a full-archive migration might be necessary for compliance, sentiment, or if your entire corpus is actively linked.

Next, understand the core difference between your old system and Obsidian. Most tools use proprietary databases or formats, while Obsidian uses plain Markdown (.md) files stored in a local folder on your computer. Your goal is to convert your exported data into this format. Crucially, you must locate where Obsidian will store these files—this local folder is called your vault. Always create a full backup of your existing notes and export your data from your old tool before beginning any conversion process.

Tool-Specific Conversion Pathways

Each major note-taking platform has its own export format and corresponding community-developed tools to bridge the gap to Obsidian. Using the right converter is essential for preserving as much structure and content as possible.

For Evernote users, you will export your notebooks as an ENEX (Evernote Export) file. Tools like Yarle or Evernote2Obsidian can then process this file. They convert notes to Markdown, extract and handle attachments (like images and PDFs), and can even transform Evernote's note links into a format Obsidian can understand. Pay close attention to how these tools handle Evernote's rich text formatting and checkboxes to ensure they meet your needs.

Notion requires you to use its built-in export function, choosing the "Markdown & CSV" format. This creates a ZIP file containing Markdown files and an accompanying folder for all your attachments. The conversion is relatively clean, but a key challenge is handling internal links. Notion's exported links are often absolute URLs pointing to your online workspace, which will be broken locally. You may need a script or tool like notion2obsidian to batch-convert these links to Obsidian's [[Wiki-link]] format.

If you are coming from Roam Research or similar tools like Logseq, you are already familiar with a graph-based, block-reference model. Export your graph as a JSON file. Obsidian can import this format directly via its "Import from Roam Research" community plugin. This is one of the most faithful migrations, as it preserves the bidirectional linking and block references (converted into Obsidian's ![[embed]] syntax), allowing you to maintain your existing network of thought with minimal disruption.

Handling Attachments and Preserving Links

The integrity of your migrated knowledge base depends on how well you handle embedded files and internal connections. Attachments—images, PDFs, audio files—are often the first casualty in a poor migration. Most converters will place these files in a designated folder (like assets or attachments). You must verify that the resulting Markdown text points to the correct relative path where Obsidian can find them. A broken image link in one note is a problem; hundreds of them render your vault unusable.

Internal link preservation is the cornerstone of a connected notes system. Your old notes likely contain thousands of links pointing to other notes within the same platform. During conversion, these need to be translated into Obsidian's native [[Page Link]] syntax. The efficacy of this process varies by tool. After migration, you must audit a sample of notes. Use Obsidian's built-in unlinked mentions feature and the graph view to identify notes that should be linked but aren't, allowing you to manually repair your knowledge graph. This audit phase is where you truly begin to own your new system.

Restructuring for Obsidian’s Paradigm

Simply importing files into a vault is not the end goal. To leverage Obsidian's full power, you must rethink organization. Unlike folder-heavy systems like Evernote, Obsidian thrives on linking over hierarchy. Instead of deep, rigid folder trees, aim for a flatter structure where connections between notes provide the primary navigation path. Use tags and MOCs (Maps of Content)—notes that serve as thematic indexes linking to other notes—to create flexible, emergent organization.

This is also the time to establish new workflows. Explore core features like Daily Notes for logging, Templates for consistent note creation, and Dataview for dynamically querying your notes. The goal is not to replicate your old system inside Obsidian, but to adapt your practices to a tool designed for networked thought. Start small: migrate a single project or area of your life first, refine your structure and templates, and then scale up the process.

Common Pitfalls

Neglecting a Pre-Migration Backup: Never export and convert your only copy of your notes. Always ensure you have a secure, unaltered backup from your original service before you begin any migration process. This is your safety net.

Failing to Audit Links and Attachments: Assuming the conversion was 100% perfect is a major mistake. Systematically check that internal links resolve to the correct notes and that embedded images and files display properly. A few hours of auditing can save dozens of hours of frustration later.

Attempting to Replicate a Folder-Heavy System: If you force Obsidian to behave exactly like Evernote with exhaustive nested folders, you will miss its greatest strength—the graph. Resist the urge to perfectly categorize everything upfront. Embrace linking and tagging, and let structure evolve from the bottom up.

Migrating Everything Without Curation: Bringing every single note, including the outdated and irrelevant, creates digital clutter that hinders discovery and use. View migration as a curatorial process. Be ruthless in selecting what truly adds value to your future thinking.

Summary

• Plan Strategically: Decide between a selective or full archive migration and always back up your original data before starting any conversion process.
• Use the Right Tools: Leverage dedicated converters like Yarle for Evernote, notion2obsidian for Notion, and Obsidian's built-in Roam import to transform proprietary exports into Obsidian-compatible Markdown.
• Verify Core Integrity: Post-migration, your two critical audits are for functional internal links ([[wiki-links]]) and properly linked attachments (images, PDFs).
• Adapt Your Workflow: Move from a mindset of hierarchical filing to one of linking and connection. Utilize tags, MOCs, and Obsidian's core plugins to build a dynamic knowledge system.
• Curate, Don't Just Transfer: A migration is the perfect opportunity to declutter. Import only the notes that are active and valuable to your current and future work.