[BUG] Conversations locked after moving personal account to Team org: "This conversation has moved to a view that isn't available here"
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Summary
This bug is doing serious damage to my business. After I moved my personal Claude account into our Team organisation, several of the conversations we work in every day were locked. Months of work, important client data and live processes are now frozen. That directly hits our ability to earn, pay our staff and cover our bills and our families' living costs. Each locked conversation shows "This conversation has moved to a view that isn't available here", and every message fails with "Failed to send". My previous support requests to Anthropic went unanswered for over three weeks, so I can't rely on the normal support queue for this.
Actual: the old messages are visible, but the message box is locked and every send fails. The account menu has no switch back to a personal account.
What Should Happen?
The conversations open and accept messages, or I'm told clearly where they moved to.
Ask: restore the conversations or recover their full history, and link this report to support conversation ID 215476168475049.
Error Messages/Logs
This conversation has moved to a view that isn't available here.
Failed to sendSteps to Reproduce
- Have active conversations in a personal account. These used Cowork tools: email, browser and files.
- Move the personal account into a Team organisation.
- Open those conversations in the Team organisation.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
Worked before the personal-to-Team account move on 29 September 2026
Claude Code Version
Not the CLI: claude.ai in Chrome on macOS, and the Claude desktop app for Mac (current version)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
Environment
- Plan: Team, moved from a personal plan
- Affected: claude.ai in Chrome on macOS, and the Claude desktop app for Mac
- Started: 29 September 2026, right after the account move. It happens every time.
Already tried
- Switching between the Chat, Code and Cowork views
- Quitting and reopening the desktop app
- Requesting an organisation data export
- Support conversation ID 215476168475049. It was passed to a human on 30 September and I was told the reply won't be same-day.
Possible cause (a guess): Team organisations may not have the merged Chat and Cowork view from the 16 September update yet, so conversations created in that view can't load.
3 Comments
Update with evidence for engineers: the conversation data is intact and still readable through the claude.ai web API under the Team org (the main affected chat returns all 120 messages). What looks like the trigger: every locked conversation I've checked has
"workspace_upgraded": truein its conversation record. 34 of my recent conversations carry that flag. So it looks like conversations upgraded to the new merged Chat/Cowork workspace before the move can't be rendered or continued in a Team org that doesn't have that view yet.The personal account was closed by the move (per the "We moved your chats and projects" email on 29 Sept), so there is no way back to the original view. Please either enable the view for this Team org or allow these conversations to be continued. Support conversation ID 215476168475049.
We are experiencing exactly the same problem. After moving a personal Claude account into our Team organisation, conversations that were created in the merged Chat/Cowork view are locked ("This conversation has moved to a view that isn't available here") and cannot be continued.
This is business-critical for us
Same story here with a migrated account, and it's a major issue for in-progress work.