# Migrating Virtual Machines | Cycle.io

Canonical URL: https://cycle.io/docs/platform/migrating-virtual-machines

## Migrating Virtual Machines.

[Virtual machines](https://cycle.io/docs/platform/introduction-to-virtual-machines) are able to be migrated between servers that support hypervisors **in the same region as the existing virtual machine**.

##### Caution

At this time, virtual machine migrations **are not live**. A new copy of the virtual machine will be started on the target server before traffic is redirected.

Under the hood, Cycle uses the same system to migrate a virtual machine as a [container instance](https://cycle.io/docs/platform/migrating-instances). This means that volumes attached to the virtual machine will also be migrated to the target instance.

### Target Server Requirements

A virtual machine may only be migrated to a server in the same region as the existing virtual machine, and to a server that supports the **hypervisor** feature. Virtual machines may only run on servers with this feature, and not all servers supported by Cycle have the hypervisor feature.

### Network Considerations

When migrating a virtual machine, it will maintain its assigned IP addresses. As IP addresses are attached to the [gateway service](https://cycle.io/docs/platform/gateway-service), the virtual machine is able to migrate freely between servers in the same region (hence the server restriction) without causing any change to networking.

### Migrate Virtual Machines on Cycle

[##### Portal](https://cycle.io/docs/portal/virtual-machine-dashboard#host-server)[##### API](https://cycle.io/docs/api/platform/tag/instances/POST/v1/containers/%7BcontainerId%7D/instances/%7BinstanceId%7D/tasks#tag/instances/POST/v1/containers/{containerId}/instances/{instanceId}/tasks)

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
