> 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/what-they-are.md).

# What Migrations Are

What migrating in Plenit means, what you can move, and what to check before starting to avoid blocks.

Migrating in Plenit means moving servers, disks, backups, or environments from an external source (physical, virtual, or another provider) to the platform, so they are operational, manageable, and monitorable from the dashboard.

It’s not just about copying data: the service chains together the transfer, format conversion, import, and, if you want, the deployment of the target server and its final settings.

> #### 📘 In one sentence
>
> Move disks or servers from any provider or local environment to the platform in three steps. The wizard guides you from the start until everything is operational.

### What you can migrate today

You can migrate **Servers** and scenarios related to **Remote Desktop**, using virtual disks, OVA, or Acronis-based workflows depending on the case.

The source can be a physical or virtual server, and may come from an on-premises environment, another hypervisor, or another cloud provider.

### What you will decide

A migration is defined by four choices, and understanding them well is what prevents blockages halfway through the process: the **source** (physical or virtual), the **disk format** (Acronis Agent or VHD – Disk Conversion), the **transfer mode** (how the disk gets to Plenit) and the **destination** (import only the disks or also deploy a server). Each one has its own page in this section.

The starting point determines almost everything else. This is the initial decision depending on where you are coming from:

<figure><img src="https://files.readme.io/44172c96bbb841aa040ea78a336ae5e83edf953cdd8b9b19f497672264b2a558-diagram-migration-decision-tree.png" alt=""><figcaption></figcaption></figure>

### Before you start: what it’s worth checking

These prerequisites repeat in almost all migrations and prevent the process from getting stuck halfway through:

* **Local administrator access** on the source machine.
* **Validated VPN** if there is site-to-site connectivity or network dependency.
* **Firmware identified**: BIOS or UEFI.
* **Unencrypted disks**: encrypted disks cannot be migrated.
* **Compatible operating system and workload** with the platform.
* **Well-defined disks**: number, size, and partitioning where applicable.
* **DHCP enabled** on all network adapters.

> #### ❗️ Encrypted disks are not migrated
>
> This is a hard limitation of the current workflow. If the source disk is encrypted, decrypt it before migrating or you will not be able to complete the process.

### Next steps

* Decide the starting point in [Physical or virtual source.](https://docs.plenit.com/docs-en/productos/migrations/concepts/source.md)
* When you know the source, go to [Disk formats](https://docs.plenit.com/docs-en/productos/migrations/concepts/formats.md) and [Transfer modes.](https://docs.plenit.com/docs-en/productos/migrations/concepts/transfer.md)
* To launch your first migration, go to the [Quick Guide to the Migrations tool.](https://docs.plenit.com/docs-en/productos/migrations/quickstart.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/what-they-are.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.
