# Move a project to another workspace

> Move a project with its files, chats and Cloud computers into another workspace, and what changes for access, folders, billing and domains.
> Source: https://playcode.io/docs/build/move-a-project - last reviewed 2026-10-09.

Move a project when it belongs in another workspace: its files, chats and Cloud computers go with it, and nothing has to be rebuilt. Open the project's menu in the left panel and choose **Move to workspace**.

## Do it yourself

1. In the left panel, point at the project and choose ⋯ (**More**), or right-click it.
2. Choose **Move to workspace**.
3. Choose the destination. The note under the list says what changes: "Members of" the workspace "will get access to this project, including its chats and data", or, for your Personal workspace, "The project becomes private. Workspace members will lose access."
4. Choose **Move**. The app says "Project moved to" and the workspace name, and the project leaves the current list.
5. Open the workspace menu at the top of the left panel and switch to the destination to find the project there.

What happens in the move:

| | After the move |
|---|---|
| Files, chats and their attachments, Cloud computers | Move with the project, in one step |
| Access | Into a team workspace: **Everyone at** the new workspace gets **Can edit**. Into your Personal workspace: members of the old workspace lose access. People you invited directly keep theirs |
| Folder | The project leaves its folder, because folders belong to a workspace |
| Billing | From now on, the new workspace pays for the agent's work and the Cloud computers, and its plan's Cloud app limit applies. Past usage stays with the old workspace |
| Domains | A domain in the old workspace's **Domains** stays there. If it was connected to this project, Playcode disconnects it, and it stops opening the site |
| Published site | Keeps its Playcode address |

> [!IMPORTANT]
> A domain does not move with a project. When a project and its domain end up in different workspaces, Playcode disconnects the domain. To use the domain with the moved project, move the domain to the same workspace (in **Settings**, **Domains**, open the domain and choose **Move to another workspace**; this needs an Admin of the destination workspace), then connect it to the project again. See [Connect a domain you own](/docs/publish/connect-a-domain).

## If it doesn't work

### Move to workspace is missing

The item shows only to the project's creator, only when they belong to more than one workspace, and not for archived projects. Restore an archived project first: see [Projects and folders](/docs/build/projects-and-folders).

### "Failed to move project: ..."

The text after "Failed to move project:" says why. If it says "you are not a member of workspace", join that workspace first.

## Limits

- In the app, only the project's creator can move it.
- The agent cannot move projects for you.
- Moving a project into a team workspace gives its members the project's chats and data. Check the **Everyone at** row in the **Share** tab right after the move if the project should stay narrower.