> 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-migration/how-to-migrate-from-cortex-xsoar-6-on-prem-to-cortex-xsoar-8-saas.md). # How to migrate from Cortex XSOAR 6 On-prem to Cortex XSOAR 8 SaaS You can migrate from Cortex XSOAR 6 On-prem to Cortex XSOAR 8 SaaS by doing the following: * Self-service migration Work with your Customer Success or Sales Representative to manually migrate to Cortex XSOAR 8 SaaS. You can create a new Cortex XSOAR 8 tenant for up to 60 days by requesting an evaluation license. You can then decommission your Cortex XSOAR 6 server and move your licenses to Cortex XSOAR 8. Your Customer Success or Sales Representative can help you migrate your content, such as scripts, playbooks, and settings. Self-service migration doesn't include migrating incident or indicator data.

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.

Level of effort: Follow the manual steps in [Migrate from Cortex XSOAR 6 to Cortex XSOAR 8 SaaS (Self-Service)](/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-self-service.md). * Migration using the migration wizard
Migration consists of the following processes in Cortex XSOAR 8: | Migration Process | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Pre-migration wizard |

The pre-migration wizard sets up the Cortex XSOAR 8 tenant, ensures connectivity, and starts an initial data sync.

You can decide whether to migrate incident and indicator data.

| | Migration wizard |

The migration wizard guides you through the User Acceptance Test (UAT) process, enabling you to test, review, and approve changes such as incidents and indicator data, integrations, jobs, users, and roles. You set the switchover date during this period, and the migration occurs.

You have 60 days from the date of the initial data sync in the pre-migration wizard to complete your migration.

| Level of effort: Follow the steps in [Migrate from Cortex XSOAR 6 to Cortex XSOAR 8 SaaS using the pre-migration and migration wizard](/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard.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 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-migration/how-to-migrate-from-cortex-xsoar-6-on-prem-to-cortex-xsoar-8-saas.md?ask=&goal= ``` `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.