> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/general-virtual-machine-management/convert-a-virtual-machine.md).

# Convert a Virtual Machine

**prlctl convert** <*path*>

This command is used to convert a third-party virtual machine to a Parallels virtual machine. The <*path*> parameter specifies a path to the original virtual machine.

{% hint style="info" %}
**Note**: Importing, converting, and running previously created virtual machines from another virtualization application is not available on Apple Silicon Macs.
{% endhint %}

#### Optional Parameters

**--dst** <*path*>

A path where the converted virtual machine files will be stored. If omitted, the default virtual machine location will be used.

**--force**

If included, the virtual machine conversion will continue even if the guest OS cannot be identified.

{% hint style="info" %}
**Note**: The following third-party virtual machines and disks are supported:

* Microsoft Hyper-V
* Microsoft Virtual PC
* Virtual Box
* VMware
  {% endhint %}


---

# 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.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/general-virtual-machine-management/convert-a-virtual-machine.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.