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

# The Process

The stages of a migration: from the 3-step wizard to transfer, conversion, deployment, adjustments, and validation.

The migration assistant is the visible part, but the service's value lies in what it automates afterward: download, conversion, deployment, and validation.

It's worth understanding the full flow so you know at what point you are at any given moment.

<figure><img src="https://files.readme.io/84334c48c8071996fa5d3a058333767084b428c5f882ba8e4a11a455b2d0b8d6-diagram-migration-process-flow.png" alt=""><figcaption></figcaption></figure>

### The 3-step assistant

From **Cloud Services → Migrations**, **New migration** opens an assistant that collects your intent and configuration:

1. **Service**: what you are going to migrate (for example, Servers).
2. **Source**: physical or virtual, disk format, transfer mode, and file names.
3. **Destination**: organization, subscription, and zone, and whether you want to deploy a new server with the disks (name, operating system, size, and network).

> #### 🚧 Step 2 determines everything
>
> The source format and transfer mode determine the rest of the process. Changing them later means relaunching the migration.

### The stages that come next

Once launched, the migration goes through several phases that are reflected in the status:

* **Transfer**: the disk, backup, or image arrives via SFTP, URL, or Acronis, depending on the flow. You will see statuses such as *preparing transfer* and *waiting for transfer*.
* **Conversion**: if the source format cannot be used directly, the platform automatically converts it into a compatible format.
* **Import or deployment**: either you only import the disks, or you also create the destination server.
* **Final adjustments (tuning)**: in migrations with deployment there may be a tuning phase. In Windows this usually involves downloading and running an application on the migrated server; in Linux, an application and some additional commands.
* **Final status and validation**: when you see **Pending adjustments**, the planned phases have been completed and only the final adjustments remain. When you validate from the tool, a series of checks confirm that everything is correct; if any fail, it tells you what to fix.

> #### 📘 Notices during the process
>
> Not all migrations flow the same way. Sometimes the process is fully automatic; other times, the tool asks you for specific actions via notices in the migration details so you can unblock it.

### Tracking

All processes are recorded on the main Migrations page, so you can have several migrations in progress and track them from one place. Each one has its details, with the current phase, the data at each moment, and the required actions.

### Next steps

* Launch your first migration with the [Quick guide to the Migration tool](https://docs.plenit.com/docs-en/productos/migrations/quickstart.md).
* Choose the guide for the specific source in the section of [How-to.](https://docs.plenit.com/docs-en/productos/migrations/how-to.md)
* Check requirements, costs, and limitations in [Migration Details.](https://docs.plenit.com/docs-en/productos/migrations/details.md)

<br>


---

# 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/the-process.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.
