> 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/how-to-migrate-your-multi-tenant-deployment-from-cortex-xsoar-6-to-cortex-xsoar-8-saas.md).

# How to migrate your Multi-Tenant Deployment from Cortex XSOAR 6 to Cortex XSOAR 8 SaaS

Learn how to migrate from Cortex XSOAR 6 multi-tenant/MSSP to Cortex XSOAR 8 SaaS multi-tenant/MSSP.

Work with your Customer Success or Sales Representative to manually migrate Cortex XSOAR 6 multi-tenant to Cortex XSOAR 8 SaaS multi-tenant. To set up a Cortex XSOAR 8 multi-tenant deployment, request an evaluation license to create a main tenant and one child tenant. The child tenant can be used for a maximum of 60 days, while the development and main tenants can be used for up to 90 days. Your Customer Success or Sales Representative can help you migrate content such as scripts, playbooks, and settings.

Self-service migration doesn't include migrating incident or indicator data.

{% hint style="info" %}

### Note

You can keep your Cortex XSOAR 6 On-prem installation and data for audit or compliance requirements. You can still access your Cortex XSOAR 6 instance until EoL or the end of your contract term (whichever comes first). Cortex XSOAR 6 will not support processing production workloads and will only provide 30 days of incident history.
{% endhint %}

Follow the steps in [Migrate from Cortex XSOAR 6 Multi-Tenant to Cortex XSOAR 8 SaaS Multi-Tenant (Self-Service)](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-self-service.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://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/how-to-migrate-your-multi-tenant-deployment-from-cortex-xsoar-6-to-cortex-xsoar-8-saas.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.