#6

Yarle worked great for me on macOS… Just cloned the repo, ran a few commands to set it up (as shown in the readme), and it was able to process 99% of my Evernote files without issue. There are just a handful that an error printed for that I’ll need to manually check.

1 Like
#7

Hi @Vadych!

I’m sorry, I missed this thread.
Could you please share a bit more info about the failure?
You can reach me on PM.
Cheers,
akos

2 Likes
#8

Everything worked out. I had to install Node.js for this instruction.
You must install version 10.18.1
After npm i there were error messages. The in needs to be fixed by running npm audit fix
Then follow the instructions. It worked perfectly

1 Like
#9

Or in any case npm audit fix --force, but be careful! And then npm rebuild.

#10

For those who arrive here after the release 2.9.0 of Yarle, it now supports any Node version > 10, and some Evernote notes which would fail to convert are now OK.

#11

I was last hacking on the python scripts in https://github.com/exomut/evernote-dump trying to fix places it was breaking for my notes.

Curious to try yarle. Anyone know if it works for some types of webclipper notes? A lot of my notes are of the form (Clip to Evernote > Bookmark)

Notes of Web Clips are not supported (yet)."

#12

Important!
Don’t upgrade to Evernote 10. We have introduced restrictions on the selection of a maximum of 50 notes.
And it works very poorly

4 Likes
#13

Evernote 10 is a complete disaster.

3 Likes
#14

The good news is, Evernote having turned into an absolute unusable disaster should be a benefit to Obsidian. I waited and suffered with version 7.x for years before they dropped v10…and that was the straw that broke the camel’s back and pushed me to seek refuge in Obsidian.

I just wish there was a really great way to import my EN notes. I’ve tried YARLE but it still mangles a lot of stuff and cleaning up notes is so tedious.

3 Likes
#15

You just described me. Version 10 of Evernote came out, broke my file links, and that was that for me.

#16

Keep in mind that yarle may fail to convert some notes. It converted 99% for me, but I doubt you want to discover later that a note that you really need is missing. For some reason it was not obvious for me during the conversion that it was not 100% successful. So be vigilant.
Otherwise yarle is a good tool to get the job done and move away from Evernote, which no longer works for me after many years of paid subscription.

#17

Hi @Scientist !

Could you please provide me some insights about which kind of notes were failed to be converted?
I’m glad to improve the code to let you reach 100% .

#18

Apologies if I am way off base here, but what worked for me was using Evernote Legacy to Joplin and then to Obsidian. I had the extra step of having to import OneNote into Evernote, but maybe Evernote Legacy could help?

#19

I’m trying to debug it, but so far I was not able to find enough time to finish the process. My gut feeling is that it’s related to the case (in)sensitivity on macOS. By default macOS uses a non-case sensitive filesystem. I see that yarle resolves duplicates and assign them unique file names, but I guess the conversion code uses a case sensitive matching, which inadvertently leads to a file overwrite (i.e. same output for two notes that different only in the letter case). I came to this hypothesis based on what notes are missing.
Take it with a grain of salt though - it’s just a hypothesis. I didn’t have time to understand it in details.

1 Like
#20

Could anyone give me a help?

(node:83256) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line options | Node.js v15.10.0 Documentation). (rejection id: 2)
(node:83256) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

#21

Hi! Could you please provide me a bit more info about how you do use yarle, config etc? And please do it in github, I used to check it on a daily basis, so I’ll respond there faster.
Thank you!

1 Like
#22

An update of my failures. So out of 2399 notes I found 23 missing notes. 7 out of them had name clashing with other notes in a different register and were lost because I use case insensitive file systems (default on macOS). For the rest I haven’t noticed anything obvious. @akos0215 I would suggest that you add some sanity checks and at least report inconsistencies. It’s not hard to manually move 23 notes as long as you know that you are missing them.

1 Like
#23

I found what is common for the other 16 notes that failed - they all had evernote check boxes. Hope this helps.

1 Like
#24

Hi @Scientist !

Great, thanks for the hints, I investigate the root cause.
thanks a lot!

#25

Hi! This reply may be a bit late to address any previous replies, but I wanted to mention this nonetheless for the possible benefit of anyone finding this thread in the future–I went through quite an experience migrating off of Evernote and into Obsidian a few weeks ago, and that involved using Yarle.

While Yarle worked, it took me a bit of effort to get it up and running, so I wrote a wrapper script for it and open sourced it to GitHub. That script can be grabbed here: GitHub - dmuth/evernote-to-obsidian: Wrapper for the Yarle app to make converting Evernote notebooks to Markdown easier

Hope that it can be of some help to others in the future.

– Doug

2 Likes