Migration
Evernote to Obsidian: A Practical Migration Guide
Step-by-step guide to migrating from Evernote to Obsidian using Markdown export.
Read guide
Markdown migration
Export Evernote to Markdown
Markdown is useful when your Evernote notes need to become editable local files. The migration succeeds only if attachments, tags, and formatting survive well enough for your real notebooks.
Search intent: Users preparing to move Evernote notes into Obsidian, a static folder archive, or another Markdown-based system.
Back up before converting
Create an ENEX archive first, then generate Markdown as the working migration format. That gives you a fallback if conversion loses formatting or resources.
Keep attachments near the notes
Markdown files should reference local images and documents with predictable relative paths. Inspect notes with many attachments before importing them elsewhere.
Review tags and filenames
Special characters, duplicate note titles, and nested tag structures can create messy filenames or frontmatter. Clean those problems before relying on the new vault.
Related guides
Comparison
ENEX vs HTML vs Markdown: Which Export Format?
A detailed comparison of Evernote export formats to help you choose the right one.
Read guide
Technical
The Hidden Problem with Evernote to Obsidian Tag Migration
Special characters, large tag systems, and what breaks during export.
Read guide
Questions people ask
Is Markdown the best Evernote backup format?
Markdown is best for editing and migration. For backup alone, keep ENEX too because it preserves Evernote-specific metadata more faithfully.
Can Markdown exports include attachments?
Yes, but the exported Markdown should link to local attachment files. Always test image-heavy and PDF-heavy notes.