Move a project to another organization
How a project is moved to a different organization, what moves with it, and what the new owner should do straight afterwards.
Sometimes a project has to change owners: a freelancer hands an app to a client, or a company restructures. A project can be moved to another organization with everything in it, without rebuilding anything.
How to ask for a move
Project transfers are carried out by PGBHub support rather than by a button in the project. Use Contact support and tell us:
- The project (its name and its Immutable Project ID from Project Settings).
- The organization it should move to, and the email of that organization's owner.
- Whether usage from the move date onward should be billed to the new organization.
Both sides should agree before you ask. The person receiving the project needs an account and an organization.
What moves
A project is the container for its databases, containers, API keys, secrets, mail settings and domains. A transfer changes which organization owns the project. Nothing is copied, so:
- the project ID, slug, database names and connection strings stay the same,
- your applications keep working during and after the move,
- the new organization's owner sees the project under Projects, and the old one no longer does.
Before the move happens, a preview shows what will move and what to check. A transfer that stops part-way can be run again safely.
What does not change automatically
Keys, passwords and secrets are not rotated by the move. Anyone who had them before, including the previous owner's team, can still use them until the new owner replaces them. The new owner should rotate them as soon as the move is done:
- Create new project API keys and revoke the old ones. See API keys.
- Rotate the database role key on the Connection page and update your apps. See Connection strings.
- Review Secrets & Env and replace values the previous owner knew.
- Reconnect GitHub in Project Settings if containers deploy from a repository. The old owner's GitHub connection stays linked until you do.
- Review who has access under IAM. See Invite teammates and choose roles.
Good to know
- You can export your data before the move. See Restore, download and import backups.
- The new organization's role rules apply from the moment it arrives.
- Billing for the project follows the arrangement agreed with support when the transfer is scheduled.
More guides in Console: projects & teams
Organizations and projects
How organizations (workspaces) and projects relate, how to switch between them and who pays for what.
Invite teammates and choose roles
Invite people to your organization from IAM, pick a role and project scope, change access later and cancel invitations.
Project settings, keys, secrets and deleting a project
What the Project Settings page shows, how to rename a project, where API keys and secrets live and how to delete a project safely.
Protect your account with a strong password, two-step sign-in and session control
Change your password, turn on two-step sign-in with recovery codes, sign out other sessions and revoke account API keys.
The PGBHub mobile app
What you can check and do from the PGBHub app on your phone, and what stays on the web.