> 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/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz.md). # Migrate from Cortex XSOAR 6 Multi-Tenant to Cortex XSOAR 8 Multi-Tenant using the migration wizard ## Cortex XSOAR 6 Multi-tenant This process uses the following wizards to help you migrate your data to each tenant in your multi-tenant deployment. * Pre-migration wizard Sets up the Cortex XSOAR 8 migration tenant, such as sizing, retention, and dev/prod environments. During the pre-migration wizard process, for development and child tenants, you can decide whether to migrate incident and indicator data. We recommend not migrating incident and indicator data for a quicker and more efficient migration process. No data will be deleted from Cortex XSOAR 6 when you migrate your data.

Note

By default, each tenant (development and child tenant) has 6 months of incident retention. The retention period is calculated from the date the incident was created in Cortex XSOAR. All migrating customers receive an additional six months of retention until the end of the license term, regardless of whether they migrate incident and indicator data. For more information about retention, see Retention Policy.

If migrating incident and indicator data, you can select a retention period in the development and child tenant pre-migration wizard.

After completion of the pre-migration wizard, data is synced from Cortex XSOAR 6 to 8. * Migration wizard Verifies that your data and content are synced in each activated tenant and that your integrations work correctly. During this UAT phase, you are responsible for content propagation during the migration process. When you push content from the Cortex XSOAR 6 main tenant, only Cortex XSOAR 6 child tenants are updated. Cortex XSOAR 8 tenants must be updated from the Cortex XSOAR 8 development (if activated) or main tenant. When logging into the Cortex XSOAR 8 development or main tenant, you will see a notification to install content. {% hint style="info" %} ### Important For child tenants, you have up to 60 days from the date of the initial data sync to complete the switchover. For development and main tenants, you have up to 90 days. {% endhint %} **Before you begin** * Review the [Migration Prerequisites for Cortex XSOAR 8 SaaS Multi-Tenant](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migration-prerequisites-for-cortex-xsoar-8-saas-multi-tenant.md). * After receiving notification by email that your Cortex XSOAR 6 instance will be migrated, you need to provide details of administrators who will manage the migration. After the migration process starts, you can add or delete these administrators in the Cortex Gateway. * In each Cortex XSOAR 6 server, review the recommendations by going to Settings → **About** → **Migration**. **How to migrate to Cortex XSOAR 8 using the wizards** ![mt-wizard-migration-flow.png](/files/YRDxziDsGyokPxGFHPjS) | Step | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Step 1. Activate Cortex XSOAR 8 SaaS Multi-Tenant](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-1.-activate-cortex-xsoar-8-saas-multi-tenant.md) |

In Cortex Gateway, activate in the following order:

1. Main tenant

2. Development tenant and child tenant

It doesn't matter if you activate a child tenant before a development tenant.

Note

If you have a Cortex XSOAR 6 multi-tenant/MSSP license (for example, PAN-DEMISTO-MSSP), in Cortex XSOAR 8, you can activate a main tenant and one child tenant.

If you need to activate more child tenants or a development tenant, contact Customer Support to see how to obtain additional licenses.

| | [Step 2. Set up Cortex XSOAR 8 Multi-Tenant using the Pre-migration Wizard](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-2.-set-up-cortex-xsoar-8-multi-tenant-using-the-pre-migration-wizard.md) |

Sets up your Cortex XSOAR 8 tenants, ensures connectivity, and starts an initial data sync.

We recommend completing the pre-migration wizard steps in the following order:

1. Development Tenant (if activated)

If using a development tenant, we recommend configuring this tenant first, as you install and configure content on the development tenant.

2. Main Tenant

As configuration and content propagate from the main tenant to the child tenant, you should configure the main tenant before the child tenant. If you initially sync a child tenant, it will not contain any data, as you have not yet synced the main tenant.

3. Child Tenant

During the pre-migration wizard stage, for development and child tenants, you can decide whether to migrate incident and indicator data.

| | [Step 3. Run user acceptance tests (UAT) in a Multi-Tenant Deployment using the Migration Wizard](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-3.-run-user-acceptance-tests-uat-in-a-multi-tenant-deployment-using-the-migration-wizard.md) |

The wizard guides you through the User Acceptance Test (UAT) process, enabling you to test, review, and approve the changes, such as incidents and indicator data, integrations, jobs, and users and roles.

Note

Incidents, indicator data, and jobs are not relevant to the main tenant.

Although you can run tests using the migration wizard in any tenant order, you must complete the switchover on each child tenant before switching over the main and development tenants.

| | [Step 4. Select whether to resync data and set the switchover on Cortex XSOAR 8 SaaS multi-tenant](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-4.-select-whether-to-resync-data-and-set-the-switchover-on-cortex-xsoar-8-saas-multi-tenant.md) |

After completing the UAT stage, decide whether you want to resync data and set the switchover date, if relevant. The switchover must take place in the following order:

1. Child tenant

On the child tenant, you must switch over before the main tenant. When you switch over, the main tenant syncs content from the child tenant. You also want the development tenant to switch over before the main tenant (production tenant). There is no data resync on the main tenant, as the main tenant doesn't hold incident data.

2. Development tenant (if activated) and main tenant

It does not matter if the development switchover is before or after the main tenant. We recommend the development tenant first, as it minimizes downtime for content and configuration resync.

At switchover, if data is resynced (not on the main tenant), it is migrated.

Note

If you want to roll back the migration, contact Customer Support within 30 days of each tenant switching over to Cortex XSOAR 8.

| | [Post Migration Steps for Cortex XSOAR 6 Multi-Tenant to 8 SaaS Multi-Tenant](/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/post-migration-steps-for-cortex-xsoar-6-multi-tenant-to-8-saas-multi-tenant.md) | Validate settings and data. If you have decided not to migrate incident and indicator data, consider moving your incidents and indicators. | --- # 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/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz.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.