> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/how-to/transfer-project-ontologies-between-projects.md).
# Transfer project ontologies between projects
Ango Hub allows you to copy the project ontology from one project and paste it in another, by following the below steps:
1. Navigate to the project containing the ontology you wish to copy.
2. Navigate to the *Settings* tab, then the *Category Schema* section.
3. Click on the "code" button (1) on the right. A panel showing the project's ontology JSON will appear. Copy the JSON to your clipboard using the "copy" button (2).
4. Navigate to the project where you'd like to paste the ontology and follow the same steps, but instead of copying, paste the JSON you have just copied into the box.
5. Click on *Save* at the bottom of the page.
---
# 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://docs.imerit.net/how-to/transfer-project-ontologies-between-projects.md?ask=&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.
