Preparing a Logseq graph for migration to Obsidian — what should I watch out for?

Help
1

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.

2

Does someone have experience with this transition ?

3

Your inquiries are overly general. I recommend submitting them to an AI model and attempting to create a vault in Obsidian independently to understand the underlying mechanics. Knowledge bases are highly individualized constructs dependent on the creator’s habits; we cannot ascertain what is important or convenient for you. Overall, the list of questions is commendable, but it is unlikely that you will receive satisfactory answers here. I encourage you to explore through empirical experimentation and not to abandon your established tools immediately.

4

Thanks @LemeRus . These are all aspects of LogSeq that would need to be converted. May I ask what makes them overly general ?

I did mean to ask for the experience of users having made that transition, not of an AI model. For example, how people were dealing with block references.

5

I shall start anew and endeavor to clarify my previous statements.

I agree: all stated points constitute aspects of LogSeq that require decisions regarding their handling. Their excessive generality stems from the inseparability of the vault from its author and the evident scarcity here of individuals who have migrated their vaults specifically from LogSeq to Obsidian. I can readily cite half a dozen scenarios wherein different individuals, for various reasons, would handle the same block references differently.

For instance, some users may wish to immediately process the vault using regular expressions to eliminate hard-to-read names with minimal effort; others will tolerate aesthetically displeasing links due to lack of time; a third group will not even see block references, reading their vault solely in reading view; a fourth group will manually correct links as they interact with them and the vault; a fifth group will again not encounter the problem, but due to the absence of block references (i.e., a structure more native to Obsidian than to LogSeq); and a sixth group will decide not to migrate to Obsidian at all due to this discrepancy. Moreover, in none of the described scenarios will individuals refactor their vaults to achieve a structure more native to Obsidian.

I can devise scenarios perhaps not so diverse, yet still variable, for each of the questions raised. Given that you have been waiting for over a month without receiving answers, it may be assumed that there are no individuals on this forum capable of sharing their experience with you. I sincerely wish to help but cannot do so without knowing the scope of the proposed changes, the existing vault structure, or the nuances of information display important to you.

6

Hi! I recently migrated (back) to Obsidian, and decided to do it the proper way and implement an importer based on the official plugin. Here’s my implementation: Add Logseq Markdown graph importer by laughedelic · Pull Request #592 · obsidianmd/obsidian-importer · GitHub

It has some pretty detailed documentation:

If anyone wants to try it out on their notes and provide feedback, it would be great. But even if you don’t intend to use my implementation, the docs might come useful. There’s also a simpler, older, but maybe easier to review list of Markdown flavor differences here.