memory-transfer

Migrate memories and personalized data across AI assistants.

12|3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/marswaveai/memory-transfer --skill memory-transfer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-transfer
Source: https://github.com/marswaveai/memory-transfer/tree/main
Command: npx skills add https://github.com/marswaveai/memory-transfer --skill memory-transfer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating between AI assistants often loses context: histories, preferences, and writing styles. This Skill enables seamless transfer of memories and personalization data between local agents (Claude Code, Cursor, Windsurf, OpenClaw, etc.) and cloud agents (ChatGPT, Gemini, Copilot, Claude, Perplexity), preserving continuity across transitions.

Core Features & Use Cases

  • Cross-agent memory migration: migrate stable memories, preferences, and working styles across agents with guided prompts and optional local exports.
  • Dual-path extraction: supports both local memory scraping and cloud-export workflows, with cleaning, validation, and import-ready output.
  • Privacy & safety: excludes sensitive credentials and conflicts with user control and confirmation before importing into new agents.

Quick Start

Instruct the AI to start memory transfer by telling it which sources you are migrating from and where to import to, then follow the guided prompts to complete the process.

Frequently Asked Questions about memory-transfer

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

FAQPage Schema
How do I transfer memories and preferences when switching from ChatGPT to Claude?

Cross-agent memory transfer migrates histories, preferences, and writing styles between cloud assistants like ChatGPT and Claude by reading exported data, cleaning it to a memory schema, and writing it to the target system after user confirmation.

Can I migrate personalization data from local agents like Cursor or Windsurf to cloud assistants?

Yes, cross-agent memory transfer supports dual-path extraction, allowing you to scrape local memory files from agents like Cursor or Windsurf and map that data to a cloud assistant's memory system.

Does cross-agent memory migration work with both local memory files and cloud export workflows?

Cross-agent memory migration supports both local memory scraping and cloud-export workflows, reading data from local files or remote assistant exports, cleaning it, and validating it before importing into the target memory system.

How do I start the memory transfer process between different AI assistants?

To start memory transfer, instruct your AI assistant which source you are migrating from and the target destination, then follow the guided prompts for extraction, cleaning, and confirmation to complete the import.

What happens to sensitive credentials during AI memory migration?

AI memory migration excludes sensitive credentials during the data cleaning process and requires explicit user confirmation before importing any mapped memories into the new assistant, ensuring privacy and user control.

Why do I lose context when switching AI providers and how can I preserve it?

Switching AI providers loses context because histories and preferences are not natively transferable; cross-agent memory transfer solves this by extracting, cleaning, and mapping your personalization data to the new assistant's memory schema.