How to Export Your Evernote Notes Safely: Avoiding the 5 Most Common Migration Pitfalls

14,147 notes. That is how many Mark Koester had when he decided to leave Evernote. Eight hours later, his Bear export was still churning at about six to twelve notes a minute. He had already spent 30 minutes deleting 3,000 legacy notes he no longer needed. The export did finish eventually, but the pacing tells you something the official help page never will: exporting from Evernote is not a quick step. It is the bottleneck.

Export Is the Bottleneck

If you have already chosen your next note-taking app — Obsidian, Notion, Bear, Joplin, something else — the hard decision is behind you. What comes next looks simple: export from Evernote, import into the new app. But the export step has a habit of failing halfway, dropping attachments, mangling tags, and carrying along notes you thought were gone forever. The official Evernote Help page tells you what is possible: export up to 100 notes at a time or entire notebooks, choose a file size between 300 MB and 2 GB, and do it all from the desktop app. What it doesn't tell you is that many of those settings are exactly where things go wrong. The five pitfalls below are the most common reasons an export goes wrong. None is insurmountable. But they are predictable — and most people only discover them after the export has already failed.

If you haven't decided on a destination yet, the Evernote Migration Guide 2026 covers the full decision tree. This article assumes the decision is made. The only question left is how to get your data out in one piece.

The Export That Stalls Halfway

The most common failure mode is the export that simply stops. Evernote's desktop app lets you export entire notebooks, but the LiveIt guide notes that large notebooks regularly cause the export to fail mid-process. The official file cap of 2 GB sounds generous, but many third-party import tools choke on anything over 1 GB. In practice, a 500 MB to 1 GB ENEX file is a safer target. If your notebook is larger, split it into smaller batches.

The 100-note batch limit is another splitting strategy. Evernote lets you select up to 100 notes and export them as a separate ENEX file. If you have a notebook with 2,000 notes, that means exporting 20 separate files. It is tedious, but it avoids the stall. Mark Koester's experience drives the point home: after cleaning out 3,000 legacy notes, his remaining 11,000-plus notes still required careful batching. He spent hours, not minutes.

I would not trust the 2 GB cap. Never export your entire account in one shot. Always export notebook by notebook or in batches under 500 MB. A stalled export that takes hours to fail is far more frustrating than a planned sequence of small exports that each succeed.

Where Do the Attachments Go?

An export can complete successfully — no errors, no stalls — and still lose data. The ENEX format bundles attachments (images, PDFs, audio files) into the archive, but not all destination apps parse every attachment type correctly. Some ignore embedded files that rely on Evernote-specific encoding. Others drop files that exceed their own size limits.

The only reliable defense is a post-export spot-check. Before you import into your new app, open the ENEX file in a text editor or a dedicated ENEX viewer. Search for file attachments by looking for resource tags. Or, even simpler, use a small test notebook with a known set of attachments. Export that notebook, verify that all files appear in the ENEX, then import it into your destination and confirm nothing is missing. If a single image goes missing in the test, you know the problem will scale.

The Bear FAQ adds another wrinkle: the ENEX format does not include notebook structure. If you have organized notes into multiple notebooks, that hierarchy is lost in the export. Each note's notebook assignment is gone. Plan to reorganize after import.

Internal Links Are Gone. Accept It.

This one is straightforward and disappointing: internal note links in Evernote — those cross-references you carefully built between related notes — do not survive the export. The ENEX format does not preserve them in a portable way. The LiveIt guide states it bluntly: internal note links will break in most alternatives. Some destination apps can rebuild links if the note identifiers match, but that is rare and unreliable.

Assume every internal link will break. Before you export, identify the most critical cross-references — the few links that actually matter for your workflow — and document them manually. A simple list of note titles and the connections between them will save you hours of rebuilding after the migration.

Tags: The Silent Casualty

You might not think of tags as a failure point. They are just labels, right? But in Evernote, you can have tags with spaces, commas, and special characters. When you export those tags into a destination app — Obsidian, Joplin, or any tool that uses plain-text tagging — those characters cause trouble.

Take a tag like “Work Projects.” In Evernote it works fine. In Obsidian, that space splits the tag into two tags: “Work” and “Projects.” Or worse, the space is encoded as a different character and the tag becomes completely unreachable. The result is a tag system that looks right in the import report but fails every time you try to filter by it.

Mark Koester recommends cleaning tags before export: replace spaces with CamelCase (WorkProjects) or underscores (Work_Projects). Also remove commas and other punctuation that might be misinterpreted. This is tedious if you have hundreds of tags, but it is the only way to ensure they survive the migration intact. Set aside an hour for tag cleanup — it is worth it.

Trash and Encrypted Notes: The Hidden Baggage

This pitfall is easy to miss. The ENEX export includes notes you trashed unless you empty the trash first. The Bear FAQ explicitly warns: 'Please consider emptying Evernote’s trash before exporting.' If you have been using Evernote for years, your trash might hold hundreds of deleted notes you never want to see again. Exporting without emptying the trash means those notes appear in the new app as regular entries, cluttering your vault.

The same caution applies to encrypted notes. Evernote allows you to encrypt text within a note. When exported, that encrypted content may appear as unreadable gobbledygook depending on the destination's handling. Some apps will not import encrypted content at all. If you have encrypted notes that must remain readable, decrypt them in Evernote before exporting.

Empty the trash. Decrypt encrypted notes. Do both before you export. These are quick steps with disproportionate consequences if skipped.

The Safe Export Protocol: Batch, Verify, Scale

The five pitfalls above are all preventable. Here is a tested protocol that works regardless of your destination app.

1. Clean tags and empty trash. Replace spaces in tags with underscores or CamelCase. Empty the Evernote trash. Decrypt any encrypted notes you need. This pre-export cleanup takes an hour but eliminates two entire pitfalls.
2. Split notebooks into batches under 500 MB. If a notebook is larger than 500 MB, export it in smaller chunks. Use the 100-note selection to create manageable ENEX files. Do not rely on the 2 GB cap working in practice.
3. Export one small notebook as a test. Pick a notebook with fewer than 50 notes and a few attachments. Export it as ENEX and verify the file size is reasonable (not zero, not huge). Open the ENEX in a text editor to confirm attachments and tags are present.
4. Test import into your destination app. Import the test ENEX file into your chosen app. Spot-check: Are all attachments visible? Do tags appear correctly? Are internal links broken (they will be)? If anything is wrong, adjust your export settings or clean up further before proceeding.
5. Export remaining batches. Once the test passes, export the rest of your notebooks in the same batched manner. Do not attempt to export everything at once.
6. Post-export verification. After all ENEX files are exported, do a final spot-check on a few files. Verify that the total file size makes sense for the number of notes you expect to have exported. If you exported 10,000 notes and the total ENEX size is only 100 MB, something is missing.

After the export is verified, you are ready to import. For destination-specific steps, see the Evernote to Notion guide or the general migration guide for any notes app.

When to Keep Evernote as a Read-Only Archive

Not every note needs to move. If you only have a handful of reference notes that you rarely touch, you can keep Evernote on the free tier. The free plan keeps up to 50 notes accessible as a read-only archive. That is enough for a few favorite recipes, old meeting notes you want to keep for legal reasons, or a personal journal you never export. Downgrading your account is a legitimate strategy that avoids the export process entirely for the notes that matter least.

For everything else, use the safe export protocol. The export is the hardest part, but it is also the only part you control completely. If you prepare for the five pitfalls, the migration becomes a series of small, verifiable steps — not a single anxious wait for a progress bar that might never finish.