How to Back Up Evernote Before Changing Apps or Plans

Why backup comes first

The risky version of migration is making account, billing, or app changes first and then exporting later. The safer version is the opposite: create a local archive while everything still works, open the exported files yourself, and only then decide what to do next.

• Sync is not the same as backup: synced notes still depend on the working app account.
• Readable files matter: you should be able to open some of your archive without importing it back into anything.
• Verification matters more than file count: a folder full of exports does not prove the files are usable.

Which export formats to keep

Different formats solve different problems. The safest approach is usually to keep more than one.

• ENEX: best for preservation and future re-import workflows.
• HTML: best for a readable offline archive with browser access.
• Markdown: best when you want to test another local notes app later.

If you are not sure, start with ENEX plus HTML. Add Markdown if you are testing a workflow such as Obsidian migration or a Joplin migration path.

What to verify before changing anything

Open real notes from the exported archive, especially the messy ones that tend to break first.

• Image-heavy notes
• PDF-heavy notes
• Scanned receipts or research notebooks
• Notes with internal links
• Older notebooks you rarely open

If internal note links matter to you, read Do Evernote Note Links Survive Export?. If attachments are the main risk, check the attachment export guide.

A practical safer workflow

1. Run a full sync into a local database.
2. Export ENEX for preservation.
3. Export HTML for readable spot checks.
4. Optionally export Markdown if you plan to test another notes app.
5. Open several exported notes and attachments yourself.
6. Copy the archive to external storage or your preferred backup destination.