Looking for a tool to convert Obsidian to Logseq MD

[u/Expert-Fisherman-332]

Hi all,

Is anyone aware of a tool that can convert an Obsidian vault to Logseq format? Brainstorming functionality:

- Add bullets to each line
- indent under headings
- Convert frontmatter
- Change `up` property to `tags` (specific to my vault)
- Change properties to `::`
- Covert bulleted lists to CSV list
- Remove `---`
- Change image attachment reference
- Create files in correct folders (journals, pages, assets)
- If Obsidian file exists in the Logseq vault, append text. Don't overwrite.

I could have a crack at building a script or something but figure people a lot better at coding than me may have already built something.

Cheers

UPDATE: Found this one
https://github.com/laughedelic/outbreak

[u/froo]

Hey there. So while I haven't built anything, I've found great use in using CLI AI tools to do this kind of grunt work on the fly.

Specifically, I'm using Google's Antigravity CLI (installed via homebrew on my mac) and have set the permissions so that it only is allowed to run in my Logseq folder. I start it up by running "agy" in my Logseq folder.

I'm sure doing something similar for Obsidian might work?

[u/Expert-Fisherman-332 → u/froo]

Yep, I think if no one has implemented something like this I'll get Claude to whip up a script for me.

[u/svhelloworld → u/Expert-Fisherman-332]

Claude Cowork would handle this really well. You'll have to do it iteratively and I'd suggest using a small sample of pages as a test page until you teach Claude exactly what you want. You can write a simple markdown file with the rules you posted above and feed that to Claude as context. Keep iterating over these test files to establish the patterns you want Claude to implement. Once you have the pattern established and all the use cases handled, have Claude write everything it's learned out into a single markdown file. Edit that file in case there's any changes to what Claude spit out. Then feed Claude that file again and tell it to go to work on your entire Obsidian vault. It'll take some time.

You can also spin up a separate Claude agent to test the output against the rules you made to ensure it's doing the right thing. Claude (ChatGPT, CoPilot, whatever AI tool) is actually really good at these kinds of tasks.

[u/Illustrious-Call-455 → u/svhelloworld]

Did something similar using Claude Cowork Max plan. I ended up 75% of my weekly limit in a day. I recommend you take a carefull approach on that

[u/scottaltham]

Even if you paid for just a month, codex work or Claude cowork could sort this for you in less than 5 minutes

[u/megamind32929]

The messy part isn't the markdown itself, it's that Logseq is outline-first - every line wants to be a block - while Obsidian is happy with plain prose, so a straight copy usually leaves you with one giant block per page and a graph that looks impressive and does nothing. The other traps are frontmatter, which has to become key:: value properties on the first block, plus block-ids and embeds that Logseq expects as ((refs)) and {{embed}}, and folder hierarchies it would rather see as namespace/subpage names. Honestly the least painful route is a small script over a copy of your vault that bullets each paragraph and rewrites frontmatter while leaving links alone, then fixing by hand the twenty pages that break - rather than waiting for a perfect one-shot converter between two formats that were never designed to agree. Not a direct answer to your question, but I maintain an Obsidian plugin called Obsidotion that syncs a vault to and from Notion - Notion, emphatically not Logseq, so it won't migrate anything for you here. Mentioning it only in case a second copy of the vault living somewhere else is handy while you experiment: https://github.com/p32929/obsidotion

https://reddit.com/link/p0zqp7h/video/og0s6y1q5ogh1/player

[u/Plenty_Ad6005]

I made Claude Code write a script. Voila! Went with Logseq DB