> 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 an 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 of **Partner Success** supports you in the migration of **Servers** or **Remote Desktop**.

<br>

> 👍 What you get
>
> A migration request registered and the appointment coordinated with Partner Success, without leaving the platform's usual flow.

<br>

### Before you begin

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

<br>

> ❗️ Create the destination organization first
>
> The form will ask 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 exit and come back.

<br>

### Step 1. Access Assisted Migrations

In the side menu, expand **Cloud Services** and go into **Migrations**. Open **Assistance Request** and click the button with the same name, in the top right.

![Access to Assistance Request from Cloud Services › Migrations](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-5a7dea811e9ce77cd6b3e1a111f1f766ea5c7da3%2FCAPTURA%201%20%C2%B7%20Cloud%20Services%20%E2%80%BA%20Migrations%20%E2%80%BA%20Solicitud%20de%20Asistencia%20con%20el%20bot%C3%B3n.png?alt=media)

<br>

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

![Service selection to migrate](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-0c8fce825260f7e071579bd9eb3a9c315f826573%2FCAPTURA%202%20%C2%B7%20selecci%C3%B3n%20del%20servicio%20a%20migrar.png?alt=media)

<br>

#### 2.2 Destination location

Indicate the availability zone or location to which you want to migrate the environment.

![Selection of destination location](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-3e5ddc67d397224fc05d62a7cd2db0cbe01113c2%2FCAPTURA%203%20%C2%B7%20selecci%C3%B3n%20de%20la%20ubicaci%C3%B3n%20de%20destino.png?alt=media)

<br>

#### 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 easier if you come with the number of servers and their resources (CPU, RAM, and disk) already noted down.

![Definition of the environment characteristics](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-25ffa346f8ac231e83b10c8f4bd4f7bd8bf942e6%2FCAPTURA%204%20%C2%B7%20caracter%C3%ADsticas%20del%20entorno%20\(n%C2%BA%20de%20servidores%20y%20especificaciones\).png?alt=media)

<br>

#### 2.4 VPN and contact

Indicate whether a **Site-to-site VPN** VPN will be needed on the destination machine and enter the details of the person who will coordinate the migration with Partner Success. Click **Next**.

<br>

> 📘 If you check VPN, be clear about the scenario
>
> You have the details in [How to create a site-to-site VPN tunnel](https://docs.plenit.com/productos/servers/how-to/how-to-create-a-site-to-site-vpn-tunnel).

<br>

![VPN and contact person indication](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-195ec4581b7446d8c55380bd35a1d1f6f2803619%2FCAPTURA%205%20%C2%B7%20opci%C3%B3n%20de%20VPN%20site-to-site%20y%20datos%20de%20contacto.png?alt=media)

<br>

#### 2.5 Date and time

Select the date and time when you want to perform the assisted migration and click **Next**.

![Selection of migration date and time](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-87d53db0533c3855d99bd678b528f7709c3cb737%2FCAPTURA%206%20%C2%B7%20calendario%20de%20fecha%20y%20hora%20de%20la%20migraci%C3%B3n.png?alt=media)

<br>

#### 2.6 Destination organization

Indicate the organization to which the environment will be migrated and continue. When you save, the platform sends the request to Partner Success for review and coordination.

![Selection of the destination organization and submission of the request](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-17d12f11b2afd2eb6df6c28a2b4f0f01128c9ad4%2FCAPTURA%207%20%C2%B7%20selecci%C3%B3n%20de%20la%20organizaci%C3%B3n%20destino%20y%20confirmaci%C3%B3n%20de%20env%C3%ADo.png?alt=media)

<br>

### Conclusion

Migrations are a delicate process, and centralizing the request in the platform with the support of a specialist team reduces the risk that something gets left behind. Assisted Migrations does not perform the migration for you: what it does is leave the intervention booked and coordinated with Partner Success, 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 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-solicitar-ayuda-para-migrar-un-servidor-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.
