> 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/how-to/como-migrar-un-servidor-desde-hyper-v-a-cloud.md).

# How to Migrate a Server from Hyper-V to Plenit

Migrating a virtual machine from Hyper-V to Plenit has two halves: you prepare the import from the platform, which gives you the migration SFTP, and you export the machine from Hyper-V to upload its disk to that destination.

The process is guided, but there are several checks on the Hyper-V side that are worth doing first so the import does not fail.

<br>

> 👍 What you get
>
> The import prepared in Plenit and the VHDX disk of your Hyper-V machine uploaded to the SFTP, ready to deploy the target server.

<br>

### Before you begin

* Log in to the Plenit platform.
* Have access to the section **Migrations** within **Cloud Services**.
* Having a virtual machine in an environment **Microsoft Hyper-V** to migrate from.
* That the virtual machine has **DHCP enabled** on all its network adapters.

<br>

### Step 1. Prepare the migration in Plenit

In **Cloud Services → Migrations**, click **New migration** to open the wizard. If you have migrated before, this screen also shows the history.

#### 1.1 Source service and type

Select **Servers** as the service to migrate and, as server type, **Physical**.

{/\* 📸 SCREENSHOT 1 · wizard · Servers service and Physical type \*/}

![Selection of Servers and Physical type in the wizard](https://REEMPLAZA-URL/servidores-migracion-hyperv-01.png)

<br>

#### 1.2 Disk format and delivery method

Select **VHD – Disk Conversion** as the format (it is the one delivered by Hyper-V) and **copy via FTP** as the delivery method. Specify the **name of the disk to import** (the one the system will expect when uploading the data) and the **Display Name** (the name under which it will be identified in the console). Click **Next**.

{/\* 📸 SCREENSHOT 2 · wizard · VHD-Disk Conversion format, copy via FTP and disk names \*/}

![Disk format and delivery method via FTP](https://REEMPLAZA-URL/servidores-migracion-hyperv-02.png)

<br>

#### 1.3 Organization, subscription and deployment

Indicate the **organization**, the **subscription** and the **availability zone** where to deploy. If you do not have a subscription, you can create one here. To the question **Do you want to deploy a new server with the imported disks?**, the usual answer is **Yes** (or leave the uploaded image for later).

{/\* 📸 SCREENSHOT 3 · wizard · organization, subscription, zone and deployment option \*/}

![Selection of organization, subscription and deployment](https://REEMPLAZA-URL/servidores-migracion-hyperv-03.png)

<br>

#### 1.4 Target server

If you chose to deploy, specify the **server name** (spaces allowed), the **operating system**, the **sizing** (CPU and RAM) and the **network type** (standard or VPC; the most common is standard). Click **Finish**.

{/\* 📸 SCREENSHOT 4 · wizard · target server configuration \*/}

![Target server configuration](https://REEMPLAZA-URL/servidores-migracion-hyperv-04.png)

<br>

#### 1.5 SFTP connection data

When finished, Plenit shows the status (**preparing transfer** and, then, **waiting for transfer**) and the **SFTP connection details**: server, username, and password. Save them: you will need them to upload the disk.

{/\* 📸 CAPTURE 5 · migration summary with the SFTP connection details \*/}

![SFTP connection details in the migration summary](https://REEMPLAZA-URL/servidores-migracion-hyperv-05.png)

### Step 2. Export the machine from Hyper-V

<br>

> 🚧 Check this before exporting
>
> These points prevent the typical import failures:
>
> * The virtual machine must be **Generation 1**.
> * It must not have **snapshots**: if it does, delete them.
> * It must not have **mapped CD/DVD drives**: unmap them.
> * All network adapters with **DHCP** enabled.
> * In **Windows Server 2012**, defragment the machine before migrating: unlike 2016 and later, it does not do it automatically, and the image may end up larger than necessary.

<br>

#### 2.1 Start the export

In the Hyper-V console, select the virtual machine, right-click and **Export**. This is the recommended method versus copying the VHDX by hand, because the machine first goes through checks.

{/\* 📸 CAPTURE 6 · Hyper-V · context menu with the Export option \*/}

![Starting the export from the Hyper-V console](https://REEMPLAZA-URL/servidores-migracion-hyperv-06.png)

<br>

#### 2.2 Choose the path and wait

Indicate the **destination path** of the export and wait for it to finish. The time depends on the size of the machine, the host's CPU and RAM, and the destination disk IOPS.

{/\* 📸 CAPTURE 7 · Hyper-V · export path selection and progress \*/}

![Selection of the virtual machine export path](https://REEMPLAZA-URL/servidores-migracion-hyperv-07.png)

<br>

#### 2.3 Locate the VHDX

The export creates a structure with three folders: **Snapshots** (snapshots, if any), **Virtual Hard Disks** (the disks) and **Virtual Machines** (configuration files). The disk you are going to upload is in `Virtual Hard Disks`, for example:

```shell
C:\Datos\Exportacion\WS2022ADDS1\Virtual Hard Disks
```

{/\* 📸 CAPTURE 8 · Hyper-V · Virtual Hard Disks folder with the VHDX \*/}

![Export path with the VHDX disk](https://REEMPLAZA-URL/servidores-migracion-hyperv-08.png)

<br>

#### 2.4 Upload the VHDX to the SFTP

Upload the VHDX file to the migration SFTP using the Step 1 details, with a graphical client or from the command line:

```shell
sftp -P 22 <user>@<sftp-server>
put "C:\Datos\Exportacion\WS2022ADDS1\Virtual Hard Disks\disco.vhdx"
```

{/\* 📸 CAPTURE 9 · uploading the VHDX to Plenit's SFTP \*/}

![Upload of the VHDX to the migration SFTP](https://REEMPLAZA-URL/servidores-migracion-hyperv-09.png)

When the upload finishes, the import continues on the platform. You can track progress from the migration console and complete the final parameters so the server is ready for use.

<br>

### Conclusion

Migration from Hyper-V is guided, but what decides whether it works on the first try is the preparation on the hypervisor side: a Generation 1 machine, without snapshots or dangling CD/DVD drives and with DHCP on all adapters imports cleanly; any of those loose ends is what usually gets the process stuck.

With that checked and the VHDX uploaded to the SFTP the assistant gave you, the platform handles the rest until the server is deployed.


---

# 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/how-to/como-migrar-un-servidor-desde-hyper-v-a-cloud.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.
