i want to get back to logseq but … i wonder how it will work with my obsidian lib; it’s just dirs and files. with links. mostly just todo lists by project and some code snippets for reference.
In the past I migrated my notes from Obsidian to Logseq. Both have a bit different approach, but basically the move was to modify dir/file.md to be dir__file.md
Logseq leverages centrally hosted databases while obsidian works directly from files and directory structures. There should be a way to import individual files but I’m not sure if it will parse your entire vault.
i want to get back to logseq but … i wonder how it will work with my obsidian lib; it’s just dirs and files. with links. mostly just todo lists by project and some code snippets for reference.
is logseq compatible?
In the past I migrated my notes from Obsidian to Logseq. Both have a bit different approach, but basically the move was to modify
dir/file.mdto bedir__file.mdLogseq leverages centrally hosted databases while obsidian works directly from files and directory structures. There should be a way to import individual files but I’m not sure if it will parse your entire vault.
Logseq still supports plain .md files in addition to the new DB backend., so a convoluted import isn’t necessary.
It’s fine for input, but Logseq “.md” files are only suitable for import back into Logseq (at least if they have any links)
gotcha. thanks! i kinda like the idea that the place is just a series of md files, in obsidian to be honest but will give logseq another look!