Skip to main content

Move a Project Between Organizations

As a platform operator you can move a project — with its entire contents — from one organization to any other organization on your instance, straight from the admin dashboard. This is the operator-level counterpart to the self-serve move your organizations' own owners and admins can perform from their dashboard.

Operator vs. organization move
  • You (operator) can move a project between any two organizations on your instance — no membership required.
  • An organization owner/admin can move a project only between organizations they belong to (as owner or admin). That self-serve flow is covered in the Developer Guide.

What Moves​

Moving a project takes its whole subtree in one step — all environments, applications, databases, Compose stacks, and the domains attached to them. Nothing is migrated piece by piece.

No downtime

Running services are not redeployed or restarted. Kubernetes namespaces are keyed to the project name, not the organization, so workloads keep running.

How to Move a Project​

  1. Open the admin dashboard and go to Organizations & Plans.
  2. Find the organization the project currently lives in (the source). Use the search box if needed.
  3. Click Move project on that organization's row.
  4. In the dialog, choose:
    • the project to move (the picker lists that organization's projects), and
    • the destination organization.
  5. Click Move project.

The dialog reports how many source-organization members lost access as a result.

What Happens to Team Access​

Access is scoped per organization, so the move resets who can reach the project:

  • Source-organization members lose access to the project and its services — their access grants for it are cleared.
  • In the destination organization, owners and admins see the project immediately; other members start with no access and must be granted it.

Plan Limits​

The move is validated against the destination organization's plan. If it 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 assign it a larger plan (see Organizations), then try again.

Billing & History​

Past usage and billing history stays attributed to the source organization — moving a project does not retroactively re-bill prior consumption. From the move forward, the project's usage counts toward the destination organization. Org-scoped billing records (subscriptions, usage history, mailboxes) are not transferred.

Payment Gateway services

If the project had the Payment Gateway service enabled, its per-project service record is automatically re-pointed to the destination organization's merchant on move (and re-provisioned on the next license sync if the destination has no merchant yet).

Reversing a Move​

There's no separate undo — move the project again, selecting the original organization as the destination.