How to Move 1,000+ Evernote Notes Without Losing Your Mind (or Your Notes)

Migrating 50 notes is an errand. Migrating 2,000 is a project — and the standard advice quietly stops working somewhere around note 500.

I moved 1,640 notes out of a 7-year-old Evernote account. Here’s the playbook for large accounts specifically: where things break at scale, and how to keep the project to one afternoon.

Why scale changes everything

Three things that don’t matter at 50 notes and dominate at 2,000:

Export limits multiply. With ENEX’s 100-note selection ceiling, 2,000 notes = 20 separate exports, each with its own silent-failure risk. The fix: use HTML export (no practical limit, one folder per note) and export notebook-by-notebook.

Error rates stop being theoretical. A 1% failure rate on 50 notes is “probably fine.” On 2,000 notes it’s 20 missing notes you won’t notice until you need one. At scale, verification is not optional: record your note count first, compare after every stage.

Time per note compounds. Anything manual — converting, uploading, renaming — multiply it by your note count. One minute per note × 2,000 = 33 hours. If a step can’t be automated, it can’t be in your pipeline.

The pipeline that works

Stage 1 — Inventory. Write down the total note count and per-notebook counts from Evernote’s sidebar. Five minutes now saves hours of doubt later.

Stage 2 — Export as HTML, notebook by notebook. Skip ENEX entirely for accounts this size (I’ve written about why ENEX fails at scale separately). You’ll get one folder per note with attachments included.

Stage 3 — Verify the export. Count exported note folders per notebook against your inventory. Deal with gaps now, while Evernote still has your data.

Stage 4 — Convert and upload. For a destination you’ll actually live in, that means Google Docs in a folder tree mirroring your notebooks. This is the stage where “manual” dies — nobody converts 2,000 files by hand. Whatever tool you use, at this scale it must handle:

• Resume after interruption — a 2,000-note upload will get interrupted at least once. Restarting from zero is how projects get abandoned.
• Bounded memory — bulk parsing can balloon RAM if attachments accumulate in memory (a user of my tool once hit 112GB before I fixed exactly this).
• Attachment-only notes — big accounts have hundreds of notes that are just a photo or PDF. They should upload as files, not become blank documents.
• Storage-quota handling — 2,000 notes with attachments can exceed a free 15GB Drive. Multi-account switching or graceful stop, not a crash at note 1,847.

Stage 5 — Spot-check. Open 10–20 random notes at the destination: one with a table, one with a checklist, one with audio, your oldest note, your newest.

My numbers, for calibration

1,640 notes, ~2GB of attachments: HTML export ~15 minutes, automated conversion+upload ~25 minutes, verification ~10 minutes. Under an hour total. The same account, done manually, would have been a 30-hour slog — which in practice means “never finished.”

The automation I used is my own macOS app, built for exactly this job: Evernote Migration Tool — free for the first 20 notes, one-time $19.99 for unlimited, resume and multi-account included.

Large migrations don’t fail because the data is hard. They fail because unverified, unresumable, manual processes collapse under multiplication. Fix those three, and 2,000 notes is an afternoon.