To move from Evernote, export a backup, choose a destination with a documented import path, and test representative notes before moving everything. A successful note count does not prove that attachments, tags, links, reminders, or formatting survived. Keeping Evernote is reasonable when those features already work well and migration adds more cost than value.

To move from Evernote, export a backup, choose a destination with a documented import path, and test representative notes before moving everything. A successful note count does not prove that attachments, tags, links, reminders, or formatting survived. Keeping Evernote is reasonable when those features already work well and migration adds more cost than value.
Published by AFFiNE. Migration documentation checked October 18, 2026. This guide provides a procedure and fictional test materials; it does not report completed end-to-end migrations or security testing.
For product selection, use the Evernote alternatives comparison. This companion focuses on the decision to move and how to check what you retain.
| Situation | Practical next step |
|---|---|
| Your current plan, capture, and search meet your needs | Keep using Evernote and maintain a separate export. |
| You only need a small active project elsewhere | Move that subset first; retain the archive as a reference. |
| You want an editable local Markdown collection | Evaluate Obsidian or Joplin with a representative ENEX sample. |
| You want documents and a planning canvas together | Trial a small manually transferred project in AFFiNE. |
| You need shared database pages | Check Notion's documented Evernote importer and plan limits. |
| You need a different security model | Review hosting, access, recovery, and AI processing requirements with the destination's documentation. |
Evernote's current plan table is the starting point for a cost comparison. Avoid assuming every paid tier is unlimited. Include the time spent correcting imported notes and the cost of sync, storage, and backup in your decision.
This is a documentation matrix, not a pass/fail test result. The blank results sheet is where your own observations belong.
| Destination | Documented route | What needs particular attention |
|---|---|---|
| Joplin | ENEX import | Notes, tags, resources, and metadata are supported. Evernote OCR data is not retained; Joplin can recreate OCR data when enabled. Markdown conversion can change fonts and colors. Internal-link reconstruction can fail when titles are ambiguous. |
| Obsidian | Official Importer plugin with ENEX | Output is Markdown. Tag hierarchy needs preparation; notebook stacks need a naming convention. Inspect attachment links and generated notes. |
| Bear | ENEX import | Map notebook organization to tags; do not assume notebook names survive inside ENEX. |
| Notion | Connected Evernote importer | Notes become database items. Evernote Teams is excluded. Images and dates may need cleanup; test small batches. |
| AFFiNE | Small manual transfer or a supported file-import workflow | Direct ENEX import is not verified by this guide. Rebuild and check tags, links, dates, attachments, and organization rather than claiming lossless migration. |
Permissions, historical versions, alarms, and application-specific behavior require separate checks. Even where content imports, a checkbox may be text rather than a scheduled task, and a visible attachment may not be searchable.
The Evernote migration kit (ZIP) contains three fictional notes, a text attachment, a manually authored ENEX fixture, Markdown reference files, and a checklist. You can also download the ENEX fixture and README separately.
The fixture is syntactically checked XML with an embedded attachment. It was not exported from Evernote and has not been imported into the listed applications during this review. It does not test screenshots, handwriting OCR, complex tables, or every ENEX variant. Its example Evernote link is deliberately a nonworking placeholder: recreate a real inter-note link in your own sample when testing link preservation.
Use fictional content first to learn the destination's import controls. Then select a small set of your own notes with the formats that matter to you. Remove sensitive content before sharing diagnostic files with anyone.
Record notebook names, note counts, essential tags, and the devices where you need access. Include a long note, an attached document, an image or scan, a note with a table, and linked notes in your sample. If you use reminders, make them a separate test case.
Use Evernote's desktop export instructions. Save ENEX for a compatible importer and HTML with its resource files for comparison. The documented route is available on Mac and Windows, not the web app. Free accounts can export; you do not need to upgrade solely for this export feature.
Export by notebook when notebook boundaries matter. Keep the original files unchanged and give working copies descriptive names. Do not delete source notes to make the first import easier.
Follow the destination's current official instructions from the matrix. Record the app version, operating system, plan, importer, date, and chosen settings. If an importer reports an error or omits content, record that result instead of repeating a full import into your main collection.
For AFFiNE, a simple initial trial is to copy the kit's project brief into a Doc and organize its decision points on an Edgeless canvas. This tests whether the new workflow is useful; it is not an ENEX compatibility test. Local editing, Cloud limits, and AI data processing are separate decisions.
Open each attachment, inspect the list and table structure, find a note by a known phrase, and check tags and dates. Follow internal links to the intended destination note. If a link still opens Evernote, that dependency remains even if the text looks correct.
Test offline access on the device and app you will actually use. Reconnect and inspect any edits. If sharing matters, test with the intended account type and access level. These are checks to perform, not claims that all apps offer identical capabilities.
Export the sample from the new app into an available format, then open it independently. Record which content and structure remain readable. This second export helps you understand the next migration before committing to the first one.
Resolve failed checks before expanding the batch. Keep the source archive and reference export until your essential workflows work. Decide explicitly what will stay in Evernote, what will move, and what needs manual reconstruction. An unresolved requirement may be a reason to stay.
Where are notes stored? Who can access shared content? How is recovery handled? What happens when a device is lost? Does an AI feature send note content to an external provider? Use official security and privacy documentation to answer those questions for the exact plan and deployment.
This article does not provide evidence that Evernote is currently compromised or that an alternative is automatically safer. Local storage, encryption, backup, access control, and self-hosting are distinct properties. For AFFiNE, public source code and local editing do not establish end-to-end encrypted Cloud sync.
Yes. Evernote's desktop export documentation includes Free accounts. Use its supported Mac or Windows app and keep the accompanying resource files for an HTML export.
No. ENEX is useful for transferring note content, but the destination must interpret it. Notebook stacks, tag hierarchy, links, OCR data, and app-specific functions can need reconstruction. Verify the items you actually use.
This guide has not verified a native ENEX import path. Try a small manual transfer or a supported format and check the result. Do not move a full archive on the assumption that ENEX is supported.
Plan limits, cost, local-file preferences, and different collaboration needs are reasons a person might evaluate alternatives. This review does not contain a representative survey of departures, so it cannot establish how common those reasons are.