Move a Project Between Organizations
You can move a project — together with everything inside it — from one organization to another, without redeploying anything.
What Moves
Moving a project takes its entire contents with it in a single step:
- All environments
- All applications
- All databases (PostgreSQL, MySQL, MariaDB, MongoDB, Redis)
- All Compose stacks
- All domains attached to those services
There's nothing to migrate piece by piece — the whole subtree follows the project automatically.
Your running services are not redeployed or restarted by a move. Kubernetes namespaces are tied to the project name, not the organization, so workloads keep running exactly as they were.
Who Can Move a Project
You must be an owner or admin of both organizations:
- the organization the project is in (the source), and
- the organization you're moving it to (the destination).
| Your role in… | Source org | Destination org |
|---|---|---|
| Owner / Admin in both | ✅ Can move | ✅ Can move |
| Member, or admin of only one side | ❌ Cannot move | ❌ Cannot move |
If you don't belong to both organizations as an owner or admin, the move is refused.
How to Move a Project
- Go to Projects.
- On the project card, open the actions menu (the ⋯ / dropdown).
- Click Move.
- Choose the destination organization from the list. Only organizations where you're an owner or admin appear.
- Review the notice about team access and billing (below), then click Move project.
The project disappears from the current organization's list and appears under the destination organization.
The picker only lists organizations where you're an owner or admin (other than the current one). If the organization you want isn't there, have one of its owners promote you to admin first.
What Happens to Team Access
Access is scoped per organization, so a move resets who can reach the project:
- This organization's members lose access to the project and its services. Their access grants for the moved project are cleared.
- In the destination organization, owners and admins see the project immediately.
- Members of the destination organization start with no access — grant it to them afterward from Teams & Access Control if they need it.
See Teams & Access Control for how to grant project and service access.
Plan Limits
The move is checked against the destination organization's plan. If moving the project would push the destination over its limits — projects, apps, databases, or domains — the move is blocked and nothing changes.
Free up capacity in the destination organization (or have it upgraded) and try again. See Plans & Usage.
Billing & History
Past usage and billing history stays attributed to the original organization — a move doesn't retroactively re-bill prior consumption. From the move forward, the project's usage counts toward the destination organization.
Moving a Project Back
There's no separate "undo." To reverse a move, simply move the project again, selecting the original organization as the destination (subject to the same role and plan-limit rules).