> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-transfer-a-project.md).

# How do I transfer a project?

To transfer a project to another workspace, you can:

1. Right-click on the [canvas](/overview/user-interfaces/map-editor.md#canvas)
2. Select **Project**
3. Select **Transfer project**

Alternatively, you can:

1. Open the [project settings menu](/overview/user-interfaces/settings.md#project-settings)
2. Select **Admin** from the sidebar
3. Select **Transfer project**

## Caveats when transferring projects

To transfer a project into a Pro workspace, you first need to be [added as an owner](/guides/pro-workspaces.md#add-users-to-a-pro-workspace) of the Pro workspace (if you created the Pro workspace, you are an owner by default).

If you see an "Unable to transfer project" error after trying to transfer a project, here is how you can troubleshoot:

1. Ensure that the recipient (the workspace you're transferring to) does not have a project with the same name. If they do have a project with the same name, rename one of the projects, and try transferring again.
2. If you are transferring a private project, make sure that the recipient has added a credit card in their billing settings, and that they have not met or exceeded their private project limit (annual plans only).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kumu.io/frequently-asked-questions/how-do-i-transfer-a-project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.