> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/pe-add-on-simulink/appendix/project-migration-procedure.md).

# Project Migration Procedure

To migrate a VeriStand project to a newer version of the Power Electronics Add-On:

1. Save a backup of the original project by making a copy of the entire project folder on disk.
2. Follow the steps in the [**Uninstallation and Upgrade Procedure**](https://www.opal-rt.com/docs/pe-add-on-simulink/get-started/install-the-power-electronics-add-on/upgrade-or-uninstall-the-power-electronics-add-on.md) to upgrade the Power Electronics Add-On to the desired version. If multiple versions are to be skipped during the upgrade, it is not necessary to install intermediate versions.
3. Follow the procedures below, beginning with the section corresponding to the Add-On version used to create the original project.
4. Complete the steps in each subsequent section until the desired Power Electronics Add-On version is reached. Steps repeated across multiple sections can be skipped.

## Migrating from 1.15.X to 1.16.0 <a href="#inlineextension-migrating-from-1.15.x-to-1.16.0" id="inlineextension-migrating-from-1.15.x-to-1.16.0"></a>

### Project Dependency Update <a href="#project-dependency-update" id="project-dependency-update"></a>

1. Open the S*ystem Definition* of the existing project. This will automatically trigger a dependency update.
2. If a window opens asking for files to be relinked, click **Skip**. The files will automatically be relinked by the system definition update process.
3. **Save** and close the S*ystem Definition.*

The project is now compatible with version 1.16.0.


---

# 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://www.opal-rt.com/docs/pe-add-on-simulink/appendix/project-migration-procedure.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.
