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

# Frequently Asked Questions

Frequently asked questions about Migrations: what can be migrated, formats and transfer, the process, and assistance and costs.

For the details of each item, each answer links to the corresponding concept, guide, or reference.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What can be migrated</strong></td><td>What services and sources it supports, physical vs. virtual, encrypted disks, and prerequisites.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/concepts/what-they-are.md">What Migrations Are</a></td></tr><tr><td><strong>Formats and transfer</strong></td><td>Disk formats, automatic conversion, and how to choose the transfer mode.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/details/formats-and-transfer.md">Formats and Transfer</a></td></tr><tr><td><strong>The process</strong></td><td>Duration, target deployment, states, validation, and parallel migrations.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/concepts/the-process.md">The Process</a></td></tr><tr><td><strong>Support and costs</strong></td><td>What it costs to migrate, free support, and how to request or modify it.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/details/assistance-and-limitations.md">Support and Limitations</a></td></tr></tbody></table>

### What can be migrated

<details>

<summary>What services can I migrate to Plenit?</summary>

Today you can migrate Servers and scenarios related to Remote Desktop. The source can come from an on-premises environment, another hypervisor, or another cloud provider. It is developed in [What migrations are.](https://docs.plenit.com/docs-en/productos/migrations/concepts/what-they-are.md)

</details>

<details>

<summary>What is the difference between physical and virtual source?</summary>

If the disk is already a virtual file that you can export (VMware, Hyper-V, a cloud VM), it is virtual. If you have to generate the image from a physical machine or from a backup, it is physical. The choice changes the formats and the workflow offered by the wizard, so it is worth getting right. More in [Physical or virtual source.](https://docs.plenit.com/docs-en/productos/migrations/concepts/source.md)

</details>

<details>

<summary>Can I migrate encrypted disks?</summary>

No. This is a hard limitation of the current flow: encrypted disks are not migrated. Decrypt the source disk before starting. You have the full list of prerequisites in [Requirements and states.](https://docs.plenit.com/docs-en/productos/migrations/details/requirements-and-statuses.md)

</details>

<details>

<summary>What do I need to check before launching a migration?</summary>

Local administrator access on the source, validated VPN if there is site-to-site, identified firmware (BIOS or UEFI), unencrypted disks, compatible operating system, well-defined disks, and DHCP enabled on all network cards. Checking it beforehand avoids blocks halfway through the process.

</details>

### Formats and transfer

<details>

<summary>What disk formats does Migrations support?</summary>

Via VHD – Disk conversion: VMDK, VHD, VHDX, QCOW2, VDI, and RAW. In addition, the flow supports OVA images and dumps with Acronis Agent. The platform automatically converts the format if needed. You have the table in [Disk formats.](https://docs.plenit.com/docs-en/productos/migrations/concepts/formats.md)

</details>

<details>

<summary>Do I have to convert the disk myself before uploading it?</summary>

No. You upload the disk exactly as you export it from your source and, if the format is not directly usable, the platform performs the conversion to a compatible format.

</details>

<details>

<summary>Which transfer mode is best for me?</summary>

SFTP is the general mode (encrypted, works from on-premises or cloud with any operating system). If the disk is already published as a link in S3 or Azure, downloading by URL is faster. You also have web upload and Acronis Agent. How to choose each one is in [Transfer modes.](https://docs.plenit.com/docs-en/productos/migrations/concepts/transfer.md)

</details>

<details>

<summary>I'm going to import by URL. What should I keep in mind?</summary>

The link must remain active and accessible for the duration of the transfer, because Plenit is the one downloading the disk. In some sources, such as AWS, URL import is launched from the same machine where you performed the export operation.

</details>

### The process

<details>

<summary>How long does a migration take?</summary>

It mainly depends on the server size and the transfer mode. Transfer and conversion are the phases that vary the most. You can track the status at any time from the Migrations page.

</details>

<details>

<summary>Do I have to deploy a server at the end?</summary>

Not necessarily. You can choose to only import the disks and leave them uploaded for later use, or import and deploy a destination server with name, operating system, size, and network in the same wizard.

</details>

<details>

<summary>What does the Pending settings status mean?</summary>

That all planned phases have been completed and only the final adjustments remain for the machine to be 100% operational. In Windows, this usually means downloading and running an application on the migrated server; in Linux, an application and some additional commands. The full walkthrough is in [The process from start to finish.](https://docs.plenit.com/docs-en/productos/migrations/concepts/the-process.md)

</details>

<details>

<summary>What happens if validation fails?</summary>

When you validate from the tool, a series of checks is run. If any fail, the validation itself tells you the detected error and what you need to fix before validating again.

</details>

<details>

<summary>Can I have several migrations at once?</summary>

Yes. All processes are recorded on the main Migrations page, so you can launch several and track them from one place, each with its own details and current phase.

</details>

### Support and costs

<details>

<summary>How much does it cost to migrate?</summary>

There is no fixed public rate for the migration service. The real project cost comes from the consumption of the destination infrastructure (servers, storage, network). There are only exceptional costs for special operations such as reversibility or export, and they are communicated for prior approval. The three-layer breakdown is in [Costs.](https://docs.plenit.com/docs-en/productos/migrations/details/costs.md)

</details>

<details>

<summary>Does migration support have a cost?</summary>

No, migration support is free. It is the support from the Partner Success team to plan and execute the migration, mainly intended for cases with operational risk or outside business hours.

</details>

<details>

<summary>How do I request an assisted migration?</summary>

From the tool itself, with a request that includes the service to be migrated, the location, the number of servers and their characteristics, the need for VPN, the contact person, and the date. The step-by-step process is in [How to request an assisted migration.](https://docs.plenit.com/docs-en/productos/migrations/how-to/como-solicitar-ayuda-para-migrar-un-servidor-a-cloud.md)

</details>

<details>

<summary>Can I change or cancel a support request?</summary>

Yes. Once submitted, you can modify the date, contact person, or phone number, as well as cancel the request.

</details>

### Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick Start</strong></td><td>Launch your first migration with the tool.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>The approach and decisions before migrating.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides to migrate depending on the source.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/how-to.md">How-to</a></td></tr><tr><td><strong>Details</strong></td><td>Requirements, costs, and limitations.</td><td><a href="https://docs.plenit.com/docs-en/productos/migrations/details.md">Details</a></td></tr></tbody></table>


---

# 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/faq.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.
