migrate

Migrate legacy engram memories to schema_version 2 and archive originals.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/toejough/engram --skill migrate-toejough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/toejough/engram/tree/main/skills/migrate
Command: npx skills add https://github.com/toejough/engram --skill migrate-toejough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate legacy engram memories from the pre-cfd5fb5 flat format to the current split layout of feedback and facts, enabling consistent recall integrity and future-proof memory data.

Core Features & Use Cases

  • Locates legacy memory files in ~/.local/share/engram/memories.v1-backup/ and ~/.local/share/engram/memories/ and guides the user through a safe upgrade.
  • Rewrites each legacy memory into the current schema (schema_version = 2) and separates task-shaped situations from hindsight-biased content.
  • Archives the original legacy sources after successful migration and verifies parse-ability with engram show.

Quick Start

Run the migrate skill to convert all legacy memories to the current format.

Frequently Asked Questions about migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy engram memories to the current format?

To migrate legacy engram memories, trigger the migration via the /migrate command or related prompts to rewrite pre-cfd5fb5 flat files into the current split feedback and facts layout. This process updates your data to schema version 2.

When do I need to convert memory files to schema version 2?

You need to convert memory files to schema version 2 when you have existing flat memory data that requires consistent recall integrity and future-proofing. This applies if legacy files exist in your engram memories or backup directories.

Does the memory migration process archive my original legacy files?

Yes, the memory migration process archives your original legacy sources after successfully rewriting them into the current schema. It also verifies parse-ability using engram show to ensure data integrity.

How does the engram migration separate feedback from facts?

Engram migration separates feedback from facts by rewriting each legacy memory and classifying task-shaped situations as feedback while isolating hindsight-biased content as facts. This creates a split layout for better data organization.

What is the best way to upgrade old memory backups without losing data?

The best way to upgrade old memory backups safely is to run an automated migration that rewrites legacy files to the current schema and archives the originals for verification. This ensures no data is lost during the conversion.

Why are my legacy memories not working after an engram update?

Legacy memories may not work after an engram update because they remain in the pre-cfd5fb5 flat format instead of the current split feedback and facts layout. Running a schema migration resolves this incompatibility.