> 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-c-retire-some-features.md).

# Path C: Retire some features

Retire legacy features one at a time after upgrading to YouDesign Command v26.1, with an update set per feature.

{% hint style="info" %}
**Follow the page of each feature you retire for the cleanup.** Each one has every step in full: the migration, the update set and the manual steps. This page is a summary of the order.
{% endhint %}

Path C uses **YCM V26.1 Legacy Logic Preservation**, plus the cleanup set of each feature you retire. Each feature's page has its own set.

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

1. Commit **YCM V26.1 Legacy Logic Preservation**, once.
2. For each feature you retire, follow its page. Each one backs up the legacy tables, migrates, commits its own cleanup set and does its manual steps:
   * [Data Governance](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/data-governance.md)
   * [Lifecycles](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/lifecycle.md)
   * [Measures](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/measures.md)
   * [TIME Analysis](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/time-analysis.md)
   * [Dashboards](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/retire-dashboards.md), last, and only once every other feature is retired

The four feature sets are independent: commit them in any order, now or later.

Do not commit Logic Preservation again between features. Committing it after a cleanup switches that feature's scheduled jobs back on, and they then run against data the cleanup removed. It also puts the **Lifecycles**, **KPIs** and **TIME Analysis** sections back on the **Business Application** form, where they show as empty blocks once their feature is retired. If you ever have to commit it again, first remove the retired features' jobs from the set. Then, for each retired feature, repeat the step that removes its form sections: [Lifecycles](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/lifecycle.md), [Measures](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/measures.md) or [TIME Analysis](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/time-analysis.md).

**Legacy dashboards** go only when you retire every legacy feature. **YCM V26.1 Legacy Dashboards Cleanup** deletes all 27 legacy dashboards, including Data Quality, Financials, TPM, Portfolios and Strategic Planning, and the 15 legacy Platform Analytics dashboards, whatever you keep. Skip it while any legacy feature stays: each feature set already removes its own broken dashboard tiles.


---

# 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-c-retire-some-features.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.
