> 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/post-migration-steps-for-cortex-xsoar-6-on-prem-to-8-saas.md). # Post Migration Steps for Cortex XSOAR 6 On-prem to 8 SaaS ## Post Migration Steps for Cortex XSOAR 6 On-prem to 8 SaaS Relevant for Cortex XSOAR 8 SaaS wizard migration. After the switchover, Cortex XSOAR 8 becomes active. You can still access your Cortex XSOAR 6 instance after migration until EOL or the end of your contract term (whichever comes first), but you can't perform any automation. You should now perform the following steps: 1. Validate settings and data. For remote repositories, if you changed the branch in your remote repository, review the settings and decide whether to switch back to the original branch used with Cortex XSOAR 6 or to continue to use the new one. 2. Ensure that local users complete their user registration in the CSP. For more information, see [How to Create your CSP user account](https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClNVCA0). 3. If you have not done so already, update your engines.

The Cortex XSOAR 6 engine is supported up to 30 days after the switchover date to resolve any potential engine migration issues. To have a definitive engine in the XSOAR 8 environment, you need to deploy XSOAR 8 Engines. For more information, see Install an engine.

4. If you did not migrate indicator data and want to use the indicators in Cortex XSOAR 8, you can do the following: * Manually export and import indicators from Cortex XSOAR 6 to 8. * Set up a TAXII server integration on Cortex XSOAR 6 and use TAXII feed integration on Cortex XSOAR 8. * If no intel is needed and only the indicators are needed, use an External Dynamic List (EDL) on Cortex XSOAR 6 and use a plain text feed to ingest the EDL into Cortex XSOAR 8.

We suggest you work with your customer success or support team to determine the best path forward specific to your requirements. The ways you can move indicator data may not encapsulate all the data present in Cortex XSOAR 6 with respect to that indicator.

You can continue working on active incidents until closure in Cortex XSOAR 6 until the end of your contract term (but no automation). #### Troubleshoot a Content Migration Error Some PANW-supported content (including customized PANW-supported content) uses a maximum version to ensure that content is updated to the latest released version. When content is migrated and you have copied and customized PANW-supported content, you may receive a similar message to the one below: ```programlisting Content Installation Conflicts Found Could not create widget with ID 'incidents-dropped-in-preprocessing' and name 'Incidents Dropped in Preprocessing'. Version (7.9.9) is not compatible with environment version (8.4.0) [Content Pack: 'CommonWidgets'] Could not create playbook with ID 'playbook0' and name 'Default'. Version (7.9.9) is not compatible with environment version (8.4.0) [Content Pack: 'DefaultPlaybook'] Could not create playbook with ID 'c1fe5585-4a1d-46ec-86bc-9e1a32eb3a05' and name 'Default_copy'. Version (7.9.9) is not compatible with environment version (8.4.0) Could not create playbook with ID '7e3e6e45-1102-4a58-84a3-0baf88f42d54' and name 'Default_saar'. Version (7.9.9) is not compatible with environment version (8.4.0) Could not create integration with ID 'Demisto REST API' and name 'Demisto REST API'. Version (7.9.9) is not compatible with environment version (8.4.0) [Content Pack: 'DemistoRESTAPI'] ``` You can verify this content by checking the YAML file for the relevant content, which includes the entry: `toversion: 7.9.9`. If you receive this error, update the content in Marketplace and create a copy of the updated supported content. You can then add customized content to the copied content. ## Limitations of using the migration wizard This section describes the limitations of using the migration wizard. **Playbook authenticated communication tasks** **Issue:** Any authenticated communication tasks that were not completed on Cortex XSOAR 6 before the switchover date can't be completed after migration. **Reason**: The authenticated communication task link, whether sent through email, Slack, or generated directly, will always link to Cortex XSOAR 6. After the switchover date, this link will not redirect to Cortex XSOAR 8. **Solution**: Update your authentication settings on Cortex XSOAR 8 and rerun the task after the switchover date. --- # 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/post-migration-steps-for-cortex-xsoar-6-on-prem-to-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.