memory/YYYY-MM-DD.md, MEMORY.md). MemoClaw can import these directly — each ## section becomes a separate, searchable memory with auto-detected importance, tags, and type.
CLI migration (recommended)
.md files in the directory, splits them by ## headers, and sends them to the /v1/migrate endpoint.
Migration is idempotent — running it twice won’t create duplicates. Each memory chunk is content-hashed and checked against existing memories.
What gets imported
Each## section in a markdown file becomes one memory:
| Source | MemoClaw field |
|---|---|
| Section body | content |
| Keywords in content | memory_type (decision, preference, correction, etc.) |
| Header words + filename date | tags (e.g., date:2026-01-30, migrated, openclaw) |
| Content heuristics | importance (0.6–0.9 based on keywords) |
## headers are stored as a single memory.
API migration
If you prefer direct API access, usePOST /v1/migrate:
Response
errors array:
Limits
- Max 50 files per request
- Each section truncated to 8,000 characters
- Sections shorter than 10 characters are skipped
- Requires x402 payment or free tier credits
Install OpenClaw hooks (recommended)
After migrating your files, install the MemoClaw hooks so your agent automatically stores and recalls memories going forward — no manual commands needed.| Event | What happens |
|---|---|
| Session start | Recalls relevant memories based on the first message |
| Context compaction | Saves important context before the window is compressed |
| /new command | Extracts and stores key info before session reset |
| Heartbeat | Periodic consolidation to merge duplicate memories |
After migration
Your memories are now searchable by meaning:Quickstart
New to MemoClaw? Start here.
API Reference: Migrate
Full endpoint documentation.