← Back to Blog
February 9, 2026

SaveState v0.7.0: Your AI Context Is Finally Portable

The Migration Wizard is here. Extract everything from ChatGPT, load it into Claude, and switch platforms without starting over.

You've spent months training your AI. Custom instructions tuned just right. Memories accumulated from hundreds of conversations. Files uploaded, workflows established, maybe even a few custom GPTs built. It all adds up to something valuable.

Then you want to try Claude. Or your team switches platforms. Or OpenAI changes something you don't like.

And you realize: none of it is portable.

Your AI context is locked inside one platform. Switch, and you start over. That's the problem SaveState v0.7.0 solves.

Introducing the Migration Wizard

The Migration Wizard is our biggest feature since launch. It's a complete system for moving your AI identity between platforms — not just backing up, but actually transforming your context to work natively on the target platform.

Today we're shipping the ChatGPT → Claude path, with Claude → ChatGPT coming in v0.8.

Here's what you get:

  • ChatGPT Extractor — Pulls your custom instructions, memories, conversation history, uploaded files, and custom GPTs
  • Claude Loader — Transforms and loads everything into Claude Projects with proper system prompts and knowledge docs
  • Transform Rules Engine — Smart bidirectional transformations that handle character limits, format differences, and platform-specific features

The Architecture: Extract → Transform → Load

Migration isn't a simple copy-paste. ChatGPT and Claude structure context differently. Custom instructions have different character limits. Memory formats don't map 1:1. Files need to be reorganized.

That's why we built a three-phase architecture:

Extract pulls everything from your source platform into a normalized intermediate format. Every piece of context gets catalogued and validated.

Transform applies platform-specific rules. ChatGPT's 8k character custom instructions get intelligently condensed for Claude's limits. Memories become knowledge documents. Conversation history gets reformatted.

Load pushes the transformed data into your target platform, creating projects, uploading files, and setting up system prompts.

Before any migration runs, you get a compatibility report showing exactly what will transfer, what needs transformation, and anything that can't migrate. No surprises.

See It in Action

Migration is one command:

# Migrate everything from ChatGPT to Claude
savestate migrate --from chatgpt --to claude

# Check compatibility first (recommended)
savestate migrate --from chatgpt --to claude --dry-run

# Resume an interrupted migration
savestate migrate --resume

The dry-run shows you exactly what will happen:

$ savestate migrate --from chatgpt --to claude --dry-run

Migration Compatibility Report
══════════════════════════════════════════════════════

Source: ChatGPT (user@example.com)
Target: Claude (user@example.com)

✓ Custom Instructions     → Claude System Prompt (needs condensing: 8,412 → 4,000 chars)
✓ Memories (47 items)     → Knowledge Documents
✓ Conversations (312)     → Exportable (last 90 days)
✓ Uploaded Files (23)     → Project Knowledge (18.4 MB)
✓ Custom GPTs (4)         → Claude Projects

⚠ Limitations:
  - GPT actions/plugins have no Claude equivalent
  - Some DALL-E image prompts will be text-only

Ready to migrate. Run without --dry-run to proceed.

Built for Reality: Checkpoints & Rollback

Migrations can fail. Networks drop, APIs timeout, rate limits hit. We've all been there.

That's why every migration creates checkpoints. If something fails at step 47 of 312, you don't start over — you run savestate migrate --resume and pick up where you left off. Every file, every memory, every conversation gets checkpointed.

And if a migration completes but something's wrong? Rollback support lets you undo and try again. We snapshot the target platform's state before loading, so you can always get back to where you started.

Security First

Your AI context contains sensitive information. Conversations about work, personal preferences, maybe proprietary code. We don't take that lightly.

v0.7.0 includes path traversal hardening throughout the migration pipeline. All file operations are sandboxed. Archive extraction is validated. Nothing can escape the migration directory.

And as always, everything is encrypted with AES-256-GCM before it touches any storage. Your passphrase never leaves your machine.

What's Next

v0.7.0 ships the ChatGPT → Claude path. Here's the roadmap:

  • v0.8 — Claude → ChatGPT (the reverse path)
  • v0.9 — Gemini support (both directions)
  • v1.0 — GPT-4o, Copilot, and full platform matrix

We're building toward a world where your AI context is truly yours. Platform-agnostic. Portable. Protected.

Try It

# Install or upgrade
npm install -g @savestate/cli@latest

# Verify installation
savestate --version

# Run your first migration
savestate migrate --from chatgpt --to claude --dry-run

159 tests passing. Production ready. Your AI context doesn't have to be a hostage anymore.

Get SaveState →

Questions? Feature requests? Open an issue on GitHub or reach out at hello@savestate.dev.