> 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/formats-and-transfer.md).

# Formats and Transfer

Supported disk formats and transfer modes, as a quick reference.

Quick reference for what Migrations supports. The details, with the tables and the criteria for choosing according to your case, are in Concepts.

### Disk formats

Two options: **Acronis Agent** (dump of an Acronis copy) and **VHD – Disk conversion** (VMDK, VHD, VHDX, QCOW2, VDI, RAW), which the platform converts automatically. The flow also includes images **OVA**.

The table of formats with their usual source is in [Disk formats.](https://docs.plenit.com/docs-en/productos/migrations/concepts/formats.md)

### Transfer modes

Four options: **SFTP** (encrypted, the general mode), **download by URL** (from S3, Azure or a compatible source), **web upload** and **Acronis Agent**.

The table showing when each mode is appropriate is in [Transfer modes.](https://docs.plenit.com/docs-en/productos/migrations/concepts/transfer.md)

### Next steps

* Review the [Requirements and statuses](https://docs.plenit.com/docs-en/productos/migrations/details/requirements-and-statuses.md) of the process.
* Choose the guide for the specific source in the section of[ How-to.](https://docs.plenit.com/docs-en/productos/migrations/how-to.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/formats-and-transfer.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.
