Transferring ownership
Move a project, server, website, or ad campaign to another account entirely.
Transferring ownership hands a project, server, website, or ad campaign to another account and takes it off yours, in full: billing, the Danger Zone, everything. That is different from adding an Admin or a Developer, which shares access to a project without changing who owns it, see Roles and permissions for that.
What can be transferred
Instances, VPS and Full-Stack VPS deployments, external VPS, smart apps, websites, and ad campaigns. Nothing else, a resource type outside that list has no Transfer row.
Send a transfer
Open Advanced
From the project, server, website, or campaign, open the Advanced tab, Danger Zone. See Advanced for the rest of that tab.
Enter the recipient
Click Transfer, then enter the email address of the account you are handing it to.
Confirm
Confirming creates the transfer and notifies the recipient. It now shows as pending, with a Cancel Transfer Request row in its place, until they answer.
Unlike inviting someone to a team, starting a transfer looks the recipient up by their existing account, it does not create one for an address nobody has yet.
A few things are checked before a transfer can be sent: the resource cannot already have one pending, the recipient must not already be on its team (remove them first), sender and recipient cannot be the same account, the recipient's account must be active, and their plan must allow owning that resource type. Ad campaigns are exempt from that last check, they are billed per campaign rather than counted against a plan.
Accepting a transfer
The recipient sees the pending transfer waiting for them and can Accept or Decline it. Accepting an ad campaign that is running on a recurring monthly subscription asks for one more thing first, a payment card, since accepting starts a fresh subscription on their own card going forward:
A lifetime or one-off ad campaign, and every other resource type, need no card to accept. If a card is required but not clear, the transfer stays pending so the recipient can try again with a different one.
What happens on acceptance
Ownership flips immediately: app_uId moves to the recipient's account, and any regional replicas the resource has go with it. Billing re-attributes on its own for metered resources, a VPS, a website. For a subscription ad campaign specifically, the recipient's card starts a new subscription and the sender's is cancelled, prorated back to them.
Cancelling
Either side can end a pending transfer before it completes, from the same Advanced tab: the sender pulls it back with Cancel Transfer Request, or the recipient declines it from their own pending list. Once accepted, a transfer is done and cannot be cancelled or reversed from within it, a second transfer back is a new transfer of its own.