Data export.
Portability guidance for memory data so teams can retain continuity across tool and model changes.
Why export
Export protects continuity and avoids memory lock-in to any single client surface. Use it before deleting a workspace, migrating storage, or changing account ownership.
empirical memory export --scope personal --out ./empirical-memories.json
What to export
Include memory records, relationships, and metadata needed for downstream replay. Treat the resulting file as sensitive because it may contain private project context.
Operational cadence and limits
Schedule periodic exports and test import/restore flow before relying on backups. Export is a portability and backup aid; it is not a live sync or a substitute for access controls.
Verify: Open the JSON only in a trusted environment, confirm expected records are present, then store or delete it according to your retention policy.
Last updated: May 21, 2026