> 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-servidores-windows-de-on-premise-a-cloud.md).
# How to Migrate On-premise Windows Servers to Plenit via Acronis
Plenit supports migrating Windows machines that have a backup of **Acronis**. In this guide, the method followed is **FTP**: you prepare the import on the platform, upload the Acronis file to the migration SFTP, and complete the restore from the server console with the Acronis bootable agent.
Where it differs from the cloud method, we point it out..
> 👍 What you get
>
> The migrated Windows server to Plenit from its Acronis backup, restored onto the destination machine from the console.
### Before you start
* Log in to the Plenit platform.
* Have access to the section **Migrations** within **Cloud Services**.
* Have a physical machine with **Windows** from which to migrate and a **Acronis account**.
* That the 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 Format, delivery method, and disk data
As the format, select **Acronis Agent**. As the delivery method, you have two recommended options:
* **FTP Client**: you upload the file via FTP yourself (the one this guide follows).
* **Acronis Agent**: delivery goes through the Acronis cloud method.
Select **FTP Client** and fill in the disk data: the **partition type** (usually *System*), the **name of the disk to import** and the **disk size**. Click **Next**.
{/\* 📸 CAPTURE 2 · wizard · Acronis Agent format, FTP Client method, and disk data \*/}
#### 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 it here. To the question **Do you want to deploy a new server with the imported disks?**, the usual thing is **Yes**.
{/\* 📸 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 **FTP connection data**: server, username, and password. Save them for Step 2.
{/\* 📸 CAPTURE 5 · migration summary with FTP connection data \*/}
### Step 2. Upload the Acronis backup to the FTP
Upload the backup file of Acronis (`.tib` or `.tibx`) to the Plenit FTP with a client like WinSCP or FileZilla, using the address, username, and password from Step 1. The time depends on the file size and your connection.
{/\* 📸 CAPTURE 6 · FTP client (WinSCP/FileZilla) uploading the .tib/.tibx \*/}
When the upload finishes, the Migrations console shows the server you're migrating with the button **VNC Console Access**. Click it to continue.
{/\* 📸 CAPTURE 7 · migrations console with the VNC Console Access button \*/}
### Step 3. Restore from the Acronis agent
When you open the console, the Acronis ISO loads and the machine is prepared. It goes through several waiting screens depending on the image size.
> 📘 The at sign (@) in the console
>
> If you need to type accounts with `@`, switch the keyboard to English (UK) and use Shift + the key next to ñ. Check that the character appears correctly before continuing.
#### 3.1 Manage the computer locally and choose Recover
When **Acronis Bootable Agent**, click **Manage this computer locally** and, in the next window, **Recover**.
{/\* 📸 CAPTURE 8 · Acronis · Manage this computer locally and Recover option \*/}
#### 3.2 Select the FTP source
In **Recover data**, click **Select the data** and then **Browse**. Choose **FTP Servers** as the source and add the **path** of the Plenit FTP from Step 1. Click **OK** and enter the **username and password**.
> ❗️ You only have three password attempts
>
> The console blocks the migration after three failed attempts. To avoid mistakes, type the password by pasting it first next to the username, copy it from there, and paste it into its field. If it gets blocked, contact support.
{/\* 📸 CAPTURE 9 · Acronis · FTP Servers source with path and credentials \*/}
> 📘 If you had chosen Acronis Cloud
>
> With the cloud method, here you would restore directly from Acronis Cloud and you would have skipped Step 2 (the upload via FTP).
#### 3.3 Choose the backup and the disk
Go to the path **Uploads** and enter the access password. Select the backup and, in **Backup contents**, choose **Disks** checking the **Disk 1**. Click **OK**, confirm the **Disk 1** destination disk and **OK** again.
{/\* 📸 CAPTURE 10 · Acronis · selection of the backup and disk to restore \*/}
#### 3.4 Wait for deployment
The operation shows its progress and, when it finishes, the machine boots. From there, complete the final configuration tasks to make it operational and put it into production.
{/\* 📸 CAPTURE 11 · Acronis · recovery progress and machine boot \*/}
### Conclusion
This migration is the most manual of the set because the actual restoration happens inside the console, with the Acronis bootable agent recovering the backup from the FTP. Two details avoid the usual pitfalls: take care when entering the password (there are only three attempts before it locks) and be clear about the branch in Step 1, because choosing **FTP Client** or **Acronis Agent** determines whether you upload the `.tib` or recover it from the cloud. With the backup properly uploaded and the correct disk selected, the machine ends up booting on its own.
---
# 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-servidores-windows-de-on-premise-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.