> For the complete documentation index, see [llms.txt](https://docs.trilio.io/openstack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/openstack/t4o-5.x/user-guide/vmware-migration/migration-plans.md).

# Migration Plans

## Definition

A **Migration Plan** is a structured and pre-defined set of instructions that outlines the process and details for migrating Virtual Machines (VMs) from a VMware environment to OpenStack. It serves as a blueprint for orchestrating the migration, including the selection of VMs, and managing the overall migration workflow. Each plan may have a name and may include a description to provide additional context and easy identification. Migration Plans are created and managed by users to ensure a systematic and controlled migration process.

## Creation

To initiate the migration process, users must create a Migration Plan:

* Provide a **name** and **description** for the plan.
* Select the vCenter from which the VMs are to be migrated.
* Using the Manage VMs functionality, select VMs from the list of VMware VMs. This list does not include the VMs that are already part of a Migration Plan.

## Update and Changes

Any modification to the plan requires users to:

* Revisit the plan details for updates.
* Execute the "[Discover VMs](#discover-vms)" call to fetch and update resource information in the Trilio service DB.

{% hint style="warning" %}
Failure to perform a "Discover VMs" after plan modification can lead to unexpected outcomes.
{% endhint %}

## Discover VMs

**Discover VMs** is an operation within the migration process that involves querying and collecting resource information from VMware for the VMs included in a Migration Plan. This operation is crucial for maintaining up-to-date details about the VMs, such as configuration, networking, and storage.

After creating or modifying a Migration Plan, users must:

* Trigger the "Discover VMs" operation.
* This operation collects resource information of VMs in the plan from VMware and stores it in the WLM service DB.
* "Discover VMs" must be called every time the plan is updated to ensure accurate information for migration. It ensures accuracy in subsequent migration steps and helps prevent unexpected outcomes due to outdated information.

## Deletion

The user can also delete a Migration Plan if required. But it will need all the initiated migrations to be deleted. Refer to [this page](/openstack/t4o-5.x/user-guide/vmware-migration/migrations.md#deletion) for deleting the initiated migrations for more information.

[How-to Guide: Creating a Migration Plan](/openstack/t4o-5.x/user-guide/vmware-migration/migration-plans/how-to-guide-creating-a-migration-plan.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:

```
GET https://docs.trilio.io/openstack/t4o-5.x/user-guide/vmware-migration/migration-plans.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.