> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/entity-types/entity-type-export-import.md).

# Exporting and importing entity types

You can export custom model-based entity types and then import them into another instance of Textual.

Textual also provides a library of entity types that you can import.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Export and import custom types</strong><br><br>Export custom entity types to an encrypted file and then import them into a different instance.</td><td><a href="/textual/entity-types/entity-type-export-import/entity-type-export-import.md">Exporting and importing custom entity types</a></td></tr><tr><td><strong>Import a type from the library</strong><br><br>Import an entity type from the library that Textual maintains.</td><td><a href="/textual/entity-types/entity-type-export-import/importing-types-from-the-textual-library.md">Importing types from the Textual library</a></td></tr></tbody></table>


---

# 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.tonic.ai/textual/entity-types/entity-type-export-import.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.
