> 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/migration-prerequisites-for-cortex-xsoar-8-saas-multi-tenant.md). # Migration Prerequisites for Cortex XSOAR 8 SaaS Multi-Tenant Before starting the migration, review the following prerequisites for the relevant Cortex XSOAR 8 SaaS multi-tenant 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. * Review the license and retention requirements for Cortex XSOAR 8 multi-tenant. Upon migration and renewal, you receive the main tenant and one child tenant with your base multi-tenant license. You need to purchase additional licenses for your additional child tenants. For more information, see [Understand Cortex XSOAR licenses](/cortex-xsoar-8-saas/learn-about-cortex-xsoar/understand-cortex-xsoar-licenses.md). By default, Cortex XSOAR keeps incidents per tenant for six months. You can purchase incident retention licenses to extend the incident retention of one or more child tenants. These licenses, once purchased, are available for allocation to child tenants in the Cortex Gateway. For more information, see [Data Retention Policy](/cortex-xsoar-8-saas/learn-about-cortex-xsoar/data-retention-policy.md). **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). | | License and retention |

Review the license and retention requirements for Cortex XSOAR 8 multi-tenant.

Upon migration and renewal, you receive the main tenant and one child tenant with your base multi-tenant license. You need to purchase additional licenses for your additional child tenants. For more information about licenses in Cortex XSOAR, see Understand Cortex XSOAR licenses.

By default, Cortex XSOAR keeps incidents per tenant for 180 days (six months). You can purchase incident retention licenses to extend the incident retention of one or more child tenants. These licenses, once purchased, are available for allocation to child tenants in the Cortex Gateway. For more information, see Data Retention Policy.

| | | 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 tenants. In your Cortex XSOAR 6 multi-tenant deployment, verify that all local users that need to be migrated, including the default admin, have a unique email address. For more information, see Set up Users and Roles.

Important

Use a valid email address so that users can receive their activation notification. This email address is also used when they need to reset their password.

| | | 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.

All child tenants must be switched over first, and then the main tenant.

Note

You have 60 days from the date of the initial data sync to complete the switchover for child tenants and 90 days for the development and the main tenants.

| | Cortex XSOAR 6 | Version | Upgrade your Cortex XSOAR 6 instance to Cortex XSOAR 6.14 and above. | | Incidents and indicators |

If migrating incidents and indicators, ensure you have sufficient memory in Cortex XSOAR 6 (child and development tenants).

Note

Consult with your Customer Service team for system best practices and a health check, where necessary.

| | | Diagnostic issues | In your Cortex XSOAR 6 multi-tenant deployment, fix any system diagnostic issues, which enables a faster initial data sync, a shorter downtime at the switchover, and a better performance on Cortex XSOAR 8. For more information about how to fix system diagnostic issues, see [Fix System Diagnostics Issues](/xsoar-6-administrator-guide/6.14/reference-docs/reference/system-diagnostics/fix-system-diagnostics-issues.md). | | | Bolt/Elasticsearch specifications |

On your child tenant/development tenants, 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 your Cortex XSOAR 6 multi-tenant deployment to supported content. For example, in 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. | | **Recommended Steps** * 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 more 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/users-and-roles-in-cortex-xsoar.md) * Understand the latest features and improvements by going to the [Cortex XSOAR 8 Release Notes](/cortex-xsoar-8-saas-release-notes/cortex-xsoar-release-information.md). * 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). --- # 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/migration-prerequisites-for-cortex-xsoar-8-saas-multi-tenant.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.