> 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/plugins/first-party-ango-plugins/export-as-ango-import.md).
# Export as Ango Import
## Overview
The Export as Ango Import plugin converts an Ango Hub export into a JSON file that can be used as an [Ango Import Format](/data/importing-and-exporting-annotations/importing-annotations/ango-import-format.md) file.
Use this plugin when you need to reuse annotations from one project as pre-labels in another project, or when you need to create an import-ready file from an existing Ango export without writing a custom conversion script.
{% hint style="warning" %}
The destination project must already contain the assets you want to pre-label. The generated import file matches assets by `externalId`, so the destination assets must use the same external IDs as the exported assets.
{% endhint %}
## Plugin Functionality
The plugin takes the selected Ango export and returns a zip file containing one JSON file named with the `[ANGO]` suffix. This JSON file is the file you upload when importing annotations into Ango Hub.
The generated import file includes:
* Asset `externalId` values
* Supported tool annotations
* Global classifications
* Nested classifications
* Relations
* Object IDs
* Annotation descriptions stored in metadata
* Brush and medical brush data URLs, when present in the export
The plugin removes export-only metadata that is not part of the import format.
## Creating an Import File from an Export
1. Add the Export as Ango Import plugin to your organization. For more information, see [How to Add Plugins to Your Organization](/plugins/introduction-to-plugins/how-to-add-plugins-to-your-organization.md).
2. Open the project containing the annotations you want to convert.
3. Open the project's *Plugins* tab.
4. Run the Export as Ango Import plugin.
5. Select the stages and batches you want to include in the export.
6. If needed, edit the plugin's *Config JSON*.
7. Click *Run*.
8. When Ango Hub notifies you that the plugin run is complete, download the zip file.
9. Extract the JSON file from the zip.
10. Upload that JSON file as your annotation import file. For import steps, see [Importing Annotations](/data/importing-and-exporting-annotations/importing-annotations.md).
{% hint style="info" %}
Only the tasks included by the stage and batch filters are converted. If an expected annotation is missing from the generated import file, check that the task was included in the plugin run.
{% endhint %}
## Plugin Configuration
The plugin supports the following configuration:
```json
{
"annotation_identifier": "title",
"logging_frequency": 0
}
```
* **"annotation\_identifier":** Determines how the generated import file identifies labeling tools, classifications, and relations. Use `"title"` to identify annotations by labeling tool title, use `"schema_id"` to identify annotations by schema ID.
* Options:
* "title"
* "schema\_id"
* Example:
* "annotation\_identifier": "title"
{% hint style="info" %}
Using `"schema_id"` is usually safer when the destination project uses the same label set schema IDs. If the destination project has different schema IDs but matching tool titles, use `"title"`.
{% endhint %}
* **"logging\_frequency":** Defines how frequently progress logs are displayed; setting this value to 0 disables logging entirely, while any positive integer enables logging at the specified interval. For more information on how to view plugin logs, [see here](/plugins/introduction-to-plugins/monitoring-plugin-progress.md).
* Example:
* "logging\_frequency": 0
* "logging\_frequency": 100
## Importing the Generated File
Before importing the generated file into another project:
* Import or upload the destination assets first.
* Make sure destination asset external IDs match the exported asset external IDs.
* Make sure the destination project's label set contains the tools, classifications, and relations referenced by the import file.
* If you import into tasks that already exist in a workflow, make sure the tasks are in the *Start* stage and that *Auto Forward* is disabled.
For more information on pre-label import requirements, see [Importing Annotations](/data/importing-and-exporting-annotations/importing-annotations.md).
---
# 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 current page URL with the `ask` query parameter:
```
GET https://docs.imerit.net/plugins/first-party-ango-plugins/export-as-ango-import.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
