> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-3.-run-user-acceptance-tests-uat-in-a-multi-tenant-deployment-using-the-migration-wizard/incidents-and-indicators-multi-tenant.md).

# Incidents and Indicators - Multi-Tenant

This topic is relevant only for development and child tenants.

If you select migrate incidents and indicators in the pre-migration wizard, all incident and indicator data is copied to each tenant in Cortex XSOAR 8.

1. Review the **Incidents** and **Indicators** pages in Cortex XSOAR 8 and view the copied incidents and indicators.

   Most of the features in Cortex XSOAR 6 are identical to Cortex XSOAR 8. Some changes for Cortex XSOAR 8 include:

   * Related Incidents and Summary tabs have been removed.
   * Some War Room filters have been changed.
   * You cannot manually share indicators.
2. To see incident/indicator types, layouts, and fields, go to **Settings & Info** → **Settings** → **Object Setup** and then select **Incidents** or **Indicators**.

{% hint style="info" %}

### Note

Active incidents are paused on Cortex XSOAR 8, as ongoing investigations are still conducted in the Cortex XSOAR 6 instance, which remains active throughout the User Acceptance Testing (UAT) phase, until the switchover date.
{% endhint %}

At the switchover date:

* Incident data is migrated (subject to the retention policy). Incidents created up to 3 months before the initial sync date are resynced.
* All indicator data is migrated and resynced.
* Any active incidents in Cortex XSOAR 6 are set to active status in Cortex XSOAR 8.

Incidents and indicators created in Cortex XSOAR 8 during the UAT phase are removed at the switchover date. This includes any changes to incidents/indicators in Cortex XSOAR 8 since the UAT phase began.

{% hint style="info" %}

### Note

If you elect not to migrate incident and indicator data, any incidents created or edited on the Cortex XSOAR 8 tenant during the UAT phase are removed at the switchover date. You can continue working on active incidents on Cortex XSOAR 6 until EoL or the end of your contract term (whichever comes first).
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-3.-run-user-acceptance-tests-uat-in-a-multi-tenant-deployment-using-the-migration-wizard/incidents-and-indicators-multi-tenant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.