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

# Disk formats

The two format paths (Acronis Agent and VHD – Disk Conversion) and which formats each one supports.

When preparing the migration, you choose the format in which you deliver the disk. There are two paths, depending on where you are coming from.

### Acronis Agent

Directly dump an Acronis backup so it can later be deployed in Plenit. This is the path when your source already uses Acronis as backup software.

### VHD – Disk conversion

Upload virtual disks in several formats and the platform automatically converts them so they are compatible. This is the general path when you export the disk from a hypervisor or a cloud.

<figure><img src="https://files.readme.io/0a442ae14a7436045b6f557731f9499d63c7dffa630b4cef735635c6ce3c1785-table-migration-disk-formats.png" alt=""><figcaption></figcaption></figure>

In addition to these disk formats, the flow also covers images **OVA** and Acronis-based flows.

> #### 📘 You don’t have to convert the disk yourself
>
> If the source format cannot be used directly, the platform does the conversion to a compatible format. You deliver the disk exactly as you export it from your source.

> #### 🚧 Compatibility according to the source
>
> Actual compatibility depends on the source and the technical state of the system. Some formats have had specific operational limitations depending on the case, so it is advisable to review the guide for the specific source before starting.

### Next steps

* Decide how the disk gets to Plenit in [Transfer modes.](https://docs.plenit.com/docs-en/productos/migrations/concepts/transfer.md)
* Check the guide for the specific source you are going to migrate in the section on [How-to.](https://docs.plenit.com/docs-en/productos/migrations/how-to.md)
* Review the full journey in [The process.](https://docs.plenit.com/docs-en/productos/migrations/concepts/the-process.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/concepts/formats.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.
