I’m considering transitioning from Logseq to Obsidian because my workflow can’t remain on hold much longer while waiting for future Logseq updates and because I want to stay with the Markdown file format. Before I decide on making the move, I’d like to see if one can prepare a Logseq graph properly and understand the best practices from people who have already done this.
If you’ve migrated from Logseq to Obsidian, how did you handle the following challenges?
Block references
Logseq block refs import as UUIDs in Obsidian.
-
Did you convert them to something more readable?
-
Did you restructure your notes to avoid block‑level linking?
Page & block properties
Page properties can become YAML frontmatter, but:
-
How did you deal with block‑level properties?
-
Did you flatten them, convert them, or restructure the blocks?
Queries
I’ve mostly used only simple querries so far, thus Obsidian’s new Base/Dataview‑style features seem promising, but:
-
How did you replace Logseq queries that rely on block‑level data?
-
Did you convert blocks into pages or subheadings (e.g.,
page#subheader) to make them queryable?
Tasks
-
Did you reformat Logseq tasks into Obsidian’s task syntax?
-
Any pitfalls when converting recurring tasks or task metadata?
Namespaces
-
How did Logseq namespaces behave after import?
-
Did you keep them, flatten them, or reorganize?
Outlining
-
Does Obsidian’s Outliner plugin correctly interpret Logseq’s indentation structure?
-
Any cleanup needed?
Anything else I should prepare for?
I’d love to hear about unexpected issues, cleanup steps, or tools/scripts that made the migration smoother.