Transfer a server to another account
You can give a server to someone else, for example when you've built a website for a client and they should own and pay for its server. The server keeps running throughout. Its disk, data and IP addresses go with it, so nothing needs to be copied.
The person you send it to chooses which of their organizations takes it. From the moment they accept, it's billed to their wallet.
What can be transferred
- Servers bought from the portal can be transferred. These are the ones you created from the catalog.
- Servers in your own cloud accounts can't be transferred. For example, servers in your own AWS or DigitalOcean account stay with that account. To move one of those, use a migration instead.
- Some servers have to wait first:
- a server that's still being created;
- a server suspended for an unpaid balance;
- a server that's part of a migration in progress.
- Only Owners and Admins can transfer servers, on both the giving and the receiving side.
Offer a server
- Open the server and scroll to Transfer to another account.
- Enter the recipient's email. They don't need an account yet.
- Optionally, add a message, such as "Your shop server, as agreed".
- Select Offer transfer.
We email the recipient a link. The offer waits for 7 days. Until they accept, the server stays yours and is billed to you.
To take the offer back, open the server and select Cancel transfer.
Accept a server
- Open the link in the email. You can also find the offer under Instances › Transfers, and the dashboard shows a notice when a server is offered to you.
- Sign in, or sign up, with the email address the offer was sent to, and verify it.
- Check the server's size, price and region.
- Under Into organization, choose one of your organizations. It must be one where you're an Owner or Admin, and not the one sending the server.
- Select Accept transfer. The server opens in your organization.
Balance: the organization's balance must cover the server's first 24 hours, the same as for a new order. If it doesn't, add funds first.
Customers of a reseller can only transfer servers to other customers of the same reseller.
If you don't want the server, select Decline. The sender is told and keeps the server.
Billing
- Usage up to the moment of acceptance is charged to the sender.
- Usage after that is charged to the recipient.
- The monthly price cap applies to each organization separately.
- If backups were on, they stay on and keep their extra charge. The recipient can turn them off on the server's page.
- Extra bandwidth bought this month stays with the server.
What changes for the server
- Project: it moves into the receiving organization's default project. Tags from the old organization are removed.
- Access for the sender: the sender's team loses access to the server in the portal. Their old activity stays in their audit log, and their support tickets about it stay with them.
- Root password and SSH keys: they don't change. If you're receiving a server, reset the root password under Hostname and root password, or reinstall, so that only you can sign in.
Notifications and the API
Transfers are recorded in both organizations' audit logs. Notification channels can subscribe to these events under Instances:
- Server transfer offered
- Server transfer declined
- Server transferred away
- Server received by transfer
Scripts and AI assistants can transfer servers too. See Transfers in the API reference.