7. Transferring a project
You can hand a project to another account, such as a client's. Every deployment keeps its addresses, ports and settings; only the owner and who pays change.
What moves and what stays
| Moves with the project | Stays the same |
|---|---|
| Every deployment in it | Hostnames, ports, IP addresses and custom domains |
| Every SDK app in it | Certificates, builds and environment variables |
| The access keys you choose | Database data and backups |
No container is recreated, so your servers keep running through the transfer.
Send a project
You need the Admin or Owner role.
- On the Dashboard, select the project and choose Transfer.
- Enter the Recipient account email: the email the receiving account signed up with.
- Under Access keys, tick the keys that should move with the project. A key that moves keeps working unchanged for whoever holds it, including you. Keys you leave are detached from the project's deployments.
- Optionally add a Note for the recipient, of at most 500 characters.
- Choose Send transfer.
The recipient is emailed. The offer stays open for 7 days. An account can start at most 10 transfers a day, and a project can have only one transfer waiting at a time.
To withdraw an offer, open Project Transfers and choose Cancel under Sent by this account.
Accept a project
Open Project Transfers and choose Review under Offered to this account.
Check Deployments: the list, and about how many credits a month the project costs.
Under Access keys, decide for each key:
Key Your choices Moves with the project Keep it as it is, or Keep it, issue a new secret Stays with the sender Create a new key with the same permissions, Use one of my keys, or No key Under SDK apps, choose whether to Issue new SDK keys, and how long the old keys keep working: Stop immediately, 7, 14 or 30 days.
Under Webhooks, choose whether to turn off webhooks that point at the sender's endpoints.
Read What the sender has seen: secrets the sender knew that keep working after the transfer. Change them from the deployment's settings if the sender should no longer have them.
Choose Accept transfer, or Decline to leave the project with the sender.
After accepting, the page shows any new access key secrets and new SDK keys once. Copy them before you choose Done.
Billing and limits
| Rule | Detail |
|---|---|
| Who pays | The sender is charged up to the moment you accept, and you from then on |
| Balance needed | The receiving account needs at least one day of the project's running cost in credits. If it has less, top up first |
| Busy deployments | A project cannot change hands while a deployment in it is being deleted or has a change running |
| Key limit | A deployment can still have at most 5 access keys after the transfer |

