Backup
Backup and Migration
Back up Wenlan's readable artifacts and daemon data together, then verify the restored runtime before trusting recall.
At a glance
01
~/.wenlan contains readable artifacts, but the daemon data directory also matters for a complete backup.
02
After moving or restoring Wenlan, check status and doctor, then recall a known fact in your client.
01
What to back up
Quit the desktop app, then run wenlan background off to stop the background service before copying the readable artifacts and daemon data together. Include custom data or page locations. A wiki export alone is not a full database backup.
Default data: ~/Library/Application Support/wenlan/ on macOS, ~/.local/share/wenlan/ on Linux, and %LOCALAPPDATA%\wenlan\ on Windows. Older installations may retain legacy folders as migration backups. Include them in your backup; the official guide names their locations.
~/.wenlan/02
Keep backups private
Backups can contain private captures, project decisions, pages, session notes, and database contents. Store and share them only where you intend.
03
Before moving machines
Install the runtime on the new machine. Quit the app and run wenlan background off before restoring your backup to the matching platform locations, including any custom paths.
After restoring, reconnect each MCP client if its settings contain paths from the old machine.
04
Verify after restore
Reopen the desktop app or run wenlan background on to start the restored runtime, then run these checks in a macOS or Linux terminal. Then use your connected client to recall a known fact and check that the expected fact and source appear. In Claude Code, /wenlan checks connection status. If doctor reports a problem, resolve it before adding new production memories.
~/.wenlan/bin/wenlan status
~/.wenlan/bin/wenlan doctor05
Plain Markdown fallback
If you cannot restore the daemon immediately, the projected Markdown under ~/.wenlan is still useful as a human-readable fallback.
That fallback does not provide capture, recall, distill, review, forget, or index updates. Treat it as readable continuity, not a full Wenlan runtime.
06
Deletion is separate
Uninstalling Wenlan's service does not delete memory data. Deleting memory data is a separate decision because it can remove the only local record of project history.
When removing Wenlan permanently, review what is in ~/.wenlan and the daemon data directory first. For normal troubleshooting, keep the data and use doctor output to diagnose the install.
Next
Wenlan Configuration
Configure Wenlan spaces, MCP clients, daemon bind address, local paths, models, and keys without editing the database by hand.
Read next