> 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/fr/productos/migrations/details/formats-and-transfer.md).

# Formats et transfert

Les formats de Disque pris en charge et les modes de transfert, comme référence rapide.

Référence rapide de ce que prend en charge Migrations. Le détail, avec les tableaux et le critère de choix selon votre cas, se trouve dans Concepts.

### Formats de Disque

Deux voies : **Acronis Agent** (export d’une copie Acronis) et **VHD – Conversion de disques** (VMDK, VHD, VHDX, QCOW2, VDI, RAW), que la plateforme convertit automatiquement. Le flux prend également en charge les images **OVA**.

Le tableau des formats avec leur origine habituelle se trouve dans [Formats de Disque.](/fr/productos/migrations/concepts/formats.md)

### Modes de transfert

Quatre voies : **SFTP** (Chiffrement, le mode général), **téléchargement par URL** (depuis S3, Azure ou une source compatible), **téléversement web** et **Acronis Agent**.

Le tableau indiquant quand chaque mode est recommandé se trouve dans [Modes de transfert.](/fr/productos/migrations/concepts/transfer.md)

### Étapes suivantes

* Consultez les [Exigences et états](/fr/productos/migrations/details/requirements-and-statuses.md) du processus.
* Choisissez le guide de la source concernée dans la section[ How-to.](/fr/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/fr/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.