For the latest instructions see the official Evernote import guide
Within a month I experienced several ways to convert a single Evernote notebook (2k notes) to MD files.
- Import into Joplin (as markdown), export as markdown.
- Import into Notion, export as markdown.
- evernote2md - GitHub - wormi4ok/evernote2md: Convert Evernote .enex files to Markdown
- yarle - GitHub - akosbalasko/yarle: Yarle - The ultimate converter of Evernote notes to Markdown
Almost any tool loses something when exporting to MD files: timestamps, tags, highlighted text, code blocks, tables, etc. Evernote links (evernote:///view/ā¦) between notes are never automagically converted to links between md files with relative paths . You may have to choose the least worst.
Because tags were a must for me, before exporting to enex, Iāve directly accessed Evernote database file (sqlite) and updated the title field adding tags between . Somehow it didnāt work as clean as I expected (notes werenāt detected as modified) so I was compelled to make a little change to each one within the Evernote app. I chose adding a single space (which automatically gets trimmed on save) at the end of the title. This marked the note as changed so it got synced with the updated title afterwards.
The following comparison is made from the results Iāve got with each method.
Joplin
Joplin as an editor is very limited: resources management is a mess, md files are mixed with plaintext files used as diffs, syncing gets corrupted.
Even though, this is my preferred in-transit app to get md files.
Pros exporting MD:
- Excellent markdown quality even for tables!
- Resources are stored into a single folder: _resources.
Cons exporting MD:
- Exported MD filename has a max of 50 characters
- Timestamps, tags, highlighted text and code blocks are not exported
- Resource filenames are hashed (you cannot guess the content from the name)
- Some resource filenames have ābinā extension or no extension at all. The link name inside the md file has the right one.
After exporting md files, Iāve post-processed each one using a perl script to fulfill my needs:
- Create a line for tags obtained from the first line of the file (the title of the note)
- Rename it with full length title, previously cleaned with rules like the ones that evernote2md uses
- Prepend the title with a # to format it as a level 1 Heading
Iām working now on 2 additional scripts
- convert Evernote links to links between md files with relative paths
- rename resources using the link name from the md file.
Notion
This is a great replacement for Evernote. You import directly from an Evernote account and you just keep writing. But somehow is huge for someone who just needs an editor for constructing a knowledge base from simple formatted notes. And your data belongs to the cloud. One of the biggest drawbacks is that Notion handles tags in a poor way: you must keep a Database page with the note-tag association.
Pros exporting MD:
- Excellent markdown quality
- Timestamps and code blocks are exported
- Internal links between notes defined inside Notion are converted to links between md files with relative paths
Cons exporting MD:
- Exported MD filename (as well as its resource folder) has a max of 50 characters and a hash identifier is added after that
- Tags and highlighted text are not exported
- Tables are converted to Inline-Databases in Notion and they are not exported to MD - you just get a link to a Notion url
- A Full-page Database is only exportable as CSV, not Markdown
- Resources are stored in an independent folder for each md file
evernote2md
This is a quite straightforward command line tool.
Pros exporting MD:
- Exported MD filename has a max of 200 characters (+ good cleaning rules)
- Resources are divided into 2 folders: image and file.
- Resource filenames are readable - the same name it has when added to the note
- Tags are added in a single line - each one as an inline code
Cons exporting MD:
- Some erratic failures in the order and detection of file resources (not images)
- Nested lists not fully supported
- Task lists broken
yarle
This is the last one I found and although it claims a lot, itās not ready now.
Pros exporting MD:
- User-defined templates for metadata
- Timestamps, tags, highlighted text are exported
Cons exporting MD:
- It was hard to get it running the first time - the template was relative to the installation path not where I was executing it
- Exported MD filename is converted to lowercase
- Exported content has a lot of unnecessary escape characters (\)
- Resources are stored into subfolders (one for each note) inside a single folder: _resources.
- Some resources filenames have āoctet-streamā extension or no extension at all. The link name inside the md file is also modified, so you may lose some extensions.