Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
Owned by Ryan
Weekly builds and game nights you and your kid actually do together. 3D printing, LEGO, STEM, co-op gaming. Free, follow along at home.
Blueprint Automation Systems
43 members • Free
AI Automation Society
456.1k members • Free
The Relationship Chef
111 members • Free
Dojo Leadership Playbook
3 members • Free
U Can Build This
327 members • $7/month
THE SKOOL HUB
5.6k members • Free
Skoolers
159.7k members • Free
11 contributions to Blueprint Automation Systems
2d •
Moving from Chat GPT to Claude
Not sure if this is the right place to ask, but I’m wondering if anyone knows of any good videos, guides, or instructions on how to move as much as possible from ChatGPT over to Claude. I’m currently using ChatGPT to run my business and have built up quite a bit over time — projects, custom instructions, past chats, memory/context, workflows, and other information. I’d like to start using Claude also to help run my business, but I really don’t want to start over from a blank slate. I’ve searched YouTube, but most of what I’ve found only covers basic memory or copying a few prompts over. I’m looking for something more comprehensive that explains how to transfer or recreate the overall setup. Has anyone done this successfully? If so, what was the best process, and are there any good videos or guides you would recommend?
1 like • 2d
@Sean McNeely fair warning, this one's long. Paul already gave you the short version and he's right: if you've got a second brain, point Claude at it and let it cook. If you don't, this is how I'd build one, and I'd rather hand you the actual steps than a tidy paragraph that leaves you nothing to do. Sorry for the wall of text... First, the reason you can't find a good video on this. Most people are asking the wrong question. "How do I move ChatGPT to Claude" has no clean answer. ChatGPT's memory isn't a file you can take with you, it's a summary that lives inside their app, with your rules, your business facts, and years of one-off chats all mashed together. What actually works is: You move ChatGPT into local files you own, in a folder on your own computer not in their software. Then you point Claude, ChatGPT, Grok, or whatever you want to use in the future at the folder. After that you never do this again, because the next tool that comes out just gets pointed at the same folder (You can also store/backup/mirror your second brain in cloud storage like Gsuite, dropbox, etc so you can get access on the go) Here's how I'd do it, in order. STEP 1. GET EVERYTHING OUT OF CHATGPT AND INTO TEXT FILES (about an hour) Make a folder on your desktop called chatgpt-export. Everything below goes in there as a plain text file. Notepad is fine. One file per item, named so you know what it is. Nothing in ChatGPT lives in one place, so work the list: - Saved memories: Settings > Personalization > Manage memories. There's no export button. Select the whole list, paste it into a new text file, save it as memories.txt. Or open a new chat and ask ChatGPT to write out every memory it has about you, word for word, and paste that instead. (Claude's importer hands you an exact prompt for this, more on that below.) - Custom instructions: Settings > Personalization > Custom instructions. Copy both boxes into custom-instructions.txt. - Projects: open each one. Copy the project instructions into a file named for the project, like project-proposals.txt, and re-download any files you uploaded into a subfolder with the same name. Then, inside the project, ask it to summarize everything it knows about that project, the decisions you made, and where you left off. Paste that into the same file. Project instructions are NOT in the data export. Skip this and they're gone.
11d •
Your safety net was the credit card statement
Ryan's point in this clip rewired how I think about tool sprawl. Every piece of software that ever snuck into a business eventually surfaced on a statement. That was your safety net, and you didn't know it. Shadow AI is the first one with no bill, so the net catches nothing. • No admin console, it's not your account • No dashboard of who's using what • Nothing on your network when it's their phone 🎯 The one thing Your existing alarms all watch money and infrastructure. This uses neither. What was the last tool you discovered your team using without you? Tell that story below. 👇
0 likes • 10d
It's scary how many of my friends will say "oh yeah, my work hasn't really implemented AI yet, but I installed chatgpt to help me write emails all the time, it's great, but no one really knows, I just look really productive" Ask your team business owners!
Jun 23 •
New Classroom: What Is an AI Operating System?
Most people use AI like it's one magic app. You open a chatbot, ask it something, and the second you close the window it forgets who you are. Tomorrow you're back to re-explaining your whole business from scratch. Useful, sure. But it's not running anything. There's a better way to think about it, and it's the whole point of this new series. 🎯 The one thing An AI operating system isn't one app. It's a set of modules that share one brain and one brand, all driven from a single Command Center. The apps are the modules. The OS is what turns ten disconnected tools into one system that actually knows your business. I built mine with an AI coding assistant, one piece at a time, starting from nothing. No master plan, no computer science degree. In Episode 1 you get the mental model, a full card-by-card tour of my real Command Center, and the roadmap for how we build the whole thing together over this series. Here's the part most courses won't tell you: you don't need all of it. A contractor might just want his inbox triaged and his calendar under control. A creator might just want the editor and the shorts engine. A local shop might just want the social poster running so they post every day without thinking about it. It's modular on purpose. Build the piece that fixes your biggest headache first, add the next one when it starts to hurt. How the series works: 1. One module a week, built right along with me. 2. The lean what-and-why lives on YouTube. The full step-by-step build, every prompt, file, and template, lives here. 3. Once a week, Paul and I go live in here for a build session and Q&A. Ask us anything and watch us actually work. I'll announce days and times in the community. If you do one thing this week: 1. Watch Episode 1 and get the mental model down. Stop thinking "which app" and start thinking "which module." 2. Pick the one headache in your business that hurts the most right now. That's the piece we build first for you. 3. Drop it in the comments so I know where to point you as the series rolls out.
Poll
3 members have voted
2 likes • Jul 8
Hey everyone! Due to the holiday weekend and traveling with family, there is a gap in our posting schedule for the next classroom video. Our next video will be releasing next Tuesday for this series!
0 likes • 17d
@Ken Cason Thanks! It was great to get a chance of scenery (Massachusetts to California) and peel myself away from my screen for a week. Still playing catch up, but needed the unplug and family time.
Aug 9 •
AI OS Training
Hey all, just a quick note. I had to take off and travel for all of last week. I'm just getting back into town late tonight and will get back on creating more training videos for the AI OS series. Next episode I go over setting up your second brain! See you all soon!!
1
0
Jul 30 •
A Month of Work Done in Six Hours With AI
The AI OS payoff isn't gradual. It's sudden. I've been two months deep building context in Claude. Teaching it how I think, how I write, what my business looks like. Yesterday I was at my Academy for six hours running oversight for summer camp. Not at my desk. No big blocks of time. Just oversight. I walked out with roughly a month's worth of work done. That's not a coincidence. That's what happens when the AI actually knows your business. You stop explaining yourself every session. You stop correcting it constantly. It just moves with you. If you're still in that early phase where it feels like you're putting in more than you're getting out, that's exactly where I was six weeks ago. It's not broken. It hasn't clicked yet. What's one thing you're still doing manually that you wish Claude could just handle? Drop it below. I want to see if it maps to what we've already built out.
0 likes • Aug 1
@Paul DiRienzo yeah, building up that second brain pays off in the long run.
1-10 of 11
@ryan-morency-4219
Dad and co-creator behind The Bonding Blueprint. Building, gaming, and learning alongside my son through hands-on STEM projects.
Online now
Joined Apr 11, 2026
Boston Area, MA