> 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-vmware-a-cloud.md).
# How to Migrate a Server from VMWare to Plenit
Migrating a VMware virtual machine to Plenit has three stages: you prepare the import from the platform, map the SFTP storage as a drive to upload the image directly, and export the machine from VMware to that drive.
Direct upload over SFTP saves you from first storing the image on your local infrastructure.
> 👍 What you get
>
> The import prepared in Plenit, the SFTP mounted as a disk drive, and the VMware machine exporting directly to that destination.
### Before you start
* Sign in to the Plenit platform with company administrator permissions or on a subscription of **Servers**.
* Have access to the section **Migrations** within **Cloud Services**.
* Having your VMware on-premises infrastructure with administrative permissions.
* That the virtual machine has **DHCP enabled** on all its network cards.
> 📘 Lighten the image before exporting
>
> Eject the mounted CD/DVD images and, if you want to reduce the size, uninstall the **VMware Tools**. The lighter the export, the less time it takes and the less likely it is to be interrupted.
### 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, **Virtual**.
{/\* 📸 CAPTURE 1 · wizard · Servers service and Virtual type \*/}
#### 1.2 Disk format and delivery method
Select **VHD – Disk Conversion** as the format and **copy via FTP** as the delivery method. Then fill in the disk data and the **Display name**, which will be the disk identifier in the console. Click **Create** and then **Next**.
{/\* 📸 CAPTURA 2 · asistente · formato VHD-Conversión Discos, copia mediante FTP y datos del disco \*/}
#### 1.3 Organization, subscription and deployment
Choose the **organization**, the **subscription** and the **availability zone** where you want to deploy. To the question **Do you want to deploy a new server with the imported disks?**, the usual thing is **Yes**, to chain the deployment in the same flow.
{/\* 📸 CAPTURE 3 · wizard · organization, subscription, zone and deploy option \*/}
#### 1.4 Destination server
If you chose to deploy, the wizard asks you for the **name**, the **operating system**, the **sizing** and the **network type** (standard or VPC). Click **Finish**.
{/\* 📸 CAPTURE 4 · wizard · destination server configuration \*/}
#### 1.5 SFTP connection data
When finished, Plenit shows the migration status (**preparing transfer** and then, **waiting for transfer**) and, on the same screen, the **SFTP connection details**: server, user and password. Save them: you will need them in Step 2.
{/\* 📸 CAPTURA 5 · resumen de la migración con servidor, usuario y contraseña SFTP \*/}
### Step 2. Map Plenit SFTP as a drive
For a large image, it's better to export it directly to Plenit's SFTP instead of saving it locally first. In this guide, it uses **SFTP Drive** from NSoftware, but any similar tool will do. If you'd rather not install anything, export the machine to your PC and upload it manually afterward.
#### 2.1 Install SFTP Drive
Download it from NSoftware (complete the product registration first) and install it with administrator privileges. During installation, use the same email and name you used to register the product. It's a good idea to restart when you're done, although it may work without doing so.
{/\* 📸 CAPTURA 6 · instalación de SFTP Drive con los datos de registro \*/}
#### 2.2 Create the mapped drive
Open SFTP Drive and click **New** to create the drive with the SFTP data from Step 1:
* **Drive Name**: connection name.
* **Drive Letter**: the drive letter.
* **Remote Host**: the SFTP server address.
* **Remote Port**: `22`.
* **Username / Password**: the credentials provided by Plenit.
* **Remote Folder**: leave **User's home folder**.
Click **Test SSH Connection** and, if everything goes well, **OK**.
> 📘 Accept the SSH keys if prompted
>
> When connecting, prompts may appear asking you to accept the SSH keys. Accept them: they are part of the key exchange that establishes the secure connection.
{/\* 📸 CAPTURE 7 · SFTP Drive · connection data and Test SSH Connection \*/}
### Step 3. Export the machine from VMware
#### 3.1 Open the export
In VMware, select the virtual machine to migrate, go into **Actions** and choose **Export**.
{/\* 📸 CAPTURA 8 · VMware · menú Acciones con la opción Exportar \*/}
#### 3.2 Choose the format and export
Select the format **.vmdk** and click **Export**. Save the export in the **mapped drive** from Step 2 to upload it directly to Plenit, or on your PC if you'd rather upload it by hand later.
> 🚧 Allow pop-ups
>
> For the export download to start, the browser must allow pop-ups and not have software that blocks them.
{/\* 📸 CAPTURA 9 · VMware · selección del formato .vmdk \*/}
#### 3.3 Check the progress
Verify that the export is progressing from **Recent Tasks** in VMware (the progress bar) or by checking the destination folder. When it finishes, the import continues on the platform until the server is deployed.
{/\* 📸 CAPTURA 10 · VMware · Tareas recientes con la barra de progreso de la exportación \*/}
### Conclusion
The migration from VMware chains three environments: Plenit's wizard gives you the SFTP, SFTP Drive turns it into a local drive, and VMware exports the `.vmdk` directly onto it.
That mapping is what saves you the intermediate step of downloading the image to your disk and uploading it again.
If you lighten the machine beforehand (CD/DVD out and, if you want, without VMware Tools) and leave the export pointing to the mapped drive, the upload and the import proceed in sequence without you having to touch anything in between.
---
# 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-vmware-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.