Logseq DB Import: Pages Empty or Missing
Ongoing Windows, Mac, Linux Updated October 21, 2026
Quick answer
Importing a Markdown (OG) graph into the Logseq database version can leave some pages empty or skip them, and doesn't convert assets, some query macros, embeds or org-mode files reliably. Keep your Markdown folder as the backup, re-index in OG before importing, verify results, and stay on Logseq OG until it works.
Most likely fix: Back up first and keep OG.
Symptoms
After import, some pages exist but have no content, others are missing, images show as broken, #tags became links, queries or embeds don't render.
Why it happens
- Importer limitations (assets, org-mode, #+BEGIN blocks, changed query macros, embeds)
- OG graph not re-indexed before import
- Differences in how DB handles tags, namespaces and properties
- Bugs in the beta importer
How to fix it
Try these in order — the most common fix is first.
1. Back up first and keep OG
- Copy your graph folder somewhere safe
- Keep Logseq OG installed; the Markdown graph keeps working there
2. Re-index in OG before importing
- Open the graph in Logseq OG
- Graph menu > Re-index and wait for it to finish
- Then run the import in Logseq (DB)
3. Verify the import
- Compare page counts in All Pages between OG and DB
- Spot-check pages with images, queries and embeds
- List what's missing before deleting anything
4. Re-import missing pages
- The import always creates a new graph, so redo it after fixing problem files
- Some users report better results importing through the Logseq CLI
5. Report the bug
- File an issue on the logseq db-test GitHub repository with an example file
This guide also covers
- logseq db import missing pages
- logseq migrate to db
- logseq db migration
- import markdown graph logseq db
- logseq og to db
Still not working?
If Logseq keeps failing, you're not alone. See every Logseq problem users report or the alternatives people switch to.