Portability
Import and Portability
Move selected durable context into Wenlan and keep Wenlan's readable artifacts portable outside the daemon.
At a glance
01
The current CLI does not expose a general Markdown-vault importer. Migrate selected durable notes explicitly through store, capture, or the memory store API.
02
Wenlan's pages and session logs are readable Markdown, so the human record remains portable even though retrieval needs the daemon.
01
What migration is for
Migration is useful when you already have durable project notes, meeting notes, or research notes that should become searchable AI work context.
Do not migrate everything just because it exists. Wenlan works best when selected material is useful to future agents, not when the memory layer becomes a bulk file mirror.
02
Migrate selected Markdown context
Use wenlan store or normal capture flows for selected durable notes. For larger moves, use a small script that reads source files you choose and posts distilled facts to /api/memory/store.
Start with a representative sample, then recall against it before moving a larger archive. That gives you a chance to see whether the migrated context is useful or noisy.
Terminal
# readable Wenlan artifacts
ls ~/.wenlan/pages/
ls ~/.wenlan/sessions/
# migrate selected durable notes explicitly
~/.wenlan/bin/wenlan store "Imported note: <durable context>" --type fact03
Wikilinks and graph context
Markdown links and wiki-style relationships are useful signal, but they are not the same as the source-backed page model.
Links can still help when you rewrite selected notes into explicit memories. Source-backed pages are stronger when Wenlan can trace the synthesized claim to the source memories that produced it.
04
Keep ownership clear
If another app is your knowledge-base source of truth, keep using it for polished notes. Use Wenlan for the AI work loop: captures, handoffs, source-backed pages, recall, and cross-client context.
Running both is possible through MCP, but you still need a human rule for which system owns which kind of context.
05
Read Wenlan outside the daemon
Wenlan projects readable artifacts under ~/.wenlan, including pages and session handoffs. You can open those files in an editor or point a Markdown reader at them.
Plain-text access is not the same as full Wenlan behavior. Capture, recall, dedupe, distill, review, forget, and index updates still need the daemon and CLI/MCP paths.
06
Privacy and backup caution
Imported vaults and exported-looking Markdown can contain sensitive project history. Do not publish ~/.wenlan, sync it to a cloud drive, or attach it to an issue without redaction.
For backups, treat ~/.wenlan and the daemon data directory as private application data. If you need to recover or migrate machines, verify with wenlan doctor afterward so the daemon, index, and MCP config agree.
Next
Local Git History
Inspect the real git history Wenlan keeps for readable page, session, handoff, and status artifacts.
Read next