> 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 via SFTP saves you from having to store the image first on your local infrastructure.

<br>

> 👍 What you get
>
> The import prepared in Plenit, the SFTP mounted as a drive, and the VMware machine exporting directly to that destination.

<br>

### Before you begin

* Log in to the Plenit platform with company administrator permissions or on a subscription of **Servers**.
* Have access to the section **Migrations** within **Cloud Services**.
* Have your on-premises VMware infrastructure with administrative permissions.
* That the virtual machine has **DHCP enabled** on all its network adapters.

<br>

> 📘 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.

<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, **Virtual**.

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

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

<br>

#### 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 details and the **Display Name**, which will be the disk identifier in the console. Click **Create** and then **Next**.

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

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

<br>

#### 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 answer is **Yes**, to chain the deployment in the same flow.

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

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

<br>

#### 1.4 Target 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**.

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

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

<br>

#### 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, username and password. Save them: you need them in Step 2.

{/\* 📸 SCREENSHOT 5 · migration summary with SFTP server, username and password \*/}

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

<br>

### Step 2. Map Plenit SFTP as a drive

For a large image, it's best to export it directly to Plenit's SFTP instead of saving it locally first. In this guide, we use **SFTP Drive** from NSoftware, but any similar tool will do. If you prefer not to install anything, export the machine to your PC and upload it manually afterward.

<br>

#### 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 finished, although it may work without doing so.

{/\* 📸 SCREENSHOT 6 · SFTP Drive installation with registration details \*/}

![SFTP Drive installation with registration details](https://REEMPLAZA-URL/servidores-migracion-vmware-06.png)

<br>

#### 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 address of the SFTP server.
* **Remote Port**: `22`.
* **Username / Password**: the credentials provided by Plenit.
* **Remote Folder**: leave **User's home folder**.

Click **Test SSH Connection** and, if all goes well, **OK**.

<br>

> 📘 Accept the SSH keys if prompted
>
> When connecting, prompts to accept SSH keys may appear. Accept them: they are part of the key exchange that establishes the secure connection.

<br>

{/\* 📸 SCREENSHOT 7 · SFTP Drive · connection data and Test SSH Connection \*/}

![Mapping the SFTP as a drive with SFTP Drive](https://REEMPLAZA-URL/servidores-migracion-vmware-07.png)

<br>

### Step 3. Export the machine from VMware

#### 3.1 Open the export

In VMware, select the virtual machine to migrate, go to **Actions** and choose **Export**.

{/\* 📸 SCREENSHOT 8 · VMware · Actions menu with the Export option \*/}

![Export option in the VMware actions menu](https://REEMPLAZA-URL/servidores-migracion-vmware-08.png)

<br>

#### 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 prefer to upload it manually afterward.

<br>

> 🚧 Allow pop-ups
>
> For the export download to start, the browser must allow pop-ups and not have software that blocks them.

<br>

{/\* 📸 SCREENSHOT 9 · VMware · selection of the .vmdk format \*/}

![Export in .vmdk format from VMware](https://REEMPLAZA-URL/servidores-migracion-vmware-09.png)

<br>

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

{/\* 📸 SCREENSHOT 10 · VMware · Recent Tasks with the export progress bar \*/}

![Export progress in VMware Recent Tasks](https://REEMPLAZA-URL/servidores-migracion-vmware-10.png)

<br>

### Conclusion

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 (remove the CD/DVD and, if you want, without VMware Tools) and leave the export pointing to the mapped drive, the upload and import are chained together 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 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-vmware-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.
