> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/migrations/details/costs.md).

# Costs

The three layers of cost: assistance, destination infrastructure, and exceptional cases.

There is no fixed public fee for the migration service as such.

The cost is better understood by separating it into three layers.

| Layer                          | What it involves                                                                                                            |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| **Migration assistance**       | No cost. The team's support to plan and carry out the migration is not a paid service.                                      |
| **Destination infrastructure** | This is the project's actual cost: it depends on the servers, storage, network, and services you deploy at the destination. |
| **Exceptional costs**          | In reversibility or export scenarios, additional costs may apply, subject to prior approval.                                |

> #### 📘 The key message about costs
>
> Migration assistance is free; the cost of the project comes from infrastructure consumption at the destination, and there are only exceptional costs for special operations (reversibility or export) that are communicated for prior approval before they are applied.

### Next steps

* See the[ Support and limitations](https://docs.plenit.com/docs-en/productos/migrations/details/assistance-and-limitations.md) of the service.
* Size the destination in the [Server Details.](https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md)
* If you need support, request [an assisted migration.](https://docs.plenit.com/docs-en/productos/migrations/how-to/como-solicitar-ayuda-para-migrar-un-servidor-a-cloud.md)


---

# 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://docs.plenit.com/docs-en/productos/migrations/details/costs.md?ask=<question>&goal=<user_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.
