Moving Personal Claude Work into a Company Workspace

Anthropic lets a person move a personal Claude account into a Team or Enterprise organization when both use the same email address. Chats, projects with their files and instructions, uploads and Claude memory come across; custom skills, connector sign-ins, published artifacts and public share links do not; and once content has moved it cannot be moved back. The company's job is to decide ownership and permissions first, tell each employee what will not transfer so they can save it, and then have them accept the invitation and choose "Bring your data with you." The source for every rule below is Anthropic's article on moving a personal account to a Team or Enterprise organization, as of October 2026.

Claude is Anthropic's AI assistant. The personal plans are Free, Pro and Max; the company plans are Claude Team (2 to 150 people) and Claude Enterprise. This is the support-led companion to Claude Pro vs Team, which covers why a business should own the workspace, and to Claude Team vs Enterprise, which covers the plan choice. Companies doing the same exercise with ChatGPT can follow moving personal ChatGPT use into a company workspace.

What should the company decide before anyone migrates?

1. The plan and its owners. A Primary Owner, at least one more Owner, and who approves connectors. On Team only Owners and Primary Owners can add custom connectors and enable the Microsoft 365 connector, per Anthropic's custom connectors article and its Microsoft 365 connector article, so migrating staff will be asking those people to re-enable what they used personally.
2. Domain capture and SSO. Claim the company domain so that accounts are created through the organization from now on and no new personal accounts appear on it. Both are in Team standard seats per the Team plan article.
3. Memory. Personal Claude memory moves unless the organization has memory turned off. Decide the organization setting first, or people will lose what they expected to keep.
4. Sharing policies. Project sharing roles, the skill library setting ("Requires review," "Open" or "Off") and whether peer skill sharing stays on. Migrated projects then get shared under these rules.
5. Merge or start fresh, per person. Someone whose personal account is mostly work history should merge. Someone who used it for personal matters, or who pasted client data they should not have, should either keep both accounts or delete the personal data rather than bring it into company records.
6. What the organization will see. Content that moves becomes organization content under the organization's terms. On Enterprise, the Compliance API exposes chat histories and file content to administrators, per the Enterprise plan article. Tell people this before they choose.

What moves and what does not?

Two of these catch people out. Share links sent to clients die at the moment of migration, so anyone who shared a chat externally needs to send the content another way first. And the skills a person wrote for themselves vanish from their account; the files they uploaded as a .zip are still on their computer if they kept them, and the organization owner can provision the useful ones centrally, which is the better home anyway.

How does the migration work, step by step?

1. Check the email address. The personal account must use the same address as the organization account. If an employee signed up with a personal address, there is nothing to merge; they start fresh in the organization and keep or close the old account separately.
2. Save what will not move. Copy the content of any published artifact, note every public share link and who has it, keep the .zip of each custom skill, and list the custom connectors and connected apps in use so they can be requested from the owner.
3. Finish or document running work. Desktop Cowork sessions stay on the machine, and Cowork cloud sessions and Claude Code cloud sessions (including scheduled tasks) do not transfer. Write down any scheduled task so it can be recreated in the organization.
4. Accept the invitation. On Team, the prompt to move appears when the person accepts the invitation, and a reminder banner follows for about seven days. On Enterprise there is no prompt: the person goes to Settings > Account > "Close your personal account."
5. Choose. "Keep both accounts," or "Use your organization account only," which then offers "Bring your data with you" (content moves, the personal account closes, and a Pro or Max subscription is cancelled and refunded pro rata) or "Delete your data." Once content has moved it cannot be moved back.
6. Handle the subscription refund. Direct purchases are refunded pro rata about 24 hours after cancellation and Google Play refunds automatically. Apple App Store subscriptions must be cancelled manually or, in Anthropic's words, "Apple keeps charging you"; Apple subscribers see only "Keep both accounts" until they cancel.
7. Reconnect under organization policy. Connectors the owner has enabled can be reconnected by the member; custom connectors are re-added by an owner if policy allows. Microsoft 365 needs the organization's Global Administrator consent to be in place.
8. Re-share projects. Migrated projects are re-shared with "Can view" or "Can edit" to the right colleagues, and the owner provisions any skill worth keeping.
9. Verify. The person opens three recent chats, two projects and their memory, and confirms the personal account shows as closed.

What about Max API credits and Enterprise domain claiming?

If someone on Max is moving, Team owners can claim that account's API credits after the Team plan has been active for seven days; Enterprise plans are not eligible for monthly API credits. On Enterprise, administrators can claim personal accounts that use the verified company domain, and those users get at least 30 days' notice to merge or start fresh. Merging is not offered when the organization runs the HIPAA-ready configuration or customer-managed encryption keys: those organizations cannot receive data from a personal account at all, so staff in a HIPAA-ready Enterprise start fresh by design.

How should an employee hand work over?

• Inventory. A list of projects by client or task, which ones should be shared and with whom, and which chats contain decisions worth keeping.
• Skills. The .zip files and a sentence on what each does, handed to the owner for provisioning.
• Connectors. Which connectors and connected apps were in use, so the owner can decide and the member can reconnect.
• Scheduled work. Any scheduled tasks or routines, recreated in the organization after the move.
• Memory review. A look at what Claude remembers, since it will now sit in the organization's account.
• Clean-up. Anything personal that should not come into company records gets deleted before the choice is made, or the person keeps both accounts.

What does NetSys do for a migration?

NetSys runs this as part of its Claude consulting service: the ownership and policy decisions above, SSO and domain capture, the connector approvals and Microsoft 365 consent, a per-person migration checklist, a short session for staff on the day, and verification afterwards. It is one part of a managed rollout under our AI services, and we have run a Microsoft Copilot and Claude rollout for a 25-employee company with usage policies, connector access controls and staff training. Administration afterwards, including offboarding, runs month to month.

Frequently asked questions

Can a personal Claude account be merged into a Team account?

Yes, when both use the same email address. On accepting the Team invitation the person can choose "Use your organization account only" and "Bring your data with you," which moves chats, projects, uploads and memory and closes the personal account.

What happens to a Pro or Max subscription?

It is cancelled and refunded pro rata when the data is brought across. Direct purchases are refunded about 24 hours after cancellation and Google Play automatically; Apple App Store subscriptions have to be cancelled by the user.

Do Claude skills transfer to the organization?

No. Anthropic says there is no migration path for skills. Keep the .zip files and have an owner provision the useful ones organization-wide.

Can data be moved back to a personal account later?

No. Anthropic's article says once content has been moved it cannot be moved back, which is why the per-person merge-or-keep-both decision matters.

Will the company see my personal chats after migration?

Migrated content becomes organization content under the organization's terms, and on Enterprise the Compliance API can expose chat histories and file content to administrators. Anyone who does not want personal history in company records should keep both accounts or choose "Delete your data."

Is migration available on a HIPAA-ready Enterprise plan?

No. HIPAA-ready and customer-managed-key Enterprise organizations cannot receive data from a personal account, and domain-claim merging is not offered to them. Staff start fresh.

Do public share links keep working?

No. Public chat share links stop working permanently at migration, and published artifacts do not move because publishing is not available on Team and Enterprise. Send that content another way before the move.

NetSys can plan and run the move from personal Claude accounts to a company workspace, with the policies set first and nothing lost that could have been saved. Request a Claude rollout review.