OpenAI to Claude Migration Kit

In February 2026, Anthropic drew a line.

The Department of Defense wanted unrestricted access to Claude for any lawful use—including mass surveillance and fully autonomous weapons. Anthropic said no. OpenAI said yes.

If you're reading this, that distinction matters to you.

And if it matters to you, you're probably also sitting with a practical reality: you built something in ChatGPT. Custom instructions. A personalized AI assistant. Workflows that actually work. Prompts you've refined over months or years.

Moving on principle is one thing. Moving without losing everything you built is another.

That's what this kit is for.

What the Migration Kit Does:

The OpenAI to Claude Migration Kit walks you through three things:

First: Running extraction prompts inside ChatGPT to capture everything you've built there—your voice, your frameworks, your workflows, your custom GPT configurations—before you close the door.

Second: Setting up your new home base in Claude using Projects. The architecture Claude was actually designed around, which is more flexible and more powerful for ongoing work than anything ChatGPT offered.

Third: Rebuilding your personalized AI assistant in Claude so it knows you the same way ChatGPT did. Your voice. Your audience. How you think. How you work.

You're not starting over. You're moving. (Which still sucks, but I'm bringing pizza.)

What's Included:

A complete step-by-step migration guide covering:

• Every extraction prompt you need to pull your custom instructions, voice, frameworks, audience descriptions, and workflows out of ChatGPT before you leave
• A direct mapping of ChatGPT to Claude
• Full setup instructions for Claude Projects: what to put in them, how to structure them, how to upload knowledge files
• Orientation prompts for calibrating Claude to your voice and work style
• Honest guidance on what migrates cleanly, what needs adjustment, and what requires separate scoping
• A note on what to do if ChatGPT tries to talk you out of leaving (it happens; here's how to handle it)

Budget 2–3 hours for a thorough migration, or 45 minutes if you're focused on transferring your AI assistant only.

Who This Is For:

You're a business owner, consultant, or creator who has been using ChatGPT seriously—not casually. You've built real infrastructure there: custom instructions, a configured assistant, workflows that reflect how you actually think and work.

You've decided to move to Claude. Now you want to do it right.

This kit is not for people who used ChatGPT occasionally for one-off tasks. It's for people who built something there and want to bring it with them.

What This Is Not:

This is not a beginner's guide to AI. It assumes you already know how to work with these tools.

It's also not a technical migration for API integrations or complex GPT Actions. If you've built automated workflows connected to ChatGPT at the infrastructure level, that's a different scope of work—and one worth scoping properly. The kit includes a note on how to approach that.

What this covers is the 80% that migrates cleanly through prompts and Projects. For most serious ChatGPT users, that's everything that matters.

A Note on Why This Exists:

I've been writing about AI infrastructure and protection frameworks for years. When the OpenAI/DoD situation broke, I knew two things immediately: a lot of people would decide to leave, and most of them would do it badly—losing months of work because there was no systematic process for the transition.

This kit is that process. I wrote it because it needed to exist, and because the people who are leaving on principle deserve a migration that honors what they built.

Immediate digital delivery. Yours to use, update, and reference as Claude evolves.

Questions:

Does this require any technical knowledge? No API access, no export tools, no technical setup. Everything in Part 1 runs through a regular ChatGPT conversation. Everything in Part 2 runs through claude.ai.

What if I don't have a custom GPT? The kit still covers you. Custom GPTs are one component—the core migration (custom instructions, personalized assistant, workflows) applies whether or not you've built GPTs.

What format is this? A PDF delivered immediately via Payhip.

What if Claude changes how Projects work? The methodology is platform-agnostic enough to adapt. And this is a Library of Briar product—if something significant changes, I update the kit.