Keep a readable copy of your pages.
Your knowledge should remain readable outside the tool that stores it. Memrain can export live pages into a Markdown tree with frontmatter.
Illustrative example
Can I keep a copy of our project notes outside Memrain?
Export the selected source to a directory of Markdown pages, then check that the files contain the material you intended to keep.
Illustrative scenario, not a live product result.Move page content into ordinary files.
The export command writes each live page with its body and frontmatter, organized by slug. You can export all live pages or narrow the operation to one source. That gives you a readable copy for inspection, portability or a separate content workflow. The files can be opened without running a Memrain client or knowing the database schema.
Separate a page export from a full backup.
Markdown export covers page content. It does not include the complete facts ledger, page version history, grants, relationships or embeddings held in Postgres. Preserve and test database backups when you need to restore the full installation. Keeping an exported directory is useful, but it should not be presented as a complete replacement for an operational backup and restore process.
Review a re-import before applying it.
The Markdown import path is preview-first and create-only: it refuses slugs that already exist, including deleted pages. It restores page content into a registered source and leaves indexing to reconciliation. It does not rebuild the full previous database or automatically run fact extraction. Check the preview, source and expected page count before using exported files in another installation.
Keep the context. Move the work forward.
Connect your knowledge to the AI you already use. Find your starting point and make the next conversation count.