This migration skill is mostly purpose-aligned, but it can persistently copy sensitive legacy assistant memory into OpenClaw and may replace the active MEMORY.md file despite describing an additive, review-first workflow.
Use the report and staging steps first, then inspect imports/easyclaw before importing anything into the active workspace. Do not run --import-memory unless you are comfortable replacing active OpenClaw MEMORY.md from legacy EasyClaw data; keep the generated backup and manually merge if you want additive migration only. Review old prompt and memory files for stale, sensitive, or unsafe instructions before making them active.