> 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/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-4.-select-whether-to-resync-data-and-set-the-switchover-date.md). # Step 4. Select whether to resync data and set the switchover date Now that you have completed the UAT tests, you can do one of the following: * Resync data and set the switchover date * Decide not to resync data and complete the switchover immediately You have up to 60 days from the date of the initial data sync to complete the migration process. {% hint style="info" %} ### Important If you exceed 60 days, you will no longer have access to the Cortex XSOAR 8 tenant. To recreate the tenant, you must open a support ticket in the Customer Support Portal (CSP), but all content changes will be lost. {% endhint %} When migration has finished, the Cortex XSOAR 8 tenant becomes available for end-users. Cortex XSOAR 6 is available for audit purposes, and you can't run any automations. {% hint style="info" %} ### Note If you are running a playbook communication task in Cortex XSOAR 6 that was not completed at the switchover date when clicking the task on Cortex XSOAR 8, you will be directed to Cortex XSOAR 6 and not to Cortex XSOAR 8. {% endhint %}
Data resync and switchover If you decide to resync data, at the switchover date, the following data from Cortex XSOAR 6 is resynced to Cortex XSOAR 8, and any changes to Cortex XSOAR 8 data are overwritten. | Items | Resync action at switchover | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Content |

In the migration wizard, you can select whether to resync content, which overwrites:

Note

If you decide to resync content data, all content you have created in Cortex XSOAR 8 is overwritten at the switchover date. If you want to keep custom content created in Cortex XSOAR 8, export the content as a backup before the resync. To export custom content in Cortex XSOAR 8, go to Settings & Info → Settings → Server Settings and Export all custom content.

| | Incidents and indicators |

Note

Any changes made to incidents and indicators in Cortex XSOAR 8 are overwritten.

Regardless of whether you selected to migrate incidents and indicators, any incidents or indicators created on Cortex XSOAR 8 during the UAT are removed at the switchover date

| | Integrations and instances |

In the migration wizard, you can compare the differences between integration instances in Cortex XSOAR 6 and 8 and select the instances you want to resync and overwrite.

| | Jobs | New jobs created in Cortex XSOAR 8 that did not exist in Cortex XSOAR 6, remain unchanged. Edited jobs created in Cortex XSOAR 8 will be overridden. | | Users | Activate all users | | Engines | Engine data, including Docker images. | | Other data | | Set the switchover date At the switchover date, data is migrated (resynced) from Cortex XSOAR 6 to Cortex XSOAR 8. To minimize the expected downtime at the switchover date, we recommend setting the switchover date as soon as possible to shorten the UAT period and the accumulation of changes in Cortex XSOAR 6 that will occur during this time. After setting the switchover date, you should receive an email confirming the migration date. {% hint style="info" %} ### Note The switchover starts on the selected date between 08:00 and 10.00 UTC. {% endhint %} Both Cortex XSOAR 6 and Cortex XSOAR 8 instances are temporarily unavailable as system settings and data are synchronized during the switchover date.
Switchover without data resync You can decide not to resync data, which means there is no downtime at switchover. Cortex XSOAR continues to be available after switchover (until the end of your license). Your current Cortex XSOAR 8 tenant does not change, and any data created during the UAT period remains. If you select not to resync data, you don't need to select a switchover date. In the migration wizard, click **Start Switchover**, and the switchover is immediate.
**Rollback** You have up to 30 days to roll back the migration process. Go to the [CSP](https://support.paloaltonetworks.com/) and create a ticket requesting a rollback. --- # 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/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-4.-select-whether-to-resync-data-and-set-the-switchover-date.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.