Cognee Database Migrations
topoteretes/cognee
Explains how cognee's two migration chains run, how to check and repair migration state with cognee-cli, and how to write new Alembic or graph and vector migrations.
Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted.
Install Memmesh Migrate
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memmesh-migrate .claude/skills/memmesh-migrate && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .claude/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/memmesh-migrate .agents/skills/memmesh-migrate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .agents/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/memmesh-migrate .cursor/skills/memmesh-migrate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .cursor/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ThinkfleetAI/memmesh.git --path skills/memmesh-migrate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/memmesh-migrate .gemini/skills/memmesh-migrate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .gemini/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/memmesh-migrate .github/skills/memmesh-migrate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .github/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ThinkfleetAI/memmesh memmesh-migrate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ThinkfleetAI/memmesh.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/memmesh-migrate .opencode/skills/memmesh-migrate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memmesh-migrate" agent skill from https://github.com/ThinkfleetAI/memmesh/tree/main/skills/memmesh-migrate into .opencode/skills/memmesh-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memmesh-migrate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memmesh-migrate- GitHub stars
- 419
- Token cost
- ~1k tokens
- SKILL.md length
- 387 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted.
- Works in 5 steps: audit the incumbent → API mapping (cite in the plan) → data migration → …
- : user says migrate from mem0
- SKILL.md covers Canonical sources (fetch first), Step 1 — audit the incumbent, Step 2 — API mapping (cite in… and Step 3 — data migration, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memmesh Migrate is an agent skill from ThinkfleetAI/memmesh. Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted. Audits the current usage, produces a reviewable migration plan (API mapping + data export/import), and executes it on approval. Maps add→observe, search→search, and shows what MemMesh adds that the source lacked (prediction, calibration, bi-temporal graph). TRIGGER when: user says "migrate from mem0", "switch from zep to memmesh", "move my…
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Vector databases and Performance reviews. It works with Letta, Mem0 and SQLite. The repository describes itself as: Persistent, self-improving memory for AI agents. Local-first Rust memory engine with MCP support. The licence is Apache-2.0.
When your agent uses it
- : user says migrate from mem0
- Switch from zep to memmesh
- Move my memory to memmesh
- Replace mem0 with memmesh
Example prompts
- “migrate from mem0”
- “switch from zep to memmesh”
- “move my memory to memmesh”
- “/memmesh-migrate”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bba48f8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.memmesh.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memmesh Migrate loads about 1k tokens when it runs. Until then it costs about 189 tokens; SKILL.md has 387 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ThinkfleetAI/memmesh at commit bba48f8, republished under its Apache-2.0 licence (© ThinkfleetAI). 387 words, ~1,027 tokens.
Download SKILL.mdSave it as
.claude/skills/memmesh-migrate/SKILL.md (or your agent's skills folder).- name
- memmesh-migrate
- description
- Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted. Audits the current usage, produces a reviewable migration plan (API mapping + data export/import), and executes it on approval. Maps add→observe, search→search, and shows what MemMesh adds that the source lacked (prediction, calibration, bi-temporal graph). TRIGGER when: user says "migrate from mem0", "switch from zep to memmesh", "move my memory to memmesh", "replace mem0 with memmesh", or "move local memmesh to the hosted platform". DO NOT TRIGGER for: a fresh integration with no incumbent (use memmesh-integrate) or general SDK questions (use memmesh-sdk).
- license
- Apache-2.0
- metadata.author
- thinkfleet
- metadata.category
- ai-memory
- metadata.tags
- memory, migration, mem0, zep, platform
memmesh-migrate
Move an existing memory setup onto MemMesh with a reviewable, reversible plan.
Canonical sources (fetch first)
- Docs / API mapping: https://docs.memmesh.ai/llms.txt
- Delegate call-site code to:
memmesh-sdk(hosted) /memmesh-cli(local)
Step 1 — audit the incumbent
Detect what's in use and record .memmesh-migration/audit.md:
- Vendor & SDK (Mem0
MemoryClient/Memory, Zep, Letta, LangChain memory, bare Qdrant/pgvector, …). - Call sites — every
add/search/get_all/update/delete. - Scoping — how
user_id/agent_id/run_id/sessionmap today. - Data volume — roughly how many memories, and where they live.
Step 2 — API mapping (cite in the plan)
| Incumbent (e.g. Mem0) | MemMesh equivalent | Notes |
|---|---|---|
client.add(text, user_id=…) | memory.observe({ text, userId }) | MemMesh's engine decides what to save — you can stop pre-filtering. |
client.search(q, user_id=…) | memory.search({ query, userId }) | Same shape; MemMesh adds scope hierarchy + status lifecycle. |
client.get_all(user_id=…) | memory.list({ userId }) | |
client.update(id, text) | memory.observe(new) + memory.supersede(oldId, newId) | Correction keeps provenance instead of destructive overwrite. |
client.delete(id) | memory.delete({ id }) (soft) / hard:true (GDPR) | |
| user / agent / run scoping | userId / agentId / sessionId (+ projectId, platformId) | 6-level hierarchy. |
| (no equivalent) | lattice.predict / predictTarget, behaviors.discover, context.queryGraph | This is why you're migrating — calibrated prediction the source can't do. |
Step 3 — data migration
- Export from the incumbent (its export API or a
get_alldump to JSONL). - Transform each record to a MemMesh
observe(preferred — lets the engine re-extract and build the graph) OR amemory.savewith an explicit id when you must preserve exact rows. - Import in batches; keep a checkpoint file so a re-run is idempotent.
- Reconcile — count source vs destination, sample-search for known facts,
write
.memmesh-migration/reconcile.md.
For Local → Hosted: set sync.url in ~/.thinkfleet-memory/config.toml and
let the CRDT-style bi-temporal sync push; or export the SQLite items and observe
them into the hosted tenant. Reconcile the same way.
Show full SKILL.md (115 more words)Show less
Step 4 — cutover (gated)
Keep the incumbent behind the old flag; bring MemMesh up behind MEMMESH_ENABLED.
Run both in shadow (dual-write) for a window, compare retrieval quality, then flip
the default. Never hard-delete the source until reconciliation passes.
Step 5 — show the upgrade
After parity, add one prediction call at a real decision point so the user sees
what they gained: a calibrated confidence + provenance + honest abstention that
their previous vendor could not produce. Consider running the benchmark skill to
put numbers on the retrieval-quality / cost delta.
Definition of done
Reconciled counts match, known facts retrievable on MemMesh, dual-write window clean, and a rollback note (how to fall back to the incumbent) in the plan.
© ThinkfleetAI, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/memmesh-migrate of ThinkfleetAI/memmesh.
Open the folder on GitHubat commit bba48f8
Compare with similar skills
Memmesh Migrate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memmesh Migrate this skillThinkfleetAI/memmesh | 419 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Cognee Database Migrationstopoteretes/cognee | 32k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Paro Evidencezunor/paro | 105 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Mem0majiayu000/claude-skill-registry | 666 | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Mem0 Bridgemomori777/Artemis | 377 | — | ~453 | Automated safety check: Pass | Custom licence | |
| Cortexdbliliang-cn/cortexdb | 273 | — | ~18k | Automated safety check: Warn | MIT |
Similar skills
Paro Evidence
zunor/paro
Design or audit formal Paro performance claims: release acceptance, cross-engine parity, model calibration certification or non-inferiority.
Mem0
majiayu000/claude-skill-registry
Adds persistent, personalized long-term memory to LLM apps and agents with Mem0, the open-source memory layer: it extracts facts from conversations, stores them in a vector database and retrieves…
Mem0 Bridge
momori777/Artemis
Mem0 memory bridge for AI Girlfriend — search/read/write long-term memories from Qdrant vector DB.
Cortexdb
liliang-cn/cortexdb
Use CortexDB for local-first AI memory, vector search, RAG, knowledge graphs, SPARQL/RDFS/SHACL, corpus-to-graph workflows, external structured-data import (CSV / SQL dumps), and MCP/tool calling.
Hermes Memory Providers
mnemosyne-oss/mnemosyne
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
More from ThinkfleetAI/memmesh
All 24 skills in this repoBehaviors
ThinkfleetAI/memmesh
Surface emergent behavior patterns MemMesh has mined from a subject's history — recurring habits nobody predefined, each with prevalence, stability, and the evidence behind it.
Benchmark
ThinkfleetAI/memmesh
Run MemMesh's competitive benchmark harness (LOCOMO / BEAM) to compare retrieval quality, tokens, latency, and cost against Mem0, Zep, full-context, and naive-RAG baselines.
Context Loader
ThinkfleetAI/memmesh
Load relevant MemMesh context before starting work — searches memory and, for a specific subject, assembles a token-budgeted bundle (profile + behavior patterns + forward predictions + top memories)…
Graph
ThinkfleetAI/memmesh
Query MemMesh's bi-temporal knowledge graph — multi-hop reasoning across entities, point-in-time "what did we believe on date X", and anticipatory retrieval via spreading activation.
Memmesh CLI
ThinkfleetAI/memmesh
MemMesh CLI + local MCP server — the zero-infra, no-API-key path to the same engine as the hosted SDK.
Memmesh SDK
ThinkfleetAI/memmesh
MemMesh TypeScript SDK reference (@thinkfleet/memory-sdk) for the hosted platform at app.memmesh.ai.
Related
Categories
Questions about Memmesh Migrate
What does Memmesh Migrate do?
Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted. Memmesh Migrate is an agent skill from ThinkfleetAI/memmesh. Migrate an existing memory setup ONTO MemMesh — either from another vendor (Mem0, Zep, Letta/MemGPT, a raw vector store) or from MemMesh Local (SQLite) up to MemMesh Hosted.
When should I use Memmesh Migrate?
Memmesh Migrate fits situations like: : user says migrate from mem0; switch from zep to memmesh; move my memory to memmesh; replace mem0 with memmesh.
How do I install Memmesh Migrate in Claude Code?
Run `npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a claude-code`. Or copy the skill folder (skills/memmesh-migrate in ThinkfleetAI/memmesh) into .claude/skills/memmesh-migrate in your project. Claude Code loads it when a task matches its description.
How do I install Memmesh Migrate in Codex?
Run `npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a codex`. Or copy the skill folder (skills/memmesh-migrate in ThinkfleetAI/memmesh) into .agents/skills/memmesh-migrate in your project. Codex loads it when a task matches its description.
Can I use Memmesh Migrate in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ThinkfleetAI/memmesh --skill memmesh-migrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memmesh-migrate, .gemini/skills/memmesh-migrate, .github/skills/memmesh-migrate and .opencode/skills/memmesh-migrate in your project.
What does Memmesh Migrate need to run?
SKILL.md names no scripts, command-line tools or credentials: Memmesh Migrate is instructions for the agent only.
Does Memmesh Migrate access the network?
SKILL.md names 1 domain. As links in the text: docs.memmesh.ai. This is read from the text; nothing was executed.
Is Memmesh Migrate safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memmesh Migrate use?
Memmesh Migrate is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memmesh Migrate use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memmesh Migrate?
Skills that share tags, products or a category with Memmesh Migrate: Cognee Database Migrations (topoteretes/cognee, 32k stars), Paro Evidence (zunor/paro, 105 stars), Mem0 (majiayu000/claude-skill-registry, 666 stars) and Mem0 Bridge (momori777/Artemis, 377 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memmesh Migrate?
ThinkfleetAI (a GitHub organization) maintains it in ThinkfleetAI/memmesh, which has 419 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on August 25, 2026.
Source: ThinkfleetAI/memmesh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.