> 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/migration-prerequisites-for-cortex-xsoar-8-saas.md).
# Migration Prerequisites for Cortex XSOAR 8 SaaS
Before starting migration, review the following prerequisites for the relevant migration process.
**Self-service migration**
* Review the feature changes in Cortex XSOAR 8, including users and roles. For more information, see [Cortex XSOAR 8 Feature Changes](/cortex-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes.md).
* Plan your migration. Coordinate and obtain approval for the migration dates through your internal change management process.
**Migration using the migration wizard**
| Platform | Feature | Description |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cortex XSOAR 8 | General | Review the feature changes in Cortex XSOAR 8. For more information, see [Cortex XSOAR 8 Feature Changes](/cortex-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes.md). |
| Users and roles | Review the users and roles feature in Cortex XSOAR 8. A unique email address is required for users to access the Cortex XSOAR 8 tenant. Verify that all local users who need to be migrated, including the default admin, have a unique email address in Cortex XSOAR 6. For more information, see Set up Users and Roles.
Important
You must provide a valid email address so that users can receive their activation notification and reset their password.
If migrating incidents and indicators, ensure you have sufficient memory on Cortex XSOAR 6.
Important
When migrating from Cortex XSOAR 6 On-prem, you need more than 50% free RAM on Cortex XSOAR 6 due to how the migration flow is handled. If current use on your Cortex XSOAR 6 environment exceeds 50%, add more RAM to your Cortex XSOAR 6 server.
In Cortex XSOAR 6, ensure that you comply with the following recommended specifications:
| |
| Private remote repository | If using a private remote repository, verify that the remote repository branch is not protected before starting the migration process. You can set it to `protected` after the switchover (migration is complete). | |
| Deprecated content | Update any deprecated content in Cortex XSOAR 6 to supported content. For example, on Cortex XSOAR 6, if you have configured the Demisto REST API integration, replace it with the Core Rest API. When you start the migration process, the initial data sync includes the updated supported content to Cortex XSOAR 8. If you do not update before the initial data sync, the content is not migrated and you must configure it in Cortex XSOAR 8. | |
| N/a | Migration dates | Coordinate and obtain approval for the migration dates through your internal change management process. A brief period of downtime may be required when the migration is completed. |
{% hint style="info" %}
### Tip
We also recommend reviewing the following information:
* Familiarize yourself with the Cortex Gateway. The Cortex Gateway is a central portal for managing your Cortex products. Although most settings can also be configured in the Cortex XSOAR 8 tenant, there are additional options in the Cortex Gateway. You can manage users through the Customer Support Portal (CSP) or SSO. User management in the CSP applies to all Cortex products. For more information, see [Set up Users and Roles](/cortex-xsoar-8-saas/configure-cortex-xsoar/users-and-roles-management.md).
* [Cortex XSOAR 8 Release Notes](/cortex-xsoar-8-saas-release-notes/cortex-xsoar-release-information.md) to understand the latest features and improvements.
* Update your firewall's allow list for Cortex XSOAR 8. For more information, see [Cortex XSOAR 8 IP addresses](/cortex-xsoar-8-saas/onboard-cortex-xsoar/deployment-steps/step-1-activate-cortex-xsoar/enable-access-to-palo-alto-networks-resources.md).
{% 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-migration/migration-prerequisites-for-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.