Obsidian works best when the imported vault is plain Markdown plus local attachments. The migration should be tested as a vault, not just as a file conversion.
Who this guide is for: Evernote users who want an Obsidian vault made from Markdown files and local attachments.
Before building the vault, export ENEX and keep it untouched. That protects you if the Markdown conversion misses data.
Open the Markdown output in a temporary Obsidian vault. Check links, images, PDFs, and tags before moving the vault into daily use.
Duplicate titles, special characters, large resources, and complex tables often need manual cleanup after conversion.
Moving years of notes from Evernote to Obsidian isn't just an export and import. Here's how to migrate properly using Markdown export, avoiding the common pitfalls that leave people with broken links and missing attachments.
You export your Evernote notes, import them into Obsidian, and everything looks fine—until you notice your tags are broken or missing. Here's what's happening and how to fix it.
When you have years of notes accumulated in Evernote, the prospect of migrating them somewhere else feels overwhelming. Here's what the migration actually involves, beyond just clicking "export."
Start with a test vault and a representative notebook. Large migrations are easier to fix before the vault becomes your daily workspace.
Markdown with local attachments is the natural fit, but keep ENEX as a separate recovery backup.