> 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-solicitar-ayuda-para-migrar-un-servidor-a-cloud.md).
# How to Request Assisted Migration
A migration may require technical coordination, prior validation, and support during execution.
With **Assisted Migrations** you book an intervention from the platform itself so that the team at **Partner Success** supports you in the migration of **Servers** or **Remote Desktop**.
> 👍 What you get
>
> A registered migration request and the appointment coordinated with Partner Success, without leaving the platform's usual workflow.
### Before you start
* Log in to the platform with an active organization.
* Have identified the server or environment you want to migrate.
* Be able to access the section **Migrations** within **Cloud Services**.
> ❗️Create the target organization first
>
> The form will ask you for the organization to which the environment will be moved, so create it before starting the request. If you reach that step without it, you'll have to leave and come back.
### Step 1. Access Assisted Migrations
In the side menu, expand **Cloud Services** menu and go to **Migrations**. Open **Assistance Request** and click the button of the same name, at the top right.
{/\* 📸 SCREENSHOT 1 · Cloud Services › Migrations › Assistance Request with the button \*/}
### Step 2. Complete the request
The wizard takes you through six screens.
#### 2.1 Service to migrate
Choose the type of environment or service you want to migrate and click **Next**.
{/\* 📸 SCREENSHOT 2 · selection of the service to migrate \*/}
#### 2.2 Destination location
Indicate the availability zone or location to which you want to migrate the environment.
{/\* 📸 SCREENSHOT 3 · selection of the destination location \*/}
#### 2.3 Environment characteristics
Enter the technical information of the environment, including the number of servers and their specifications, and click **Next**.
> 📘 Have the inventory at hand
>
> This step is faster if you come with the number of servers and their resources (CPU, RAM and disk) already noted down.
{/\* 📸 SCREENSHOT 4 · environment characteristics (number of servers and specifications) \*/}
#### 2.4 VPN and contact
Indicate whether a **Site-to-site VPN** site-to-site VPN will be needed on the destination machine and enter the contact details of the person who will coordinate the migration with Partner Success. Click **Next**.
> 📘 If you select VPN, be clear about the scenario
>
> You have the details in [How to create a site-to-site VPN tunnel](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-migraciones/servicios-cloud-migraciones-how-to/servicios-cloud-servidores-tunel-vpn-site-to-site/README.md).
{/\* 📸 SCREENSHOT 5 · site-to-site VPN option and contact details \*/}
#### 2.5 Date and time
Select the date and time when you want to carry out the assisted migration and click **Next**.
{/\* 📸 SCREENSHOT 6 · migration date and time calendar \*/}
#### 2.6 Target organization
Indicate the organization to which the environment will be migrated and continue. When saving, the platform sends the request to Partner Success for review and coordination.
{/\* 📸 SCREENSHOT 7 · selection of the target organization and confirmation of submission \*/}
### Conclusion
Migrations are a delicate process, and centralizing the request on the platform with the support of a specialist team reduces the risk of something being lost along the way. Assisted Migrations does not carry out the migration for you: what it does is leave the intervention with Partner Success reserved and coordinated, with all the environment data up front, so that when the time comes everything is ready.
---
# 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-solicitar-ayuda-para-migrar-un-servidor-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.