Skip to the kits and articles ↓
VaultExit — Obsidian Exit Kit · Article

How to move from Obsidian to Logseq, step by step

Main topic: How to move from Obsidian to Logseq · Facts checked 3 November 2026 — prices change, so re-check the official page before acting on them.

Last checked: 3 November 2026

Short answer: this is the gentlest move in the Obsidian kit, because both apps keep your notes as Markdown files — most notes simply open in Logseq. The catch is shape: Logseq treats every note as an outline of blocks, not a document, so outline structure, block references, properties and plugin features need fixing by hand. Work on a copy of the vault, never the original, and test properly before you stop using Obsidian.

Step by step

  1. Copy the vault. Make a full copy of your vault folder and work on the copy only — never open the original vault directly in Logseq first.
  2. Point Logseq at the copy. Open the copied folder in Logseq as a graph.
  3. Index, then test 10 notes. Let Logseq index (re-index if it offers), then open 10 test notes: a linked note, a daily note, a note with pictures, and a note with tags.
  4. Fix what Logseq shows differently. Outline and bullet structure, block references (Obsidian ^block-id links do not become Logseq ((id)) links), properties and frontmatter, and the daily journal layout.
  5. Rebuild the plugin layer by hand. Dataview queries become Logseq queries and Templater files become Logseq templates — neither carries over automatically.
  6. Test before you switch. Check search, the graph and backlinks on the copy. Only stop using Obsidian when all three behave.

One warning about graph types

Check your graph type before you start. Some Logseq versions offer a newer database (SQLite) graph type whose working state is not plain Markdown files. For this move, use — or check that you are using — a Markdown graph / folder graph, so your notes stay as files you can open anywhere. Graph options differ between versions, so check what your Logseq version offers instead of assuming it matches anyone else’s.

What breaks

What breaksWhat actually happens
DataviewQueries do not carry over. Rebuild each one as a Logseq query — Logseq has its own query system.
TemplaterTemplate files do not carry over. Rebuild them as Logseq templates.
Canvas and Excalidraw-style plugin pagesPages made by Obsidian plugins have no Logseq equivalent — they do not come across as working pages.
Block-id linksObsidian ^block-id links do not become Logseq ((id)) links. Fix them by hand.
Some plugin settingsSettings stored in the .obsidian folder belong to Obsidian and its plugins — they do not move to Logseq.

↔ Scroll this table sideways — the rest of the page stays put.

Final check before you delete the old copy

  • Open 10 notes in Logseq and read them properly.
  • Click 10 links and confirm each one lands on the right note.
  • Open 5 pictures or attachments and confirm they load.
  • Check tags and dates — and your note properties — on a sample of notes.
  • Test search for a few words you know are in your notes.

Only when all five pass — and search, the graph and backlinks behave — is it safe to treat the Logseq copy as the real one. Until then, the original vault stays untouched.

Questions people ask

Can I use the same folder in both apps?

Not as the first step. These steps deliberately use a copy: point Logseq at the copied folder, fix what shows differently, and test search, graph and backlinks there. Once the copy works you can decide how to run things day to day — but keep the untouched original as your backup either way.

Will my wikilinks work?

Links between notes mostly carry over, because both apps work with Markdown files. The exception is block references: Obsidian ^block-id links do not become Logseq ((id)) links, so check block links carefully in your 10 test notes and fix them by hand.

What about Dataview?

It does not carry over automatically. Dataview is an Obsidian plugin, and its queries must be rebuilt as Logseq queries — Logseq has its own query system. The same applies to Templater files, which become Logseq templates. Budget real time for this if queries run your vault.