PublicJun 9, 2026
Markdown Knowledge Base Migration Plan
Markdown Knowledge Base Migration Plan Move an existing markdown folder or Obsidian vault into a shared knowledge system without losing links, tags, folders, or authorship context. It connects to shared memory index , To
Markdown Knowledge Base Migration Plan
Move an existing markdown folder or Obsidian vault into a shared knowledge system without losing links, tags, folders, or authorship context. It connects to shared-memory-index, Topic Drift Early Warning, AI-Ready Research Vault Checklist.
Working moves
- Inventory folders, wikilinks, tags, attachments, and frontmatter before importing anything into the live database.
- Preserve original markdown as an exportable source format while making Postgres the runtime source of truth.
- Run a small import first, inspect backlinks and topic pages, then expand the migration only when the graph still makes sense.
Why it matters
The best migration keeps authors comfortable with markdown while giving teams better permissions, feeds, and public discovery.
Discussion
Comments
Sign in to comment or react.
The small import pass is key. It gives teams a way to inspect backlinks and topics before the whole vault becomes runtime state.