> 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.15/onboard-cortex-xsoar/marketplace/convert-existing-content-to-content-pack-format.md).

# Convert Existing Content to Content Pack Format

Convert existing content to Cortex XSOAR 6.15 content pack format.

When you upgrade from a version earlier than Cortex XSOAR v6.0, all existing content (out-of-the-box and custom content) is migrated to the new environment,.

You can continue to use the content without converting to content pack format, but you will not receive content updates. Content updates are only applied to content packs. In cases where your existing content now requires a subscription (payment), you will not have to pay to convert the content to content pack format. You will only have to pay for newly subscribed content.

You can convert out-of-the-box content separately to content pack format by installing content packs directly from the Marketplace. When you install a content pack, it updates the content to pack format, but retains all configured settings.

Before you convert content, ensure that Cortex XSOAR successfully communicates with Marketplace services. For more information, see [Required URLs](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/system-requirements.md#required-urls).

{% hint style="info" %}
To migrate content offline, follow the procedure in [Install a Content Pack Offline](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/marketplace/install-a-content-pack-offline.md).
{% endhint %}

**Content Conversion Example**

In this example, we have an existing **Okta** integration with a defined instance, but it is not in a content pack format.

![market-okta.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/Vq92PcOJFfxQLItC8dUb/eccd8cfea34d72462df957c9f9c59392c7d264861200438f77a1695672192406.png)

In the **Marketplace**, the **Okta** content pack includes the **okta** integration (not yet installed in the Marketplace).

![marketplace-okta.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/SGnm3UOuYAAreja8rKmQ/33cb1dc5b30f294e5925e208d3d4a06251c5b97cb01f524da98c209554c024e6.png)

After installing the **Okta** content pack in the **Marketplace**, the **Okta** integration overrides the existing integration (the content pack is **Okta**).

![market-okta-new.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/zUxQFbayJsdfgeZL2gtY/6f49bd5697fedcc67bcb6a26497cac55f38a02b34167d2e2f126f3f1ae0ae8ac.png)

You can also check that the content pack is installed in the **Marketplace**.

![market-library.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/OnHIPns0xEeBi6gZKjRU/07562775db32cac928ca2f720e7c55e214495f73072ca8fdd8f50142f01e9888.png)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/marketplace/convert-existing-content-to-content-pack-format.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 `build a script that syncs our docs to a CMS` 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.