After the initial hype, ChatGPT started becoming part of some of my daily routines. It would start with the occasional quick question, but before long I started using it to clean up messy notes, to make sense of complex research, and to brainstorm design ideas. I didn’t think much about it, ChatGPT just became the default when I needed a second brain.

Enter Claude. I started experimenting with it after reading about it everywhere I turned online. At first, I was just giving it a test run and wanted to see how it compared to the tasks I use ChatGPT for. But after using both side by side for a while, I found myself reaching more for Claude, especially when working with longer documents or more complex projects.

Eventually the shift happened, and it only made sense to get my data from ChatGPT into Claude if I wanted to personalize it for my use cases.

Why I started shifting away from ChatGPT

Claude is just a better fit

ChatGPT was the tool I opened by default for brainstorming design projects and research. It’s really good for making sense of disorganized documents or long blocks of text, especially once you’ve personalized it to adopt a custom tone. It worked well for a long time, but as I started leaning more into AI for UI design experimentation, ChatGPT had too much friction. I was usually stuck describing my concepts and asking for suggestions, but then translating those ideas into something visual with a different tool.

Claude completely changed how I approach my design studies. For starters, Claude has a larger context window with up to 200,000 tokens, which is significantly more than ChatGPT’s 128,000 tokens. It also supports a wider range of file types for uploading and analyzing, with more advanced OCR capabilities, too. Moreover, it’s more consistent with long conversations and doesn’t forget the context as often as ChatGPT does in long chats.

But the thing that truly sold me was Artifacts. This feature is like a contained window for projects you want to work on without cluttering up the rest of your chats. Claude offers Artifacts templates for writing, coding, website designing, and more, and you can also create your own. This is the feature that I use to create interactive prototypes for my UI designs (for free), also referred to as vibe-coding. ChatGPT can’t directly render prototypes the same way, largely because Claude was built with stronger coding abilities.

So it’s not one specific feature that made me switch, but all of these benefits combined just makes Claude a better fit for how I work. Plus, it keeps the whole process contained in one tool so I don’t have to switch to something else for prototype visualization.

How I migrated my ChatGPT data to Claude

Claude makes it dead simple

The first thing I did before migrating my data was reviewing my ChatGPT personalization settings. It’s been a while since I’ve updated them, so I wanted to make sure all the context was current and accurate, plus check that it didn’t store anything irrelevant from random chats. To transfer the data, I headed to the Claude Import Memory feature, which you will find in the settings, and it’s available to all free users now too.

This feature is basically just a template prompt that you add to your AI provider to extract preferences and context from what it’s learned about you. You’ll find it by going to Settings -> Capabilities -> Memory, then hit Start Import and copy the prompt as instructed. In ChatGPT, or whichever AI you use, start a fresh chat and paste the prompt.

ChatGPT gave me the results in a code block as requested, which makes it easy to paste back into Claude’s Import Memory feature in the “Paste results” box. Claude will then update its memory and give you the option to see what it learned about you by redirecting you to a new chat.

Things to keep in mind before migrating to Claude

Set yourself up for success

Before copying Claude’s prompt into ChatGPT, I recommend removing or adding anything you feel is necessary. Same thing with the response ChatGPT gives you: read it before copying it over in case it contains anything irrelevant or incorrect. This does, in a way, defeat the purpose of having a long prompt that does all the work for you automatically, but it ensures that you start off on the right foot.

Another thing to keep in mind is that Claude won’t necessarily respond the same way chatGPT does, even with the same preferences. So your first couple of chats might need some experimentation. And lastly, I don’t recommend deleting your ChatGPT memories just yet - keeping them makes it easier to fall back on something familiar in case you run into a task that worked better in ChatGPT before.

The switch paid off

Switching my workflow from ChatGPT to Claude was just the right move. It gives me more to work with in the chats so I can explore ideas more freely, and its Artifacts feature is perfect for my design projects. The only hiccup was that ChatGPT already held so many of my preferences. But Claude made it surprisingly simple to bring everything over and pick up right where I left off.