I have recently moved to Obsidian for similar reasons and will be unlikely to return to LogSeq, which does make me a little sad, as I really enjoyed LogSeq for a number of years. It just failed to keep up with my changing needs.
I do not, however, have much positive advice for you. I was vastly unprepared and moved into Obsidian a little too suddenly. While I have no regrets now, the transition was somewhat rough.
I lost most of my block references, as I didn’t recognise what they were until too late. I still have my LogSeq database and will review it if I ever need those exact references, but I didn’t have too many to start with anyway.
Similarly, I didn’t really use block properties. But I can warn you about page properties. The formatting is ever so slightly different to YAML, so you will need to find a way to convert a lot of double colons to single colons. Similarly, any property that allows multiple values (say ‘tags’), will need to be reformatted. There is no default search and replace but there are plugins to assist with this. I did most of it manually, however, as I was using the opportunity to rework my page property settings. Obsidian Bases also helped with this. Once I understood how Bases can work, I used the sorting feature to identify pages with incorrect properties. Bases are also great for simple page searching, better in some respects than even Notion’s databases.
As for queries, again, I didn’t really have block properties to work with. Regardless, DataView queries are much easier than DataQuery, or whatever it was that LogSeq used. What blocks I did want to highlight, I think I ended up marking up with various task types. This works great with the Minimal style plugin which allows for ‘tasks’ to be assigned as to-dos, questions, answers, ‘hot’ tasks, and more, which can all be filtered for with Dataview. Tags are also simple to work with.
Continuing on with tasks, I think I had to incorporate Tasks to get the most out of Dataview, but I am still testing whether I need it. I don’t like the format of Tasks’ query results, whereas Dataview results were easier to customize (albeit with CSS again). YMMV.
In LogSeq, I had most of my tasks using the “LATER” format. There is an Obsidian plugin that will find all of these items for you. Again, there might be faster, automated ways of converting them, but I manually converted almost 100 of them to the markdown format as a way to find those I could delete before updating.
No advice on namespaces, sorry. Never quite understood the concept.
Outlining though? Oof. Prepare to fight the CSS. Maybe it’s just me and my tastes, but I found that I struggled with getting the outlining to look right. I think this is due to how LogSeq fudges the markdown with list dashes, and that I was never swapping to the document view that LogSeq has, whereas Obsidian has three different views to switch between. So to get the paragraph breaks to be slightly bigger than the line spacing across all three views, I ended up having to use list dashes at the start of my plain text paragraphs. I didn’t like the alternative of two line breaks; again, a matter of taste. Good excuse to learn CSS though.
Final comments about scripts, I did end up using a little bit of command line text replacement instead of installing a plugin. I use Linux now, so the command was just of the format:
find . -type f -exec sed -i 's/old-text/new-text/g' {} +
This helped with changing property names en masse, but I don’t have the know-how to really take full advantage of this function.
Anyhow, happy to try and answer any other queries you might have. I know there were more warnings than tips, but you probably want to hear about a negative experience to justify taking your time to get it as right as you can.
