Moving day: the Claude team account migration checklist

We just moved Ample from personal Claude accounts onto a Team plan. Like any move, we found out what we forgot to pack after the truck had already left. This is the packing list so you don't have to learn it the way I did.

Note: this was authored in August 2026 and is subject to change dramatically in six months… or tomorrow.

The one thing to remember

Export everything to plain text files (I suggest markdown or .md files) on your hard drive BEFORE you accept the workspace invite. Migration is one-way. What doesn't come with you is gone. No takebacksies.

If you read nothing else, do this: open every Cowork project you have and ask Claude to write a context.md file capturing the project's purpose, decisions, and memory. I didn't do this, and I had to rebuild every one of my Cowork projects from scratch. Whoops.

Why we moved

When we adopted AI at Ample, we let it be the wild west on purpose. Everyone picked their own tool, built their own workflows. That was right for the experimentation phase. Now that workflows have settled, we've consolidated onto team accounts so we can actually share projects and knowledge across the team instead of trapping it in personal subscriptions. Right call, bumpy move.

Before you accept the invite (musts)

1. Run your data export. Settings → Privacy (web or desktop only — you can't export from mobile).
2. Generate a context.md in every Cowork project (prompt below). Confirm the file is actually on disk.
3. Save every custom skill as a ZIP. No migration path exists for skills, period. Lost the folder? Ask Claude to output the skill's full contents and save it locally.
4. Save your apps as projects or HTML. Download the HTML file for every app you've built to your hard drive. Published artifacts die in migration and publishing doesn't exist on Team plans.

Before you accept the invite (suggested)

1. Screenshot your scheduled tasks and automations (neither platform moves them).
2. List your connectors (Drive, Slack, GitHub — all auths get revoked).
3. Accept that your public share links are about to die. Re-share anything important another way.

The Cowork prompt

Paste this into each Cowork project:

"Generate a context.md file for this project that captures everything a fresh Claude instance would need to continue this work: the project's purpose, key decisions made, important context from our conversations, current state, and anything stored in memory. Save it to the project folder."

The files Cowork made are already safe on your hard drive. The context, memory, and chats are not. And here's the kicker: the official export won't save you either. It exports context for chat-based projects only — nothing comes out for Cowork projects. I learned this the hard way so you don't have to. (You're welcome.)

What transfers vs. what doesn't

Per the official migration flow: chats, projects, files, and memory come over. Cowork session history, skills, connectors, and share links do not.

Real talk: the migration is permanent. No undo, no moving back, no exceptions.

After you're in

1. Verify your chats and projects actually arrived before you assume success.
2. Rebuild Cowork projects: new project → point it at your existing local folder → feed it your context.md.
3. Re-auth connectors, recreate scheduled tasks, re-upload skill ZIPs (Customize → Skills).
4. Publish team-wide skills to your org's skill directory — this is the payoff! Skills stop living in one person's account and become something the whole team can install.
5. Test memory: ask something Claude "knew" about you before. If it's blank, paste your exported memory summary back in.

How sharing works once you're all in (not how you think)

Sharing on the Team plan surprised me more than the migration did. I assumed sharing worked like a shared Google Drive folder — hand someone the folder, they get everything in it. Nope. Here's what's actually true:

• Chats and projects share between teammates. Cowork sessions never do.
• Sharing a project does NOT share your chats inside it. Your teammate gets the project shell — instructions and knowledge files — but none of your conversations.
• Shared chats are read-only. Your teammate can read one, but they can't continue it and can't nest it into a project on their side. I checked. Twice.
• There's no "here's my project and everything in it" button. Full stop.
• You can share skills at the organization level. (The first one that got installed in our org was the I have ADHD skill which helps make Claude’s output more concise.)

So the habit that works: when a chat produces a decision worth keeping, distill it into a doc and drop it in the project knowledge. That's the only version your teammates can actually build on. Chats are ephemeral; project knowledge is where decisions go to live.

Here's your checklist:

• What would I lose if my account vanished tomorrow? (Export it)
• What does my team need that's trapped in my chats? (Distill it)
• What's living only in Cowork? (context.md it)

Making a move like this at your company? I've got the bruises and the checklist. Book a call with me and let's chat.