> 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-6-administrator-guide/6.14/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/upgrade-remote-repositories-from-versions-5.5-and-below.md).

# Upgrade Remote Repositories from Versions 5.5 and below

Upgrade remote repository environments from Cortex XSOAR 5.5 to Cortex XSOAR 6.14.

This topic provides information about upgrading your remote repository environment from Cortex XSOAR v5.5 and below to Cortex XSOAR v6.2 and above. It is important that you follow these instructions exactly to avoid any problems with either environment.

1. Upgrade your development environment server to the desired version of Cortex XSOAR.
2. Navigate to Settings → **Local Changes**.
3. Filter the contents of the changes by the DBotUpgrade user. These changes reflect items that were created, deleted, and upgraded during the upgrade process.
   1. Select all changes.
   2. Push all of these changes.

      ![upgrade-remote-repo-60.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-9c9262c4b205890121810f9c7e811438ca0a7300%2F28394004da7f5cd9fcb85929e670bf253c398f43ec45a6daf0b18e8c40dbc6ae.png?alt=media)
4. Optional [Migrate all content to content packs](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/marketplace/convert-existing-content-to-content-pack-format.md).
5. Upgrade the production environment server to the desired version of Cortex XSOAR.
6. On the production server, check for new content updates and install the content.
7. Under each of your integrations, make sure that the instances are linked to the correct classifier.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/upgrade-remote-repositories-from-versions-5.5-and-below.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.