Request a service transfer

Creates a transfer request for the specified services. A request can contain any of the specified service types and any number of each service type. At this time, only Linodes can be transferred.

When created successfully, a confirmation email is sent to the account that created this transfer containing a transfer token and instructions on completing the transfer.

When a transfer is accepted, the requested services are moved to the receiving account. Linode services will not experience interruptions due to the transfer process. Backups for Linodes are transferred as well.

DNS records that are associated with requested services will not be transferred or updated. Please ensure that associated DNS records have been updated or communicated to the recipient prior to the transfer.

A transfer can take up to three hours to complete once accepted. When a transfer is completed, billing for transferred services ends for the sending account and begins for the receiving account.

This operation can only be accessed by the unrestricted users of an account.

There are several conditions that you need to meet to successfully create a transfer request:

  1. The account creating the transfer can't have a past due balance or active Terms of Service violation.

  2. The service needs to be owned by the account that is creating the transfer.

  3. The service can't be assigned to another Service Transfer that is pending or that's been accepted and is incomplete.

  4. Linodes can't:

    • be assigned to a NodeBalancer, Firewall, VLAN, VPC, or Managed Service.

    • have any attached Block Storage Volumes.

    • have any shared IP addresses.

    • have any assigned /56, /64, or /116 IPv6 ranges.

linode-cli service-transfers \
  create \
  --entities.linodes 111 \
  --entities.linodes 222

<https://www.linode.com/docs/products/tools/cli/get-started/>
account:read_write

<https://techdocs.akamai.com/linode-api/reference/get-started#oauth>
Language
Authorization
Click Try It! to start a request and see the response here!