> 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-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/remote-repositories.md).

# Remote Repositories

Depending on whether you have selected a private or built-in repository, after the initial data sync, a Git branch is created in the built-in or private content repository. The Cortex XSOAR 8 tenant replicates the content from the Cortex XSOAR 6 environment (development 6 to development 8, production 6 to production 8).

If using a private content repository:

* Before starting the migration process, verify that the remote repository branch is not protected. You can set it to `protected` after the switchover (migration is complete).
* The branch name is set according to the branch name you provided in the pre-migration wizard.

{% hint style="info" %}

### Note

If you selected a single branch in the pre-migration wizard, you can only change the selection after migration.
{% endhint %}

Check the following:

* Ensure the production environment has the latest content and can check (pull) for new content.

  Although there shouldn't be new content, check that the production tenant can communicate with its branch.
* In the development tenant, ensure that it can push content.
* If using multiple Git branches, start working on the CI/CD process. Update your version control process to merge changes between new branches used by Cortex XSOAR 8. For example, you have two branches:

  * `new_branch_1`
  * `new_branch_2`

  Align your CI/CD process to support the new branches so `new_branch_1` can push data to `new_branch_2`.

Resync data

When the Wizard steps (UAT phase) have been completed, you can resync content between Cortex XSOAR 6 and 8. The initial sync steps are repeated, instance to instance. The tenant is reconfigured to use the built-in/private content repository.

{% hint style="info" %}

### Note

If you didn't change the content repository type during the UAT phase (recommended), you can resync or not resync content without losing any changes.

If you changed the content repository type to use a private/built-in content repository during the UAT phase (not recommended), don't resync content, otherwise, content is reverted and any changes are lost.
{% endhint %}

If you don't resync data:

* No new content is synced from Cortex XSOAR 6.
* Everything created in Cortex XSOAR 8 during the UAT phase is retained.


---

# 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-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/remote-repositories.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.