I recently asked myself how easy it would be to migrate to Obsidian if I had to stop using Logseq for some reason? I’m happy with Logseq, but like to know that I could switch if I had to - it gives me peace of mind about my data.
The question is really a combination of several issues: user interface, features, and data. Out-of-the-box Obsidian can’t really handle a logseq-style workflow, but there are a number of plugins that can help:
These take care of many of the user interface and features that one might worry about, such as outlining, queries, and tasks. (Not entirely, since Obsidian isn’t truly block based - but close enough that one could manage.) But what about moving your data over?
As I see it there are four areas one has to worry about when migrating: block references, block properties, page properties, and tasks. Fortunately, when you create block references Logseq creates a hidden property that can be searched for in Obsidian, so that isn’t an issue. Less fortunately, Obsidian doesn’t seem to have any concept of block properties. I don’t use those much, but for people who do that could be a problem. I don’t know if there is a work around?
Regarding the last two, page properties and tasks, it seems possible to convert to Obsidian and the Obsidian Tasks plugin using clever search and replace tricks. I haven’t tested this fully - just enough to ease my mind that it is possible. I’m not a programmer but I do know some regex (grep). I use BBEdit’s multi-file search and replace tool on my vault. Here is one example:
[/] #task \1 🔼
I initially had difficulty because I wasn’t placing the priority marker at the end of the line, but this works. (Note: I had to add the [/] “custom status” in the settings beforehand.) I didn’t do anything similar for page properties, but that seems much simpler. Perhaps someone has already written a script to do this?
Anyway, my sense at looking at this was that it would take me one weekend of work to be up and running in Obsidian if I had to switch for some reason, and perhaps another few weeks before I was able to re-establish all my existing workflows in the new environment. Not something I would do lightly, but nice to know that it can be done.