> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/client-portal/service-management/transferring-a-service-to-another-account.md).
# Transferring a service to another account
How to transfer a service to another Synteq customer
{% hint style="danger" %}
Your service won't be wiped before the transfer by us. If you don't want the new owner to have access to your data, please re-install your service.
There is a $5 transfer fee
{% endhint %}
### 1. Open a ticket
Log into the [billing area](https://get.crunchbits.com/), then on the left navigation bar click on `Support` \[1], then `Tickets` \[2].
Then click on the `Open Ticket` button
### 2. Fill out the ticket
Select the `General Enquiries` department.
Afterward, select the correct associated service \[1], and fill out the other boxes as follows:
Subject [1]
Transfer request - xxx.xxx.xxx.xxx
Message [2]
Hello,
I'd like my service (IPv4: xxx.xxx.xxx.xxx) to be transferred to the customer associated with \[] e-mail address.
Thank you!
### 3. Submit the ticket
Submit the ticket by clicking on the `Submit` button on the bottom
### 4. Pay the invoice that we create
After we review your request, we'll add a $5 invoice to your account. Please pay it, and let us know once it's paid, so we can proceed with the transfer.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://legacy.docs.synteq.com/client-portal/service-management/transferring-a-service-to-another-account.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
