the Claude Migration Kit I wish I had
Are you on Claude yet!?
If you’ve been wanting to move over to Claude…
But feeling overwhelmed, stuck, or intimidated, and don’t know where to start -- keep reading.
I’ve put together a Claude migration kit
This week’s edition of the Narrative –
The secret shift that makes AI adoption actually stick
Why you need a Pioneer / AI build day
Claude config resources you can start using today
Look, I get it.
You finally got the hang of prompting. You have your workflows. The last thing you want is to learn another thing. Again.
But you keep hearing that Claude Cowork and Claude Code -- is genuinely some next level sh*t.
They’re not wrong.
Agentic AI is a category leap.
And no foundation model makes it easier than Claude.
Claude does enterprise knowledge work, across your files, projects, and spreadsheets. Claude takes you from prompts to agents that can work on your behalf. Even while you sleep.
The performance gap versus other LLMs is not incremental. It’s a paradigm shift.
And Claude CoWork is specifically for non-technical people.
The Hidden Unlocks for Building in AI
A month ago, I started something new.
No meeting Tuesdays.
Zero deadlines. Zero interrupts. Zero urgency. Non-negotiable.
I call it my Pioneer / AI Build Day. A time to “Think, build, ship.” Rinse and repeat.
First Tuesday, I ported my entire working memory into Claude, installed CoWork, and built three automations before dinner. I then looked up and it was 11pm. That’s what happens when you stop squeezing AI experimentation into 27-minute blocks between meetings.
My #1 job is to automate my job, so I can focus on the highest-order value creation.
That’s the whole day. And it’s become the most important day of my week.
Here’s what I didn’t expect.
My Build Day isn’t about productivity. It’s about identity.
Many of the executives and organizations I work with have done the responsible thing. Bought the licenses. Set up the pilots. Run the trainings. Six weeks later, almost nothing changed.
The team has access to everything and is using almost none of it.
Nobody resists AI. They resist losing their sense of identity in the process.
If AI does all the work, then what is my role or job?
The problem isn’t tools. It’s that people don’t yet see themselves as a person who builds in AI.
Builders have power. Builders architect. Builders create. Builders lead. Builders have options.
And you can’t close that gap in 23-minute work blocks. Or even 83-minute blocks.
As a leader, you probably feel that you are in too many meetings.
You don’t have time to breathe, think, or even go to the bathroom. Many others on your team feel the same.
Your nervous system is the obstacle.
Back-to-back meetings. Slack pings. Context switching all day. That’s a cortisol state. Fight, flight, freeze. A nervous system in hypervigilance can’t learn. You can’t experiment, play, or build new behavior in triage mode. You default to what you already know.
A new way of thinking requires a new way of working.
You can’t adopt a new way of thinking while your body is braced for the next interruption. And neither can your team.
A new way of working requires something most organizations haven’t considered:
A full, uninterrupted day to build.
When someone spends the day building with AI...
Not attending a demo, not watching a tutorial, but making something that matters to their actual work, something shifts. They stop seeing AI as a threat to their role and start seeing it as a lever for their role.
Not because you told them to. Because they experienced it.
You solve the identity problem through the behavior. Not the other way around.
The VC Vinod Khosla said it plainly this past week: AI is already redefining knowledge work at a structural level.
This isn’t just a headcount story. It’s a fundamental redefinition of what the modern org chart looks like. 30% of knowledge worker headcount will compress over the next 12 to 24 months. That’s not a prediction from a blowhard futurist on LinkedIn. It’s what I’m seeing in every organization I work with. Early stage, growth, enterprise. Same hard knocks reality.
Everyone needs to upgrade their thinking and their workflow. From CEOs and VPs to front-line employees.
The best service you can do for your people right now is to give them the mindset, tools, and playbooks for playing a bigger game. This is the principled move -- whether they level up inside your organization or are set up to thrive and adapt on a new path.
“Shipping in AI” becomes the leading indicator.
Ask yourself: Does your team have protected time to actually build with AI -- or are they just trained on it?
If the answer is trained, you don’t have an adoption problem. You have an architecture problem.
Training gives people information.
Building gives people identity, agency, and dopamine reward.
The Claude Migration Kit I wish I had earlier
Here’s a quick set of resources I’ve put together.
Set aside an AI build day and start going through these steps. You will quickly see compounding results. Feel free to share these with anyone looking to make the leap.
Step 1: Bring over your memory from ChatGPT, Gemini, CoPilot
Start here: claude.com/import-memory [30 min]
Want to go deeper and port your full memory into Claude, check out this Reddit walkthrough
Step 2: Install Claude CoWork in a day
Ruben Hassid: simple version gets you running in an afternoon [4 hours]
Ruben Hassid: intermediate version goes deeper if you want to build real workflows [1 day]
Charlie Gillis: another intermediate version to expand your depth and range [4 hours]
Step 3: Join an AI build community
Gen AI Circle -- where I go to install more advanced Claude Code playbooks [40 euros/month]
Mighty AI Lab -- great starter set of playbooks for SMBs and mid-market [$97/month]
That’s it. Block a day. Protect your nervous system.
Bring over your memory. Build something real and ship it. Identity shift follows behavior.
Dive in and let me know what you discover.
Michael
P.S. Know someone who could benefit from this Claude Migration Kit? Forward it to them.