CalS

Initial V10 was old EN converting to a new code base and leaving some features out at release due to time or complexity or conscious decision. They started putting some features back without a particular map. Now there are new owners with their set of priorities. Without a statement to the contrary one shouldn't assume any missing legacy function is returning.

I've posted this before, but I rolled my own at the end of 2121. For my use case. A combination of Windows (folders, indexing) for repository, Directory Opus for gateway, MEGA for sync, Workflowy for notes and GTD, Google Sheets for logging (tables in EN parlance), and AutoHotKey for streamlining and integration. Exported all 56k of my EN notes. My data is mine and secure. I am reasonably insulated from the vagaries of software companies, other than Microsoft. I think I am as productive as I once was. I have local notebooks, they are all now. I don't have to watch a spinning wheel at a PDF displays. Not everyone's cup of tea for sure. End of the day though, it ain't your grandms's EN anymore.

@BummedJim Download EverNote 6.25.1.9091 for Windows - Filehippo.com

It's definitely not a solution when V6 is gone. OP seems to have some sense of urgency. Still waiting for the over/under pool on Legacy sunset. 😉

For sure V10 doesn't have the export simplicity of Legacy. I did it with V6. If I were to do it today I would remove V10, install V6, and go from there.

If W0ndows you can use export to HTML to your c drive and use Windows sort for indexing of titles and contents. Pick a cloud provider of your choice for backup and sync (I chose MEGA for its end to end encryption). File explorer can be a gateway to your data but I opted for Directory Opus which provides an EN like view of things. saved searches, and some powerful file management capabilities. I moved 56k notes at the end of 2021 and have added almost 6k files since. Not everyone's cup of tea, but if all you want is a filing cabinet this works well. Other EN functions I get elsewhere.

Hey, just an observation. I’ve got no horse in the race. Nor agenda. Just thought it was interesting.

It is interesting in today's do it anywhere work environment that such a chunk would be let go. Could be cost, competence, resistance, BS thinks they do it better, or something else. When everyone goes any not absorbed as yet implicit knowledge goes as well.

Off topic. 1Password makes the conversion simple. The time consuming part for me was going to my critical websites and changing those passwords. Any financial institution or web site where I ever used a credit card. YMMV.

As I said in my post, "back in the day".... I filed a trouble ticket in August 2018 re search results not matching on IOS and Windows desktop. The response I got said the the EN server OCR engine had an issue with some fonts. The essence was since I OCR'd on the desktop I got a better OCR. To be clear, this issue may no longer exist, for all I know. I just brought it up for the OP as a maybe for what they were seeing. I left my EN data in a Basic account since I left. I have access to legacy desktop and web V10. The issue still exists. More notes are returned on the legacy desktop and some valid notes are not returned on V10 web. One data point in the wilderness. This was a data issue pre V10 that EN opted not to address in my view. Salient bit of the email exchange from 2018. To first elaborate on why it works on Windows when compared to iOS - Windows uses a different search mechanism to extract text from PDFs than the one used by our server, which is what web and iOS use. The issue you're seeing is related to server-side search, which seems to have an issue with recognizing the wrong font when scanning PDF files. The text in the PDF is printed in a monospaced font, so the letters are wider, but the OCR sometimes incorrectly recognizes it as a non-monospace font, so it sees the gap in position and thinks there's a space there.

Not sure about defe4ating the purpose. If local OCR is more complete than EN OCR it kind of is what it is. Until/when/if EN changes its OCR engine you will continue to have missing notes in your searches.

@bmcl26Yeah, I do title searches on mobile which is fine for what I do on mobile. But sometimes I want to get at the file contents when on my desktop. And that needs a contents index. 🤷‍♂️

Can't search contents then.

If I was in CA and I got a severance package I might say I was sacked. 😉

Not sure OneNote is going to be any better than EN at keeping your notes "from prying eyes around the world". If that is a major concern. Good luck in any case.

When local notebooks were kicked to the curb I opted out of EN, back in late 2021. Windows solution for ideas. I exported all my notes (56k of which 9k were local) using the HTML option. All attachments get exported in this fashion and tags are maintained in the HTML. I created a simple folder structure on my C Drive to hold my EN data and new data (mostly PDFs). I use Mega as a cloud service for backup and syncing across devices. Mega has end to end encryption so only I have the key and my data is a blob on Mega servers. I can only search titles on mobile but this is not a negative for me. I use Windows indexing on the Mega folders which provides remarkably fast search times, mostly as quick as I type. Didn't have to, but I bought a license to Directory Opus which provides an EN like interface to search my repository of 27 GB. Plus some great file management tools. This has worked for me as major part of my EN use case was paperless. I've added 5500 "notes" since I switched. The notetaking and task stuff I now do with Workflowy. YMMV.

Back in the day local OCR worked better than server OCR. Not sure if V10 accepts locally OCR'd documents the same as Legacy did. Easy enough test, OCR and replace in EN a few of the documents that did not appear in your search as they should have. Than search for Adam again.

Perhaps if a sunset date was announced the mass migration (in or out) would be triggered? Why not such a date?

I cancelled at the end of 2021. I still have legacy around as a backup with my now Basic account. I just did a search on legacy and Web V10. Web V10 includes results for text within a PDF. Though the results for the same search were 591 on Legacy and 404 on Web v10. Not surprising to me as local OCR always seemed to work better than server OCR in the day. Not sure what engine EN is using on the server now. If you want to test, create a Basic account. Create a couple of PDFs and OCR one locally before adding to the new account. Then search via Web V10 and see what you get.

Just went to my legacy copy. Did not get a "nag" so went to check for updates and got this. Looks fairly clear to me {New Windows Client) that legacy is not on the backend of the update. That being said it would be interesting to know how much EN server volume is V10 clients versus pre V10 clients. I would wonder if that is in their calculus for when to pull the plug. And the trigger for the conversion push. Folks are using pre V10 for some reason or other, from inertia to use case. The push should at least catch the inertia folks. I did not update. 😉

For sure. Back in mid 2021 my assumption was my "corner case" flow (high access paperless and my form of GTD) wasn't coming anytime soon. Mostly to do with the virtually instantaneous response time I had with V6 and less to do the loss of local notebooks. So I exited via export in December 2021. I kept Legacy desktop just in case I oopsed something. My forays with my wife's simple 2k notes account continue to confirm my hypothesis as this point. Doesn't make V10 bad, just not for me. In this incarnation anyway.

Don't know what is blacking you. Are you on a corporate network? Download EverNote 6.25.1.9091 for Windows - Filehippo.com

Try the filehippo website.

Well, in theory, one can use Legacy until one has to update one's computer. Without syncing of course. And as long as you don't sign out. Definitely a time line on this approach. Current OS device air gapped in the basement in 10 years? Probably not. If you don't care for V10 I'd get your migration plan in place and be ready to execute (maybe tested a bit). Voice of experience here, It took a minute for me to get it right. Anyway, nothing wrong in using Legacy as long as allowed and acceptable . Maybe some of whatever the problematic issues are for you will get resolved in the meantime. One can dream.

As always the voice of reason in a chaotic world. ☺️