> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/organizations/move-resources.md).

# Move resources between organizations

Transfer a project, grid or server to another organization from the portal.

An admin of both organizations can move a project, grid or server in the portal. The move dialog lists only organizations where you're an admin, previews what will move, identifies blockers and asks you to type the resource's name to confirm.

| Resource | Where to start                                      | What must be true                                                                                                                                  |
| -------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project  | Its card menu on Projects → **Move to Another Org** | No app outside the project uses a grid that moves with it, running or stopped, and the destination can use every other grid the project's apps use |
| Grid     | The grid's **Settings** → **Move to Another Org**   | No app outside the destination organization uses the grid, and the grid doesn't rent marketplace machines                                          |
| Server   | The server's actions menu → **Move to another org** | The server is not in a grid and isn't listed on the marketplace                                                                                    |

Any move also waits while either organization is frozen, while another move out of the source organization is unfinished, and, for grids and servers, while the source organization has a server order in progress.

## Review what moves

A project moves with its apps, the grids its apps run on, and the source organization's servers in those grids. A grid moves with the source organization's servers in it. The destination organization takes responsibility for the moved resources and pays for the servers from the move onward. Review the dialog's complete resource list and warnings before confirming.

* **Volumes and custom domains** stay with their apps, data and certificates included.
* **GitHub connections** the moved apps build through are copied to the destination; the source keeps its own.
* **Access** moves with the resources. Source-organization people who aren't in the destination lose access to moved grids, and creators who aren't in the destination lose access to what they created. The dialog warns about both.
* **API keys** limited to a moved project now reach the destination organization.
* **SSH keys** of the source organization come off the moved servers.

If either organization requires SSO, the browser session must be allowed into it before moving resources.

The move controls remain visible when a move is blocked; open the dialog to see why. Resolve the listed blockers and preview the move again. If the resource set has changed since the preview, Kinesis asks you to review it again.

Both organizations' audit logs record the move. If a move stops partway through, use **Finish the move** to complete it rather than starting a different transfer.

## Apps within one organization

Moving an app between projects in the **same** organization is a separate operation. It is available through the app's move flow, REST `POST /projects/{projectId}/apps/{appId}/move`, or MCP `move_app`. It does not transfer the app to another organization.

Cross-organization moves use the portal; they are not public REST or MCP operations. Merging entire organizations remains support-assisted. [Contact support](https://docs.kinesis.network/support.md) for a merge or a move that cannot be completed through the dialog.


---

# 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.kinesis.network/organizations/move-resources.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.
