Migration Guide

Upgrade between versions or migrate from other memory solutions.

From v0.7.x to v0.8.x

v0.8.0 introduced significant changes:

  • New tools: epistemic_promote, epistemic_demote, epistemic_resolve, epistemic_diff, epistemic_list
  • Identity unification: New ownerAliases config for cross-channel identity
  • Channel isolation: New channelIsolation config (default: true)
  • Health alerts: Proactive monitoring system

Steps

  1. Update the plugin: pnpm --filter @openclaw/memory-claw build
  2. Add new config fields (ownerAliases, channelIsolation) — optional but recommended
  3. Existing memories are compatible — no data migration needed
  4. New columns are added automatically on first access

From Other Memory Systems

If migrating from a simple key-value memory plugin:

  1. Export existing memories as JSON
  2. Use epistemic_store to re-ingest each memory
  3. The pipeline will assign confidence scores, decay classes, and tiers automatically
  4. Review the imported memories with epistemic_list
Note: Re-ingested memories will be scored as system source (0.9 weight). If you want them scored as user_explicit, set the source parameter explicitly.