> 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/concepts/source.md).

# Physical or Virtual Source

The migration assistant asks you, almost at the beginning, whether the source server is **physical** or **virtual**.

This choice determines the disk format and the workflow, so it is worth being clear about it before starting.

### Virtual source

This is the case when you start from a machine that already lives in a hypervisor or in another cloud: VMware, Hyper-V, an AWS instance, an Azure VM, etc. 

The disk exists as a virtual file (VMDK, VHD, VHDX, QCOW2, VDI) and what you do is export it and upload it to Plenit.

You choose **Virtual** when you migrate, for example, a VMware VM, an AWS instance, or an Azure machine.

### Physical source

This is the case when you start from a physical server, with no virtualization layer underneath. Here you first need to generate an image of the physical disk with a partner-side tool (for example, Disk2vhd for Windows, which produces a VHD) or start from an Acronis backup.

You choose **Physical** when you migrate an on-premises Windows server with Disk2vhd or with an Acronis backup, or a server from Hyper-V exported as a copy.

> #### 📘 The practical rule
>
> If the disk is already a virtual file that you can export, it is **virtual**. If you have to generate the image from a physical machine or from a backup, it is **physical**.

### Why getting it right matters

The source type opens a different path in the wizard: it changes the formats it offers you and how the disk is delivered. Choosing incorrectly forces you to relaunch the migration, so it is the first decision worth confirming.

### Next steps

* Choose how to deliver the disk in [Disk formats.](/docs-en/productos/migrations/concepts/formats.md)
* See the delivery methods in [Transfer modes.](/docs-en/productos/migrations/concepts/transfer.md)


---

# 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/concepts/source.md?ask=<question>&goal=<endgoal>
```

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