This is the default migration process.
Private repositories with a single Git branch can migrate to the built-in content repository. Those with multiple branches either need to switch to a single branch, or provide new branch details and switch to migrate to a private remote content repository.
Tip
For a single Git branch deployment, we recommend using the built-in repository.
After the pre-migration wizard steps have been completed, the initial data sync starts and a Git branch is created in the built-in 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).
| | Private content repository | Single/multiple branches |If using a single or multiple Git private repositories, add the new branch names in the pre-migration wizard. The pre-migration wizard automatically creates the branch on your remote repository.
Make sure that you use the same name in dev/prod tenants.
Important
To avoid losing changes from the Cortex XSOAR 6 production machine private content repository, pull all changes from the production machine repository before the initial sync.
If you select a single branch, after the initial data sync, a single branch is created in the UAT. You can only change the selection after migration.
After the pre-migration wizard steps have been completed, the initial data sync starts and a Git branch/branches are created in the private content repository. The Cortex XSOAR 8 environment replicates the content from the Cortex XSOAR 6 environment (development 6 to development 8, production 6 to production 8).
| {% hint style="info" %} ### Note The development and production environments must use the same remote repository type. {% endhint %} If you want to switch remote content repository types, we recommend switching after migration. **Recommended development/production workflow** When migrating both the development and production instances with or without a remote repository, the pre-migration and migration wizard steps must be performed on both the development and production tenants. You can start with the development or production tenant, but we recommend starting with the development machine. We recommend migration in this order: 1. On your Cortex XSOAR 8 development tenant, complete the pre-migration and migration wizards steps, apart from resyncing data and setting the switchover date. 2. On your Cortex XSOAR 8 production tenant, complete the pre-migration and migration wizard steps, apart from resyncing data and setting the switchover date. 3. Perform final migration steps, such as setting the switchover date and resyncing data on your Cortex XSOAR 8 development tenant. 4. Perform final migration steps, such as setting the switchover date and resyncing data on your Cortex XSOAR 8 production tenant. You don't need to align switchover dates with your development/production tenants. --- # 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-2.-set-up-the-cortex-xsoar-8-tenant-using-the-pre-migration-wizard/configure-a-remote-repository-using-the-pre-migration-wizard.md?ask=