> 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.md).

# Upgrade from v26.0 to v26.1

After upgrading to v26.1, choose whether to retire the legacy Data Governance, Lifecycle, Measures, TIME Analysis and dashboard features, keep them, or retire some of them, using the v26.1 cleanup upd

Version 26.1 completes the new Command features that replace five legacy ones: Data Governance, Lifecycles, Measures (Cost and KPI), TIME Analysis and the legacy dashboards. Upgrading to 26.1 removes nothing. Afterward you decide, feature by feature, whether to retire the legacy version, and you do it with update sets you apply yourself.

This page is for ServiceNow administrators. Read it in full before committing any update set.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-c3f2171e0911f092ef100f4bc2dc3c08ed0f09e2%2Fupgrade-v260-to-v261-flow.svg?alt=media" alt="Five steps in a row: upgrade to v26.1, back up the legacy tables, migrate Lifecycles, Data Governance and Measures, check the data is in Command, then clean up with Logic Preservation and the cleanup sets. If the check fails, a dashed arrow leads back to migrate. A side note under the first step says to stop there to keep the legacy features."><figcaption><p>The upgrade from v26.0 to v26.1, step by step</p></figcaption></figure>

## Choose your path

Decide this with your team. All three paths are supported, and you can keep legacy features now and retire them later.

|                 | [Path A: Retire everything](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-a-retire-everything.md) | [Path B: Keep legacy features](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-b-keep-legacy-features.md) | [Path C: Retire some features](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features.md) |
| --------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Best for**    | Customers who have moved fully to the new Command features                                                                | Customers who still rely on the legacy features                                                                                 | Customers ready for some features but not others                                                                                |
| **What you do** | Migrate every feature, then commit Logic Preservation and Full Cleanup                                                    | Commit Logic Preservation, or nothing at all                                                                                    | Migrate and retire one feature at a time                                                                                        |
| **Reversible?** | No. Legacy data not migrated is lost.                                                                                     | Yes. Retire features later with Path C or A.                                                                                    | Per feature: no, once its set is committed                                                                                      |

{% hint style="danger" %}
**Two rules that prevent data loss**

1. **Commit Logic Preservation first**, before any cleanup set, on every instance. A cleanup set committed without it makes shared scripts fail on their next run.
2. **Migrate before you clean up** Lifecycles, Data Governance and Measures. Their cleanup sets drop the legacy tables. Backing an update set out brings the tables back empty: the rows are gone.

Take a backup or clone of production before you start, and try your path on a sub-production instance first.
{% endhint %}

## Before you start

* Update the app to v26.1. See [Updating](https://docs.ins-pi.com/command/get-the-app/updating.md).
* Have your license file from the ins-pi team ready. Command 26.1 opens only once a license is installed. See [Install your license](https://docs.ins-pi.com/command/administration/license.md#install-your-license).
* Choose your path. Each update set is ready to download on the page where you commit it.
* Back up the legacy tables before you migrate. Each retire page lists the tables its set drops in its first step, with how to export them and put them back.
* Give people their new roles. Some cleanup sets delete legacy roles: see [Roles the cleanup removes](#roles-the-cleanup-removes).
* Know how to apply an update set: in ServiceNow open **Retrieved Update Sets**, click **Import Update Set from XML**, upload the file, click **Preview Update Set**, then **Commit Update Set**.
* In the URLs on these pages, replace `<instance>` with your instance name.

## The update sets

| Update set                                   | What it does                                                                                                                    | Path                                   |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
| **YCM V26.1 Legacy Logic Preservation**      | Makes the shared scripts safe when a feature is removed. Deletes nothing and changes nothing on its own.                        | A, B (optional), C                     |
| **YCM V26.1 Legacy Data Governance Cleanup** | Retires legacy Data Quality.                                                                                                    | C                                      |
| **YCM V26.1 Legacy Lifecycle Cleanup**       | Retires legacy Lifecycles.                                                                                                      | C                                      |
| **YCM V26.1 Legacy Measures Cleanup**        | Retires legacy Cost and KPI.                                                                                                    | C                                      |
| **YCM V26.1 Legacy Time Scores Cleanup**     | Retires the classic TIME Analysis.                                                                                              | C                                      |
| **YCM V26.1 Legacy Dashboards Cleanup**      | Retires all 27 legacy dashboards, the 15 legacy Platform Analytics dashboards and the content of the legacy UPM·X portal pages. | C, only when every legacy feature goes |
| **YCM V26.1 Full Cleanup**                   | Everything above except Logic Preservation, in one set, plus the legacy relationship roles.                                     | A                                      |

## Roles the cleanup removes

Some cleanup sets delete legacy roles that Command no longer uses: Command Editors now change lifecycles and relationships, and a persona's **Admin Settings** tab now decides who administers Data Governance. Anyone who holds one of these roles loses what it gave them when the set is committed, so give them its replacement **before** you commit that set.

| Role                               | Deleted by                            | Give its holders instead                                                                                                                                                               |
| ---------------------------------- | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `x_inpgh_upmx.lfc_editor`          | Lifecycle Cleanup, Full Cleanup       | **Command Editor** (`x_inpgh_upmx.editor`)                                                                                                                                             |
| `x_inpgh_upmx.dq_admin`            | Data Governance Cleanup, Full Cleanup | **Command Editor**, and a persona that opens **Data Governance** on its **Admin Settings** tab. See [Personas](https://docs.ins-pi.com/command/the-portal/personas.md#admin-settings). |
| `x_inpgh_upmx.report_reader`       | Dashboards Cleanup, Full Cleanup      | **Command Reader** (`x_inpgh_upmx.reader`)                                                                                                                                             |
| `x_inpgh_upmx.relationship_editor` | Full Cleanup                          | **Command Editor** (`x_inpgh_upmx.editor`)                                                                                                                                             |
| `x_inpgh_upmx.relationship_reader` | Full Cleanup                          | **Command Reader** (`x_inpgh_upmx.reader`)                                                                                                                                             |

To see who holds a role, open these lists, replacing `<role>` with the role's name:

* Users: `https://<instance>.service-now.com/sys_user_has_role_list.do?sysparm_query=role.name%3D<role>`
* Groups: `https://<instance>.service-now.com/sys_group_has_role_list.do?sysparm_query=role.name%3D<role>`

Give the replacement to the group where you can, as with every Command role.

## Migrate legacy data

Lifecycles, Data Governance and Measures each have a migration page in Command that carries their legacy data into the new features. TIME Analysis needs none: its scores are calculated, not stored. Migrate the features in any order.

1. Open Command as a Command administrator.
2. Click **Open menu** (☰) in the header and expand **Migration** (*Legacy data to Command*).
3. Choose the feature. It opens in a tab named after it, such as *Migration · Lifecycles*.
4. Click the button on each step card in turn, and wait for its bar to reach 100%. Keep the browser tab open while a step runs.

A step is complete when it is marked **Done** and its button reads **Re-check**; the top of the page then reads **Ready for legacy cleanup**. Each migration is safe to run more than once: run it again just before you commit that feature's cleanup set, to catch anything added since.

| Feature             | Steps on the page                                                                                | What is carried                                                                                                                              |
| ------------------- | ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Lifecycles**      | **Definitions and phases**, **Lifecycle data**, then **Forms show Command**                      | The lifecycle definitions and their dated phases                                                                                             |
| **Data Governance** | **Charters and rules**, **Verifications** (**Carry verifications**), then **Forms show Command** | Charters, rules, score families and the attestation dates. Reminder settings are not carried; set them up again in Data Governance settings. |
| **Measures**        | **Migrate definitions**, then **Migrate values**                                                 | Cost and KPI definitions and their history                                                                                                   |

When a feature's legacy tables are gone, its page leaves the **Migration** menu, and **Migration** disappears once nothing is left to migrate.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-b88975e628f41287b85f39e46055f621bbd7f357%2Fcommand-migration-measures.png?alt=media" alt="The Measures migration page, with the definitions and values steps both at 100% and their buttons reading Re-check."><figcaption><p>A completed Measures migration</p></figcaption></figure>

## Good to know

* On a fresh 26.1 install (not an upgrade), the cleanup sets create the old scheduled jobs as inactive records: 12 for Data Governance and 7 for Lifecycles. The manual steps on the feature pages remove them.
* The update brings Command's access rules up to date by itself; you run no script. **Command Reader** can now read the configuration behind the Global Settings sections, any **Command Editor** can change the data editors work on (measure values, planned changes, lifecycle states), and changing a section's configuration still needs **Command Admin**, or a persona that opens the section on its **Admin Settings** tab. If you changed Command's access rules on your instance, check the update's skipped records afterward.

## Related

* [Updating](https://docs.ins-pi.com/command/get-the-app/updating.md)
* [Upgrade from v4.8 to v26.0](https://docs.ins-pi.com/command/get-the-app/upgrade-v48-to-v260.md)
* [Release Notes](https://docs.ins-pi.com/command/reference/release-notes.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 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.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.
