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

# Quick Start

What Migrations are, what the 3-step wizard is like, what formats and transfer modes it supports, and how the final adjustments are made.

Migrations is the tool that uploads, converts, and deploys virtual machines and other cloud services in an assisted way.

With it you take your **Servers** and environments of **Remote Desktop** to Plenit through a guided process that reduces time and risk.

This guide gives you the overview: where the tool lives, the three-step assistant to launch a migration, the supported formats and transfer modes, how you follow the process from its details, and how the final adjustments are closed.

> #### 👍 What you get
>
> An overview of Migrations to choose the right source format and transfer mode before launching your first migration, and to know how to read the status of each process as it progresses.

### Where the tool lives

Access **Migrations** from **Cloud Services**. The tool has two tabs:

* **Migrations**: your migration processes and the assistant to launch new ones.
* **Assistance**: the assisted migration by our team, for when the scenario is complex or you'd rather delegate it.

When you don't have any migrations yet, the tab **Migrations** welcomes you with an introduction to what you can do: a **assisted migration wizard** that guides you from start to finish, **multiple formats and transfer methods** to adapt to your environment, and **connectors for any source** (AWS, Microsoft Azure, OVHcloud and other cloud providers, as well as on-premises environments).

From here you launch your first migration with **New migration**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-cc8a776d7da09891bfddbfb2d63424e506356660%2FInicio_Migraciones.png?alt=media" alt=""><figcaption><p>Migrations</p></figcaption></figure>

Once you have migrations underway, the tab **Migrations** shows the **list** of all the processes launched from your organization, for each client. This way you can have several migrations at once and follow them from a single place. Each row gives you, at a glance:

* **ID** of the process and its **status** (for example, **Pending adjustments** in orange, **Completed** in green or **Canceled** in red).
* **Server** and **Disks**, with a **progress bar** and its percentage.
* **Organization**, **Subscription** and **Date**.
* The **Actions** menu (⋮) to operate on each process.

At the top right you have **Request assistance** (takes you to the assisted migration) and **New migration** (opens the assistant). The **Filter** button helps you narrow the list when you have many processes.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-3f0fe43376c53f1bba96ec9a9878e67b8aee6893%2FPagina_de_Migraciones.png?alt=media" alt=""><figcaption></figcaption></figure>

### The 3-step assistant

Click **New migration** (New migration) in **Cloud Services → Migrations** to launch the assistant, which automates the upload, conversion, and deployment. There are three steps: **Service**, **Source** and **Destination**.

> #### 🚧 The Source Step conditions everything else
>
> The source format and transfer mode you choose determine the rest of the process. Take your time with this step: changing it later means relaunching the migration.

#### Step 1 · Service

You choose **which service to migrate**. Right now the assistant offers **Servers** and **Remote Desktop** (Remote Desktop); **File Storage** and **DNS** appear as *Coming soon*. Each card has a **Learn more** with the service details.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-d8b941818c08d328bde541ceffe79fc4bc5f5dff%2FPrimer_paso_Servidores.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 2 · Source

You define where your data comes from. Here you decide:

* If the source server is **physical or virtual**.
* The **format of the server to be migrated**: **VHD – Disk conversion** or **Acronis Agent**.
* The **transfer mode**: **FTP Client** or **Download from URL**.
* The **disks to import**: file name, partition (for example, System), and disk name. You add each disk with **Create**.

Keep in mind the limit: only disks up to **1 TB**are imported, and the compatible extensions are those of the VHD route (VMDK, VHD, VHDX, QCOW2, VDI, RAW). You have the details in Disk Formats and Transfer Modes.

> #### 📘 DHCP on all network cards
>
> All network interfaces of the machine must have DHCP enabled to operate correctly in Plenit’s infrastructure.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-f2040b96439655dcfdfdeb251110f0a92a7bd098%2FSegundo_Paso_Servidores.png?alt=media" alt=""><figcaption></figcaption></figure>

> #### 🚧 Transfer modes in the assistant
>
> The documentation describes four routes (SFTP, download by URL, web upload and Acronis Agent), but the assistant in the screenshot only shows **FTP Client** and **Download from URL** (the Acronis Agent appears as *format*, not as a mode).

#### Step 3 · Destination

You define where the migration arrives:

* **Organization** and **subscription** destination. If you're missing any, create them on the fly with **New organization** or **New subscription**.
* **Location**: the **region** (for example, Madrid or Paris) and its **availability zone**. The region applies to all servers created in that subscription.
* **Do you want to deploy a new server with the imported disks?** With **Yes**, in addition to migrating the disks we deploy a new server with them. With **No**, we only migrate the disks.

If you choose **Yes**, the assistant asks you to configure the server: **name**, **offering** (CPU and RAM), **operating system**, **network type** (Standard Network or VPC Network) and, in **Advanced options**, the manual network configuration (network, mask, gateway, IP and MAC) and opening a TCP port for SSH access.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-7a4292ec40930c84ec838d0d4a2e1377163abf1a%2FTercer_Paso_Servidores.png?alt=media" alt=""><figcaption></figcaption></figure>

> #### 🚧 Operating system catalog and step scheme
>
> The deployment OS catalog (AlmaLinux, Rocky Linux, CentOS, Oracle Linux, Ubuntu, Windows, 3CX and versions) is still to be confirmed against the current panel.
>
> And an old mockup labels the organization/location step as "Step 2 · Where you want to migrate": the current assistant treats it as **Step 3 · Destination**.

### Special case: migrating Remote Desktop

When the service to be migrated is **Remote Desktop**, the flow has a nuance: first you **server** that hosts the remote desktop and then deploy a **new remote desktop service** pointing to that server. The assistant summarizes it in four steps:

1. Migrate the disks and the server that host the remote desktop service.
2. Deploy a new remote desktop service.
3. In the assistant for the new remote desktop, select the server you migrated.
4. Complete the required information and perform the final validations.

If you haven't migrated the server yet, the assistant itself links you to **Server migrations** so you can start there.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-531d29eaecbad5c45afcc16c192b0ba1654f4b27%2FPrimer_Paso_Remote_Desktop.png?alt=media" alt=""><figcaption></figcaption></figure>

### Following the process: migration details

Each process has its **details**, where you see the **phase** the migration is in, the data at each moment, and the actions you need to take to unlock it. The number of phases depends on whether you asked to deploy a server or just migrate disks.

#### With server deployment (5 phases)

The details go through **Source → Disks → Server → Adjustments → Completed**. When the migration reaches **Adjustments** (status **Pending adjustments**), the planned phases have been completed and only the final adjustments remain for the machine to be 100% operational. From this same detail:

* **Access the server** via VNC console.
* **Install the Cloud Migrations Tool** (you download it or run it from the path indicated by the screen itself on the migrated server).
* **Validate the installed components** with the button **Validate**: the tool checks the monitoring software, the virtualization drivers, and the initialization software. If any check fails, it tells you what to fix.

> #### ⚠️ Uninstall the VMware or AWS tools
>
> If the source server has VMware or AWS tools installed, uninstall them before continuing with the adjustments.

> #### ℹ️ Restart and password
>
> When the migration is validated, we restart the server and set the administrator user’s password (if it doesn't exist, we create it). When it's ready we send you a notification with the password.

In the details you also have the blocks of **Server** (name, status, operating system, location, resources, network type and disks), **Disks** (with the progress disk by disk) and **Source** (connection status and the **transfer mode**, with its host, username, and password).

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-f1ab81f4fe0df098933e5f9e9289bc935c7925e0%2FEjemplo_de_migracion_de_Servidor.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Disks only (3 phases)

If you have chosen **No** to deploy a server, the details are shorter: **Source → Disks → Completed**. When it finishes, the screen itself confirms it. There is no Server or Adjustments block here: the migration ends with the imported disks.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-c0458fffb0662d1ce2cae004c3b35aabbeb0b837%2FMigracion_de_Disco_Detalle.png?alt=media" alt=""><figcaption></figcaption></figure>

### Supported disk formats

There are two routes depending on the source of your data: the **Acronis Agent**, which directly dumps an Acronis backup to deploy it afterward, and **VHD – Disk conversion**, which uploads virtual disks in several formats (VMDK, VHD, VHDX, QCOW2, VDI, RAW) to convert them automatically. The flow also includes OVA images. You don't need to convert anything yourself: you upload the disk as you export it and, if the format can't be used directly, we do the conversion for you. You have the table of formats with their usual source in Disk Formats.

### Transfer modes

Four routes depending on your infrastructure: **SFTP** (encrypted, the general mode), **download by URL** (from S3, Azure or a compatible source), **web upload** and **Acronis Agent**. In URL download, the link must stay alive while the transfer lasts, because Plenit is the one downloading the disk. You have the table with when each mode is suitable in Transfer Modes.

### Final adjustments and validation

Once launched, the migration doesn't always flow the same way: it depends on the type and the options chosen. Sometimes it runs automatically to the end; other times, the tool asks you for specific actions through warnings in the details so you can unblock it.

When you see the status **Pending adjustments**, the planned phases have been completed and only the final adjustments remain:

* In **Windows**, you normally download an application and run it on the migrated server.
* In **GNU/Linux**, you download and run an application and some additional commands on the migrated server.

Once that's done, validate from the tool itself: you'll see a series of verification checks. If any fail, the validation tells you the failure and what to fix.

### Assisted migration (Assistance)

If the scenario is complex or you'd rather delegate, you have the assisted migration by our team. You enter through the tab **Assistance** or with **Request assistance** from the list. We move your disks or servers from any provider or local environment through the same three-step assistant, with you at each decision. You also have it in Assisted migration with Partner Success.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-6515dd520baae24a9d1939885cda8bd8854c42db%2FInicio_Asistencias.png?alt=media" alt=""><figcaption></figcaption></figure>

### Conclusion

Migrations exists to remove complexity from a process that usually has a lot: it automates the upload, conversion, and deployment, and keeps visible what you actually have to decide.

The key is in the **Source**, because the format and transfer mode determine everything that comes after.

Once you've chosen correctly, you follow the process from its details (5 phases if you deploy a server, 3 if you only migrate disks) and the checks-based validation confirms that the machine is operational before you mark it as migrated.


---

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