> 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/requirements-and-statuses.md).

# Requirements and Statuses

The prerequisites worth validating before launching a migration and the phases the process goes through.

### Prerequisites

Validating this before starting avoids blocks midway through the process:

* 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 ones cannot be migrated).
* Compatible operating system and workload type.
* Well-defined disks: number, size, and partition when applicable.
* DHCP enabled on all network adapters.

> #### ❗️ Encrypted disks are not migrated
>
> This is a hard limitation of the current flow. Decrypt the source disk before migrating.

### Process states

The migration progresses through phases that are reflected in the status:

* **Transfer**: the disk arrives via SFTP, URL, or Acronis (states *preparing* and *waiting for transfer*).
* **Conversion**: if the format is not directly usable, the platform automatically converts it.
* **Import or deployment**: only the disks, or also the destination server.
* **Final adjustments (tuning)**: in migrations with deployment, the last adjustments on the migrated machine.
* **Final state and validation**: when you see **Pending adjustments**, the planned phases have been completed; during validation, a series of checks confirm that everything is correct.

The full walkthrough, with details of each phase, is in The process from start to finish.

### Next steps

* See the layers of [Costs.](/docs-en/productos/migrations/details/costs.md)
* Launch your first migration with the [Quick guide.](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/migrations/details/requirements-and-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.