> 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/what-it-includes.md).

# What's Included

What you can migrate today, from which sources, and with what coverage by area.

What the Migration service covers today, as a quick reference.

### What you can migrate

* **Services**: Servers and scenarios related to Remote Desktop.
* **Source**: physical or virtual server.
* **Source**: on-premises environments, other hypervisors, or other cloud providers.

### Coverage by area

| Area                | What it covers                                                                                                      |
| ------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Source**          | Physical or virtual server (the assistant handles both).                                                            |
| **Formats / types** | Compatible virtual disks (VHD, VHDX, VMDK, QCOW2, RAW, VDI), OVA images, and workflows with Acronis.                |
| **Transfer**        | SFTP, download via URL, and Acronis Cloud. The system generates upload or download credentials from a provided URL. |
| **Destination**     | Disk import only, or import plus deployment of a server.                                                            |
| **Operation**       | Status tracking, console access (VNC) in the workflows that require it, and final validation.                       |
| **Support**         | Support coordinated with Partner Success to plan and carry out the migration.                                       |

### Next steps

* See the details of [Formats and transfer.](https://docs.plenit.com/docs-en/productos/migrations/details/formats-and-transfer.md)
* Review the [Requirements and statuses](https://docs.plenit.com/docs-en/productos/migrations/details/requirements-and-statuses.md) before you begin.
* Understand the what and the why in [Migration concepts.](https://docs.plenit.com/docs-en/productos/migrations/concepts/what-they-are.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/what-it-includes.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.
