> 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/cortex-xsoar-6.x-faqs/cortex-xsoar-6-faqs/upgrade-from-cortex-xsoar-6.md).

# Upgrade from Cortex XSOAR 6

FAQs about upgrading from Cortex XSOAR 6x to Cortex XSOAR 8 SaaS.

Cortex XSOAR 8 SaaS FAQs for upgrading.

<details>

<summary>If I currently have Cortex XSOAR 6 On-prem, what are my upgrade options?</summary>

Existing Cortex XSOAR 6 On-prem customers may migrate to Cortex XSOAR 8 SaaS.

For more information about migration, see the [Cortex XSOAR Migration Guide.](broken://spaces/nPfgrPjdRQBvgLTOrM8C/pages/0apiTs374E7IoBok3fF8)

</details>

<details>

<summary>Will On-prem and hosted deployments continue to have access to both dev and prod environments after the migration to Cortex XSOAR 8?</summary>

Yes, the dev and prod environments are supported in Cortex XSOAR 8.

</details>

<details>

<summary>Is migration from a single server to a multi-tenant and MSSP supported?</summary>

This is considered a complex migration path and is not supported.

</details>

<details>

<summary>How often will Cortex XSOAR 8 have new releases?</summary>

We will also release a new version of Cortex XSOAR 8 approximately every 3 months, which will be upgraded automatically.

</details>

<details>

<summary>While Cortex XSOAR 6 is still available, how often will it have new releases, and what is the end-of-life policy?</summary>

We will continue to release new versions of the 6 product line approximately every few months.

The End of Life (EOL) policy of Cortex XSOAR 6 is detailed on the Product Support Lifecycle page in the [Cortex XSOAR Administrator Guide](broken://spaces/OHlpKeFtqCLUYKuYyccd/pages/cXNuECcqWtloIHkp7utB).

</details>

<details>

<summary>How long can Cortex XSOAR 6 On-prem and Cortex XSOAR 8 tenants run in parallel?</summary>

For more information, see Post Migration Steps in the [Cortex XSOAR Migration Guide.](broken://spaces/nPfgrPjdRQBvgLTOrM8C/pages/0apiTs374E7IoBok3fF8)

</details>

<details>

<summary>Engine Upgrades - Will customers have to manually upgrade the engine whenever Cortex XSOAR is upgraded?</summary>

Engine upgrades will be required as Cortex XSOAR upgrades. There might be Cortex XSOAR cloud updates that do not require an engine update.

</details>

<details>

<summary>Will migrated customers with both Dev and Prod get the same setup as in Cortex XSOAR 8?</summary>

Yes, they will get one tenant for Dev and one for Prod.

</details>


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-6.x-faqs/cortex-xsoar-6-faqs/upgrade-from-cortex-xsoar-6.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.