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

# Glossary

The terms that appear throughout the migration guides, explained in a table.

Terms that appear throughout the migration guides. If you come across one and you're not sure what it means, look it up here.

| Term                        | What it is                                                                                                    |
| --------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Physical / virtual source   | If the source server is a physical machine or a machine already virtualized in a hypervisor or cloud.         |
| VHD / VHDX                  | Virtual hard disk formats (VHDX is the extended version), used by Hyper-V and other hypervisors.              |
| VMDK                        | VMware and VirtualBox disk format.                                                                            |
| QCOW2                       | Disk format for QEMU-based hypervisors.                                                                       |
| VDI                         | VirtualBox disk format.                                                                                       |
| RAW                         | Raw disk, bit-for-bit copy of the original.                                                                   |
| OVA                         | Package that bundles a virtual machine and its metadata into a single file.                                   |
| SFTP                        | Secure FTP, encrypted file transfer. This is the general delivery method.                                     |
| S3 Bucket / Storage Account | Object storage in Amazon (S3) or Azure (Storage Account), from which the disk can be published as a URL.      |
| Instance (EC2)              | A virtual machine in AWS.                                                                                     |
| DHCP                        | Automatic IP assignment. All network adapters on the machine must have it enabled to operate on the platform. |
| GRUB                        | Linux boot manager (GRUB Legacy or GRUB 2).                                                                   |
| BIOS / UEFI                 | The two boot firmware types. It is advisable to identify which one the source machine uses before migrating.  |
| System / data disk          | The main disk with the operating system is the system disk; the rest are data disks.                          |
| Volume Shadow Copy (VSS)    | Windows mechanism that allows generating a consistent image of the disk while the computer is running.        |
| Assisted migration          | Request for support from the Partner Success team to plan and carry out the migration, at no cost.            |

### Next steps

* Go back to [What migrations are](https://docs.plenit.com/docs-en/productos/migrations/concepts/what-they-are.md) for the big picture.
* Review the full journey in [The process.](https://docs.plenit.com/docs-en/productos/migrations/concepts/the-process.md)
* When you want to launch one, go to the [Quick Guide to the Migrations tool.](https://docs.plenit.com/docs-en/productos/migrations/quickstart.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 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/concepts/glossary.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.
