When you join a team or an organization, your content stays in your personal workspace. You can then move it to the workspace of your choice: each item changes place, without a copy, and stays yours.
Who can move whatLink to the Who can move what section
- You move content from a workspace you own, usually your personal workspace.
- You move it to a workspace where you are an active member.
- You only move your own content.
- Content cannot leave a managed organization.
Move everythingLink to the Move everything section
- Open “Settings” › “Data and privacy”.
- In the “Move to another workspace” section, on the “Move to organization” row, click “Move…”.
- Choose the destination in “Move to”.
- Read the preview: “What will move” counts the chats, projects, files and the rest; “Stays in” lists what cannot move, with the reason; “Good to know” sums up what changes.
- Click “Move”. The progress is shown (“… of … moved”).
If you close the window during the move, Moon AI asks “Stop the move?”: the batch in progress finishes, and what has already moved stays moved. If the move did not finish, run it again: it picks up where it stopped, without moving anything twice.
Move a chat or a projectLink to the Move a chat or a project section
- In the ⋯ menu of a chat or a project, choose “Move to workspace”.
- Choose the destination, read the preview, then click “Move”.
A chat moves with the files, images and routines it uses. A project moves with its chats, its instructions and its sources. A chat moved on its own leaves its project.
This entry only appears if you own the open workspace and are a member of at least one other workspace.
What moves and what staysLink to the What moves and what stays section
| Item | What happens |
|---|---|
| Chats, with their files, artifacts and routines | They move. |
| Projects and Library folders | They move. A name already taken at the destination gets the suffix (déplacé) (“moved”). |
| Files, knowledge bases, notes, prompts | They move and become private again if they were shared. |
| Memories, personal skills, connectors, MCP servers | They move, unless they are duplicates, the name is already taken or the feature is turned off at the destination. |
| Private agents | They are not tied to any workspace: they already follow you. An agent shared with the old workspace becomes private again. |
| Public chat links | Kept if the destination allows public links, removed otherwise. |
| Shares with the old workspace | Removed. |
| Routines | They follow their chat, and are paused if the destination does not allow routines. |
| Developer API balance, subscription, invoices | They stay: they belong to the workspace. |
Why an item staysLink to the Why an item stays section
The preview gives a reason for each item that stays, for example:
- a messaging link (Telegram…) or an agent trigger uses the chat;
- an action is waiting for your decision, or a deep research is in progress;
- the organization has turned off the feature or file uploads, or the file does not meet its size or type rules;
- your storage limit or your plan’s limit would be exceeded at the destination;
- the same item already exists at the destination;
- a knowledge base shared with other people stays where it is;
- the chat is older than the organization’s retention period, and would be deleted that same night.
What does not move stays in your personal workspace: you can try again later.