Backup & Restore

Memo supports full backup and restore via .memo zip archives. Export everything or restore on any machine.

.memo Export Format

A .memo file is a zip archive containing all user data:

Path	Contents
data/sessions/	All chat session files
data/memory/	SQLite memory database and vector index
data/providers/	Encrypted provider configurations
config/config.yaml	Application configuration
data/orchestra/	Orchestra mode role assignments
data/calendar/	Calendar events database
data/whatsapp/	WhatsApp message and contact data
data/mood/mood.db	Mood engine state
data/proactive/	Learned habits and proactive-learning state
data/routines/	Scheduled automations (Routines)
data/taskloop/	Autonomous task lists
data/permissions.json	Agent tool permission policies
data/skills/	Installed skills
data/machine.key	Machine-specific encryption key — required to decrypt providers.json's encrypted API keys

As of v3.3.3, the backup is genuinely complete: calendar events, learned habits, routines, task lists, agent tool permissions, and installed skills are all included, and machine.key — previously never exported at all — now always is. Restoring an older, pre-v3.3.3 backup on a different machine or after a data wipe would have permanently left every provider API key undecryptable. Still deliberately excluded: downloaded models (optional via their own toggle), the device-specific Drive sync cursor, the machine-specific tsnet identity, and the backup function's own snapshot directory.

Export

From Settings → Backup → Export:

1. Choose a destination folder
2. A .memo file is created with timestamp: memo-backup-2026-07-04.memo
3. A WAL checkpoint runs before export to ensure SQLite data is fully flushed

Import / Restore

From Settings → Backup → Import:

1. Select a .memo file
2. Data is extracted to a temporary directory first
3. Atomic rename moves files into place
4. If any step fails, original data is not touched
5. Restart Memo to load restored data

Wipe

The /api/system/wipe endpoint clears all user data:

• All sessions deleted
• Memory database deleted
• Provider config deleted
• Calendar and WhatsApp data cleared

The data/machine.key file is preserved — wiping does not destroy your cloud backup encryption key.

Cloud Sync

See the Cloud Sync documentation for automatic encrypted Google Drive backup. The cloud backup includes the same data set as the .memo export.

Security Notes

• .memo files contain your API keys (encrypted with machine key) — treat them as sensitive
• The machine key is included in exports; without it, encrypted provider configs are unrecoverable
• Wipe preserves machine.key to avoid losing cloud backup access permanently