migrate-profile

Consolidate Claude Code project data across elpaca profile changes.

9|1|Updated Jul 19, 2022

Search Tags:#project management #claude code #emacs #data consolidation #profile migration #elpaca

Ready to run

npx skills add https://github.com/benthamite/dotfiles --skill migrate-profile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-profile
Source: https://github.com/benthamite/dotfiles/tree/main/claude/skills/migrate-profile
Command: npx skills add https://github.com/benthamite/dotfiles --skill migrate-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of Claude Code project data by consolidating it across different elpaca profile versions, preventing data loss and re-authorization prompts after profile changes.

Core Features & Use Cases

Automatic Profile Detection: Intelligently determines the new elpaca profile if not explicitly provided.
Project Discovery: Scans and identifies all Claude Code projects based on elpaca directory patterns.
Non-Destructive Migration: Copies session files, memory data, and project trust entries without overwriting existing data in the target profile.
Use Case: After updating your elpaca profile to a new version (e.g., from 7.0.0 to 8.0.0), this skill will automatically find all your old projects and merge their session and memory data into the new profile's project structure, ensuring continuity.

Quick Start

Use the migrate-profile skill to consolidate your Claude Code project data for the new profile 8.0.0-dev.

Frequently Asked Questions about migrate-profile

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

FAQPage Schema

How do I consolidate Claude Code project data after changing elpaca profiles?▼

To consolidate Claude Code project data, use a migration script that automatically discovers projects in `~/.claude/projects/` and performs a non-destructive merge of sessions, memory, and subagents into the new elpaca profile directory.

Why do I lose Claude Code session and memory data when updating elpaca profiles?▼

Session and memory data is lost during elpaca profile updates because the new profile directory structure does not automatically inherit the old project data. A profile migration process is required to copy and merge the files into the new profile.

Does Claude Code profile migration overwrite existing project trust entries?▼

No, Claude Code profile migration performs a non-destructive merge. It copies project trust entries from `~/.claude.json` and transfers session files without overwriting any existing data already present in the target elpaca profile.

Can I automatically detect the new elpaca profile for Claude Code data migration?▼

Yes, the migration process intelligently determines the new elpaca profile automatically if it is not explicitly provided. It scans elpaca directory patterns to identify the correct target profile for your Claude Code project data.

What is the best way to migrate Claude Code projects without re-authorization prompts?▼

The best way to prevent re-authorization prompts is to use a non-destructive migration that copies project trust entries from `~/.claude.json` alongside your session and memory data directly into the new elpaca profile directory.

How to move Claude Code subagent data across elpaca profile versions?▼

To move subagent data across elpaca profile versions, run a consolidation script that identifies all Claude Code projects and performs a non-destructive merge of subagent files, memory, and sessions into the newly detected profile directory.