Beyond ENEX: Why Evernote Export Breaks and How Users Fix It

What ENEX Actually Is

ENEX is Evernote's native export format—an XML-based file that contains notes, attachments, and metadata. It's designed primarily for transferring data between Evernote clients or importing into other note-taking applications.

Inside an ENEX File

An ENEX file contains:

• Note content in ENML (Evernote Markup Language—a variant of HTML)
• Attachments encoded as base64 strings
• Metadata: creation date, modification date, tags, notebook
• Note attributes: source, latitude/longitude, author

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE en-export SYSTEM "http://xml.evernote.com/pub/evernote-export.dtd">
<en-export version="x.x">
  <note>
    <title>Meeting Notes</title>
    <created>20230101T120000Z</created>
    <updated>20230101T120500Z</updated>
    <tag>work</tag>
    <content><![CDATA[
      <?xml version="1.0"?>
      <en-note>
        <div>Discussion points...</div>
      </en-note>
    ]]></content>
    <resource>
      <data encoding="base64">iVBORw0KGgo...</data>
      <mime>image/png</mime>
    </resource>
  </note>
</en-export>

The Design Intent

ENEX was designed for Evernote-to-Evernote transfers and app-to-app migration. It preserves data reasonably well for these purposes. But it wasn't designed with human readability or long-term archival as priorities—and that shows when you try to use it for those purposes.

Common Export Problems

When users export from Evernote and import into other tools, several problems appear consistently. These aren't edge cases—they're routine frustrations.

1. Formatting Loss

The most common complaint is that notes don't look the same after export. This includes:

• Text formatting (bold, italics, highlighting) not preserved
• Tables broken or flattened
• Checkboxes converted to plain text
• Indentation and spacing lost
• Code blocks mangled

2. Broken Note Links

Evernote allows linking notes to other notes. These internal links are a key part of how many users organize information. Unfortunately, they often break during export:

• Links may not convert to the destination app's format
• Note titles in other apps may not match Evernote titles
• Some tools create file-based links that don't work across platforms

3. Missing Content

In some cases, content simply doesn't make it through:

• Images in web clippings may fail to load
• Embedded content from external services may not transfer
• Large attachments might cause export failures
• Some metadata is lost in translation

4. Attachment Issues

Attachments encoded as base64 strings should theoretically transfer intact, but users report problems:

• PDFs may not embed correctly in Markdown exports
• File size limits can truncate attachments
• Linked images may break if the source isn't included

Why Exports Break

Understanding why exports fail helps you choose the right approach. The problems aren't random—they're structural.

Format Incompatibility

Evernote uses ENML (Evernote Markup Language), a proprietary variant of HTML. Other tools use different formats:

• Obsidian: Markdown with YAML front matter
• Notion: Block-based database structure
• Joplin: Markdown but with specific conventions
• OneNote: Proprietary XML format

Converting from ENML to any of these requires interpretation and approximation. Some Evernote features don't have direct equivalents, so the conversion process makes choices about what to preserve and what to drop.

Complex Content Structures

Evernote notes can contain complex structures:

• Nested lists with mixed formatting
• Tables with merged cells
• Images with captions and positioning
• Web clippings with arbitrary HTML

These structures don't map cleanly to Markdown or other formats. The conversion process has to simplify, and that's where formatting is lost.

Tool Limitations

Different import tools handle Evernote data differently. Some prioritize completeness over readability. Others favor clean Markdown over exact formatting. The tool you choose significantly affects the quality of your export.

The Standard Tools and Their Limitations

Most users start with the well-known export tools. Here's what they're good at and where they fall short.

Obsidian Importer Plugin

YARLE (Yet Another Really Long ENEX Exporter)

These tools work for many users, but the consistent reports of formatting loss and broken links led some users to seek alternatives.

Community-Built Solutions

Frustrated with existing tools, some users built their own solutions. These address specific pain points that the standard tools missed.

evernote2obsidian

One user, after 15 years with Evernote, found both the Obsidian Importer and YARLE "frustrating" due to formatting loss and broken note links. They built evernote2obsidian as a Python script specifically to address these issues:

• Better preservation of note links
• Improved formatting retention
• More predictable output structure
• Open source on GitHub for community improvement

CloudHQ and Other Commercial Options

CloudHQ offers file migration services that can move Evernote content to Google Drive and other destinations. One user successfully used CloudHQ for their migration, leveraging:

• Automated sync rather than manual export
• Integration with cloud storage services
• Support for scheduled ongoing migrations

These solutions typically cost money but may offer better support and more reliable handling of edge cases.

The Pattern

The emergence of community solutions reveals a consistent theme: standard tools work for basic cases, but users with extensive, complex Evernote libraries often find them inadequate. When the standard options don't meet your needs, someone in the community has likely built something that does.

Choosing the Right Tool for Your Needs

No single tool is best for everyone. The right choice depends on your specific situation.

Consider Your Content

What kinds of notes do you have?

• Mostly text with simple formatting? Standard tools work fine
• Many web clippings? Test how HTML is preserved
• Lots of linked notes? Verify link conversion works
• Heavy attachment use? Check file handling

Consider Your Destination

Where are you exporting to?

• Obsidian: Obsidian Importer or evernote2obsidian
• Joplin: Built-in ENEX import with specific conventions
• Notion: May need intermediate step or specialized tool
• HTML for archival: Consider direct HTML export tools

Test Before Committing

The most important step is testing before you commit to a full migration:

1. Select 10-20 representative notes
2. Include various formatting types, attachments, and linked notes
3. Export using your chosen tool
4. Import into your destination
5. Compare with original to identify issues

Keep Original Exports

Whatever tool you use, keep your original ENEX files. They're your safety net if the migration doesn't go as planned or if you need to try a different destination later.

Summary and Final Thoughts

ENEX exports are the starting point for leaving Evernote, but they're rarely the finish line. Formatting loss, broken note links, and content issues are common enough that many users find themselves searching for better tools or building their own solutions.

Key Takeaways

• ENEX is Evernote's XML-based export format, designed for data transfer
• Standard tools (Obsidian Importer, YARLE) have known formatting and link issues
• Format incompatibility between ENML and Markdown causes data loss
• Community tools like evernote2obsidian address specific pain points
• Testing with a representative sample is essential before full migration
• Keep original ENEX files as a backup regardless of which tool you use

The Bottom Line

The export tool you choose matters. The difference between a successful migration and a frustrating one often comes down to finding the right tool for your specific content and destination. Don't assume the most popular option will work for you—test with your actual notes and see what happens.

And remember: your goal isn't to perfectly replicate Evernote in another system. It's to preserve your notes in a way that lets you continue working with them. Some formatting loss is acceptable if the content remains accessible and useful.