> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/virtual-machines/vm-manual-migration.md).

# Manual VM Migration

Instructions for manually migrating running VMs between host nodes in VergeOS, including single VM and bulk migration procedures.

Migrating a VM moves it from running on one host node to run on another, while keeping the VM running. Migration operations are handled automatically during VergeOS updates and when nodes are put into maintenance mode (provided there are adequate systems resources). VMs can also be manually migrated, when needed.

## Migrate a Single VM

1. Navigate to the individual **VM dashboard**.
2. Click **Migrate** (under Actions) from the left menu.
3. The default selection of --auto-- will automatically select a target node for migration based on resource balancing. You can also select a preferred node to select a specific node to which you would like to migrate.
4. Click the **Migrate** button to begin the process.

While the VM is migrating, the status field (top left) on the VM dashboard will reflect the migration progress. The status will return to "Running" after it has migrated to the destination. Additionally, the *Host Node* field will update to reflect the new node.

## Migrate Multiple VMs Simultaneously

1. Navigate to Machines > Virtual Machines (This brings up the VM listing.)
2. Select the desired VM(s). (Selected VMs will display a check mark.)
3. Click the **Migrate** button to begin the process.
4. The default selection of --auto-- will automatically migrate the VMs to nodes based on resource balancing. You can also select a preferred node. (When migrating multiple VMs at once, it may be likely that they will not all be able to migrate to a single preferred node.)
5. Click the **Migrate** button to begin the process.

The status field column (far left) will indicate when a VM is *Migrating* along with a progress percentage. The status will return to *Running* when a VM has finished migrating to the destination. The *Host Node* field (far right) also updates to reflect the new node on which the VM is running.


---

# 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.verge.io/run-the-platform/virtual-machines/vm-manual-migration.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.