> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything.md).

# Path A: Retire everything

Retire every legacy feature at once after upgrading to YouDesign Command v26.1, with the Full Cleanup update set.

{% hint style="info" %}
**Follow** [**Retire everything**](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything/retire-everything.md) **for the cleanup.** It has every step in full: the migrations, the update sets and the manual steps. This page is a summary of the order.
{% endhint %}

Path A uses two update sets:

{% file src="/files/r5th8lgCHZ3rAU8Ldbom" %}

{% file src="/files/SVTQXCPExFDCFL0FsL5y" %}

1. Back up the legacy tables the cleanup drops, before you migrate. [Retire everything](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything/retire-everything.md) lists them in its first step.
2. [Migrate](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md#migrate-legacy-data) Lifecycles, Data Governance and Measures until each reads complete.
3. Give the holders of the five legacy roles their replacements. See [Roles the cleanup removes](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md#roles-the-cleanup-removes).
4. Commit **YCM V26.1 Legacy Logic Preservation**.
5. Commit **YCM V26.1 Full Cleanup**. Do not also commit the individual feature sets.
6. Do every manual step on [Retire everything](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything/retire-everything.md) right away. An update set cannot delete scheduled jobs, global settings or form sections, so those are done by hand on every instance.

Commit Logic Preservation **before** Full Cleanup: a cleanup committed without it makes shared scripts fail. Logic Preservation also switches on three shared calculation jobs that Full Cleanup leaves running, so delete them in the manual steps right after the commit.


---

# 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.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything.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.
