> 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/step-4.-select-whether-to-resync-data-and-set-the-switchover-on-cortex-xsoar-8-saas-multi-tenant.md).

# Step 4. Select whether to resync data and set the switchover on Cortex XSOAR 8 SaaS Multi-tenant

During this stage, 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 must complete the switchover for all child tenants before starting the main tenant switchover.

You have the following time limits from the date of the initial data sync to complete the switchover:

* Child tenants: 60 days
* Development and main tenant: 90 days

{% hint style="info" %}

### Important

If you exceed the time limit, you can no longer set a switchover date on the Cortex XSOAR 8 tenant. To reset the switchover date, you must open a support ticket in the Customer Support Portal (CSP).
{% endhint %}

Both Cortex XSOAR 6 and Cortex XSOAR 8 instances are temporarily unavailable as system settings and data are synchronized during the switchover date.

When migration is completed, the Cortex XSOAR 8 child tenant becomes available for end-users. Cortex XSOAR 6 is available for audit purposes, and you can't run any automations. You can now start the switchover for your development and main tenants.

{% 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 %}

<details>

<summary>Task 1. Child tenant: Decide whether to resync data and set the switchover date</summary>

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.

</details>

<details>

<summary>Task 2. Development tenant: Decide whether to resync data and set the switchover date</summary>

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.

</details>

<details>

<summary>Task 3. Main tenant: Decide whether to resync data and set the switchover date</summary>

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.

</details>


---

# 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/step-4.-select-whether-to-resync-data-and-set-the-switchover-on-cortex-xsoar-8-saas-multi-tenant.md?ask=<question>&goal=<endgoal>
```

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