# Importing evernote .enex

**URL:** <https://discourse.joplinapp.org/t/importing-evernote-enex/12644>\
**Category:** Support\
**Created:** [23 November 2020 09:17 UTC](https://discourse.joplinapp.org/t/importing-evernote-enex/12644 "2020-11-23T09:17:36Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![jb261](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/jb261/32/7324_2.png) [@jb261](https://discourse.joplinapp.org/u/jb261)\
**Post date:** [24 January 2021 19:00 UTC](https://discourse.joplinapp.org/t/importing-evernote-enex/12644/21 "2021-01-24T19:00:48Z")

</div>

> [@o5t6iaqo7](#):
>
> Will inter-note links be preserved?

No. This is a limitation of Evernote's ENEX format. You can read more about that here:

> [@Internal links questions](https://discourse.joplinapp.org/t/internal-links-questions/14213/4):
>
> That limitation of enex files doesn't just apply when importing enex into another note app, it applies to importing to Evernote itself. Yes, that means for Evernote users, their enex backups are not lossless - in the event an Evernote user needed to restore those backups to Evernote, that user would lose all their note links. With all their resources, they couldn't figure out how to create a lossless backup. I guess they were too busy trying to settle on the perfect shade of green and shape of …

and here:

> [@Evernote ENEX import suggestion (or plugin) re: note links](https://discourse.joplinapp.org/t/evernote-enex-import-suggestion-or-plugin-re-note-links/13968):
>
> As many of you are aware, Evernote's ENEX export format does not include note GUID's (unique note identifiers), so the note links in a referring note, e.g., evernote:///view/623444547/s234/3234284a05c-d67a-47af-c354-adad387102b3/3234284a05c-d67a-47af-c354-adad387102b3/ are pointing to a GUID that does not exist in the enex file or in any notes imported from an enex file. So perfect recreation of note links via enex is impossible. However, in practice, most note links have note text that is exa…

---

<div class="post-metadata">

**Author:** ![o5t6iaqo7](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/o5t6iaqo7/32/6842_2.png) [@o5t6iaqo7](https://discourse.joplinapp.org/u/o5t6iaqo7)\
**Post date:** [24 January 2021 21:05 UTC](https://discourse.joplinapp.org/t/importing-evernote-enex/12644/22 "2021-01-24T21:05:43Z")

</div>

Thank you, very helpful on Q2!

For questions Q1 & Q4 - what have users found is best for my use case, 8.1k notes, 159 notebooks, 12 stacks? (I would consider this a moderate number of notes but not overwhelming, but, a fairly elaborate folder hierarchy)

[A]. unique tag each stack, each notebook, then, export all 8100 notes to a single ENEX and import, search each tag, move to newly created folder hierarchy;

or

[B]. 159 discrete ENEX exports, and 159 discrete imports (one export/import per notebook), moving each import to a newly created folder in hierarchy?

And for Q3, Q5 any thoughts?

---

<div class="post-metadata">

**Author:** ![roman\_r\_m](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/roman_r_m/32/3297_2.png) [@roman\_r\_m](https://discourse.joplinapp.org/u/roman_r_m)\
**Post date:** [24 January 2021 21:15 UTC](https://discourse.joplinapp.org/t/importing-evernote-enex/12644/23 "2021-01-24T21:15:21Z")

</div>

> [@o5t6iaqo7](#):
>
> are there any apps that accept JEX and preserve Joplin's native hierarchy and inter-note links, or plug-ins that convert Joplin JEX to another app's system preserving the hierarchy and inter-note links

JEX is essentially a tar (or tar.gz?) containing all notes, attachments and metadata, so while there probably aren't any converters from Joplin to any other app, it would not be too hard to implement.

[Previous page](https://discourse.joplinapp.org/t/importing-evernote-enex/12644.md?page=1)