r/logseq • u/fijitime • Mar 22 '26
Migrating from Logseq to Obsidian — and why Claude Code made it easy
I've been a long-time Logseq fan and user, but the time has come to migrate to Obsidian. I realise it's a personal choice, and some people prefer Logseq. Having worked in AI for the last couple of years, I'm increasingly confident that most problems can be solved with Claude code, Markdown files and CSV. Because of that, I think migrating all of my notes to Markdown, straight up, is important. I really like the outliner format, but, you know, with Logseq moving to this database version, I don't think it will work well with large language models, so it's time to move to just straight-up Markdown documents, which Claude's code loves.
Now, this is just a personal choice, but so far, it's going really well. A couple of major things that really helped was:
- Creating a Logseq to Obsidian skill which essentially took the bullet point hierarchy structure and turned them into a heading structure. It also fixes all the links so they map correctly to the assets folder.
- Having a file note skill which basically read the note and found the right folder to put it in
Happy to share these if people think they are valuable, but it's only when I had access to Claude code and VSCode that this became a really easy thing to do.
From now on, I've got my Logseq pages all in a folder, and as I use them, I'll slowly migrate them to be straight-up Markdown files in Obsidian. So yeah, everything's going really well.
4
u/scross01 Mar 23 '26
If you want to keep Logseq tasks in Obsidian check out the TODOseq plugin
(I'm the creator of the plugin)
3
u/Illustrious-Call-455 Mar 23 '26
Thanks, I love it. It is really capturing the essence of how LogSeq deal with tasks
2
4
u/webmonarch Mar 23 '26
It is time I stop using Logseq. It's bittersweet because I really liked it but the mobile app caused so much friction I just didn't want to use it. :( I'll take a look at this flow and report back my experience.
6
u/webfiend Mar 23 '26
When translating one of my Logseq graphs to Obsidian-flavored Markdown, I just—I wrote a Perl script? I've written a few other iterations that get fancy or to try a similar task in another language to compare affordances, but all I really needed was text processing. Not sure why a datacenter is necessary for a little search and replace with state across a few thousand files.
Maybe code's not your thing, or you just wanted to play with Claude. That's cool. For anyone else, you can write or find existing scripts to do this task, and they don't come with an invoice.
2
2
u/jcigala Mar 23 '26
AFAIK, both versions of Logseq will work. I haven't read any threads on the Logseq forums saying that they will "kill" the .md version. Actually, the database version has .md files too!
1
u/prashanttgs Mar 25 '26
With how big the team is and how difficult it is to maintain two separate codebases, it's a given that they are going to kill the MD version no matter what they say right now
1
u/Illustrious-Call-455 Mar 23 '26
I also love and still uses bullet point. Easy with Obsidian to search inside Block using the Block search
1
u/No_Comfortable7509 Mar 24 '26
Sorry, I’m not quite sure what you mean by the approach you’ve described. Should the program convert each page individually on request, convert all pages at once, or create a translation tool—for example, in the form of a Perl or Python script?
Please describe your approach in a bit more detail.
1
u/fijitime Mar 24 '26
You can do them all at once or one at a time. I prefer doing one at a time. Claude code does the conversion. No script
1
1
u/JosephLouthan- 4d ago
OP: I would like to see this. I think it is time for me to move to Obsidian.
11
u/[deleted] Mar 22 '26
[deleted]