> 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 Hyper-V virtual machine to Plenit has two parts: 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 beforehand so the import doesn't fail.
> 👍 What you get
>
> The import prepared in Plenit and the VHDX disk from your Hyper-V machine uploaded to the SFTP, ready to deploy the destination server.
### Before you start
* 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** from which to migrate.
* That the virtual machine has **DHCP enabled** on all its network adapters.
### Step 1. Prepare the migration in Plenit
In **Cloud Services → Migrations**, click **New migration** to open the wizard. If you have already migrated before, this screen also shows the history.
#### 1.1 Service and source type
Select **Servers** as the service to migrate and, as the server type, **Physical**.
{/\* 📸 CAPTURE 1 · wizard · Servers service and Physical type \*/}
#### 1.2 Disk format and delivery method
Select **VHD – Disk Conversion** in that format (it's the one provided by Hyper-V) and **copy via FTP** as the delivery method. Indicate the **name of the disk to import** (the one the system will expect when the data is uploaded) and the **Display name** (the name it will be identified by in the console). Click **Next**.
{/\* 📸 CAPTURE 2 · wizard · VHD-Disk Conversion format, copy via FTP and disk names \*/}
#### 1.3 Organization, subscription and deployment
Indicate the **organization**, the **subscription** and the **availability zone** where to deploy it. If you don't have a subscription, you can create one here. In response to the question **Do you want to deploy a new server with the imported disks?**, the usual thing is **Yes** (or leave the uploaded image for later).
{/\* 📸 CAPTURE 3 · wizard · organization, subscription, zone and deploy option \*/}
#### 1.4 Destination server
If you chose to deploy, indicate the **server name** (spaces are allowed), the **operating system**, the **sizing** (CPU and RAM) and the **network type** (standard or VPC; the most common is standard). Click **Finish**.
{/\* 📸 CAPTURE 4 · wizard · destination server configuration \*/}
#### 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'll need them to upload the disk.
{/\* 📸 SCREENSHOT 5 · migration summary with the SFTP connection details \*/}
### Step 2. Export the machine from Hyper-V
> 🚧 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 doesn't do it automatically, and the image may end up larger than necessary.
#### 2.1 Start the export
In the Hyper-V console, select the virtual machine, right-click, and **Export**. It is the recommended method instead of copying the VHDX by hand, because the machine undergoes checks first.
{/\* 📸 SCREENSHOT 6 · Hyper-V · context menu with the Export option \*/}
#### 2.2 Choose the path and wait
Indicate the **destination path** 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 IOPS of the destination disk.
{/\* 📸 SCREENSHOT 7 · Hyper-V · export path selection and progress \*/}
#### 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:\Data\Export\WS2022ADDS1\Virtual Hard Disks
```
{/\* 📸 SCREENSHOT 8 · Hyper-V · Virtual Hard Disks folder with the VHDX \*/}
#### 2.4 Upload the VHDX to the SFTP
Upload the VHDX file to the migration SFTP using the data from Step 1, with a graphical client or from the command line:
```shell
sftp -P 22 @
put "C:\Data\Export\WS2022ADDS1\Virtual Hard Disks\disk.vhdx"
```
{/\* 📸 SCREENSHOT 9 · uploading the VHDX to the Plenit SFTP \*/}
When the upload finishes, the import continues on the platform. You can follow the progress from the migrations console and complete the final parameters so the server becomes operational.
### Conclusion
Migration from Hyper-V is guided, but what decides whether it works the first time is the preparation on the hypervisor side: a Generation 1 machine, with no snapshots or dangling CD/DVD drives and DHCP on all adapters, imports cleanly; any of those loose ends is usually what gets the process stuck.
With that checked and the VHDX uploaded to the SFTP the assistant gave you, the platform takes over 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 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/how-to/como-migrar-un-servidor-desde-hyper-v-a-cloud.md?ask=&goal=
```
`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.