Software Factory: Transfer a Project
Hand a project to another person, or move it to another organization (for example, a client's). Who can do it, what moves, and who pays afterward.

You can transfer a project in two ways. Open the menu on a project card on the Projects page and choose Transfer project, or use Transfer under Ownership in the project’s Settings.
Two kinds of transfer
- Person. The new owner gets full control. The project stays in its organization, and that organization keeps paying for it.
- Organization. The project moves into another organization. That organization owns it and pays for it from then on. Use this to hand a project to a client.
Who can transfer
- A person transfer: the project’s owner, or an owner or admin of the project’s organization.
- A move to another organization: the project’s owner, who must also be an owner or admin of the project’s organization. If you move it right away, you must also be an owner or admin of the organization it goes to. An agency owner who reaches the organization through a workspace as an Owner counts. A workspace Editor does not.
Chipp checks this on the server. The dialog opens when at least one kind is allowed for you, and it shows only the kinds you can use. If neither is allowed, you see a message that says why. An organization admin who is not the project’s owner can hand the project to a person, but the owner has to move it to another organization.
The Organization tab
The tab names both organizations, for example “Client Portal moves from Acme Studio to Client Co.” It also says who pays: the new organization pays for builds, hosting, domains and agent usage from then on, and past usage stays on the old organization’s bill.
You can choose an organization you run, which moves the project right away and makes you the owner. Or you can enter a client’s email. They get a link, choose the organization they run, and the project moves when they accept.
What moves and what stays
- Moves: code, plan and tickets, secrets and integrations, custom domains, scheduled tasks, deploy keys and API keys, and the project’s agent.
- Stays: usage the old organization already paid for, and a GitHub repository (transfer it on GitHub).
- Resets: other members and open invites are removed, so people in the old organization lose access unless they are in the new one too.
A move is blocked while a ticket is running, while a transfer is pending, while the project takes live payments, or if the new organization already has a project with the same name.