daBongo LMS AI Training Courses

← Back to Course

Your Persistent AI Brain – Memory, Context, and Continuity (Claude Edition)

Lesson 6: Backup, Portability, and Data Safety

Lesson Objectives

By the end of this lesson, students should be able to:

  • Distinguish between cloud-stored and locally-stored Claude memory components
  • Create a complete backup of their Claude memory setup
  • Restore their Claude memory setup on a new device
  • Know how to export conversation history from Claude
  • Evaluate and manage what long-term memory data they are comfortable keeping

Lesson Content

Know where your memory lives before you need to restore it.

Most users never think about their Claude memory setup until something breaks – a new computer, an account issue, or an unexpected reset. By then it is too late to back up what was lost. This lesson is the proactive version of that conversation.

The complete map: what lives where.

Cloud-stored (in your Anthropic account, accessible from any device):

  • Custom Instructions
  • Projects (instructions, uploaded files, conversation history)
  • Claude's built-in memory feature conversations and retained facts
  • All conversation history in Chat, Code, and Cowork

Locally-stored (on your specific device, requires manual backup):

  • CLAUDE.md files (in your project directories)
  • Auto-memory files (in your Claude configuration directory, typically at C:Users[username].claude on Windows or ~/.claude/ on Mac)
  • Settings files (Claude Code configuration in .claude/settings.json)
  • Any MCP server configurations

Backing up locally-stored components.

The single most important local backup is your Claude configuration directory (.claude/). This contains:

  • Your auto-memory files
  • Your MEMORY.md index
  • Claude Code settings and configurations
  • Project-specific memory

To back it up: copy the entire .claude/ directory to a backup location – an external drive, cloud storage (OneDrive, Google Drive, Dropbox), or a backup service. On Windows: C:Users[username].claude. On Mac: ~/.claude/

CLAUDE.md files live in your project directories. Back them up as part of your normal project file backup routine. If you use git for project version control, commit your CLAUDE.md files – they belong in version control alongside the project files they describe.

Backing up cloud-stored components.

Custom Instructions: copy them to a notes app or document. This takes thirty seconds and gives you a restore option if they are ever reset.

Projects: Anthropic does not currently offer a bulk export for Projects. For critical Projects, keep copies of your uploaded reference files in their source location (your own documents, not only in Claude). Treat Claude Projects as a working environment, not as the primary storage location for original files.

Conversation history: Claude allows you to export your conversation history from account settings. This produces a file containing all your conversations. Run this export periodically for any conversations you want to keep outside of Claude.

Restoring on a new device.

When you get a new computer or reinstall Claude:

  1. Install Claude Code
  2. Sign in to your account – Custom Instructions, Projects, and conversation history are automatically available (cloud-stored)
  3. Copy your .claude/ directory backup to the new computer's home directory – auto-memory, settings, and configurations are restored
  4. Restore CLAUDE.md files to their respective project directories
  5. Reconfigure any MCP servers (these are machine-specific)

Steps 1 and 2 take minutes. Steps 3-5 depend on how organized your backups are.

What to keep and what to clear.

Over time, your Claude memory setup accumulates. Periodically evaluate:

  • Auto-memory entries: remove stale or outdated entries
  • Project files: archive or delete Projects that are no longer active
  • Custom Instructions: update sections that no longer describe your current situation
  • Conversation history: Claude's history is comprehensive; decide what you want retained vs. cleared

Claude's account settings allow you to delete conversation history, clear memory feature entries, and modify what Claude retains. Review these settings periodically rather than letting memory accumulate indefinitely without assessment.

Data safety considerations.

Understand what Anthropic does with your data by reviewing their current privacy policy. Key considerations:

  • Conversation data may be used for model improvement unless you opt out (check current settings)
  • Enterprise plans typically offer stronger data protections than personal plans
  • Locally-stored files (CLAUDE.md, auto-memory) are under your complete control
  • If you use Claude for sensitive client work, verify your plan's data handling commitments

Enroll to continue this lesson.

The preview above shows the lesson objectives and opening lesson content. Enroll to view the full lesson, complete the practice work, and take the lesson quiz.

Log In / Create Account Back to Course

← Back to Course