> 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/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/copy-content/copy-cwp-configurations.md).

# Copy CWP configurations

Copy supported CWP configurations from Prisma Cloud.

### Policies and their asset groups

When you copy **Policies and Their Asset Groups** in the Upgrade Helper, the Prisma Cloud Custom Rules and their Collections are copied as Policies and their Asset Groups in Cortex Cloud.

Prisma Cloud Runtime Rules for vulnerabilities and compliance are copied to equivalent Cortex Cloud Policies for vulnerabilities, malware, and misconfiguration.

Policy scope is handled as follows:

* Each Prisma Cloud rule has a scope of one or more Collections.
* The Cortex Cloud policies are scoped to Asset Groups with properties that match as closely as possible to the relevant Collections.

#### Verify copied rules

After you follow the steps listed in **Copy configurations**, navigate to **Posture Management** → **Rules & Policies** → **Cloud Workload** to view the list of rules that were copied.


---

# 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/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/copy-content/copy-cwp-configurations.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.