> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Import and export intents

> Move intents between organizations or back up your intent configuration by exporting to JSON and importing from JSON.

## Overview

Axon lets you export your intent configuration to a JSON file and import intents from a JSON file. Use import and export to move intents between environments (for example from a sandbox to production), share a curated intent set across organizations, or keep a backup of your custom intents.

## Export intents

You can export all of your active intents or a selected subset.

<Steps>
  <Step title="Open Axon">
    Go to the **Active intent tree** tab.
  </Step>

  <Step title="Select intents (optional)">
    Tick the checkbox next to any intents you want to export. Leave everything unselected to export the full active tree.
  </Step>

  <Step title="Trigger the export">
    Use the export action in the toolbar. Axon downloads a file named `intents-export-<YYYY-MM-DD>.json`.
  </Step>
</Steps>

The exported file is human-readable JSON. Each entry contains the intent id, its user-facing name, category placement, sort order, and deprecation state.

## Import intents

Import replays a JSON file into your Axon configuration. Each intent in the file is compared against your current tree and gets one of three statuses: **new**, **overwrite**, or **skipped**.

<Steps>
  <Step title="Open the import dialog">
    In Axon, open the import dialog from the toolbar on the **Active intent tree** tab.
  </Step>

  <Step title="Upload a JSON file">
    Drop a `.json` file into the dropzone, or click to browse. Only JSON files are accepted, and only one file per import.
  </Step>

  <Step title="Review the summary">
    Click **Next**. Axon validates the file and shows a summary grouped by status:

    * **New** — the intent id does not exist yet and will be created.
    * **Overwrite** — an intent with the same id already exists and will be replaced.
    * **Skipped** — the entry could not be imported (for example, missing `intent_id` or invalid values). The reason is shown next to the row.

    If every row is skipped, the dialog offers a **Go back** button so you can fix the file and try again.
  </Step>

  <Step title="Confirm the import">
    Click **Import** to apply the changes. New intents appear in the tree, and overwritten intents pick up the values from the file.
  </Step>
</Steps>

<Warning>
  Overwrite replaces the existing intent's fields with the values from the file. Double-check the review step before confirming, especially when importing into production.
</Warning>

## File format

The file must be a JSON array of intent objects. `intent_id` is mandatory — every other field is optional but recommended.

```json theme={null}
[
  {
    "intent_id": "request_simple_order",
    "frontend_name": "Simple order",
    "base_model_intent": "request_simple_order",
    "deprecation_status": false,
    "deprecation_date": "2099-12-31",
    "intent_type": "standard",
    "sort_order": 111101,
    "custom_first_level": "Request",
    "custom_second_level": "Order",
    "custom_third_level": "Order"
  }
]
```

Field reference:

* **intent\_id** — unique identifier used to match against existing intents. Required.
* **frontend\_name** — the user-facing name shown in Workstation and Flow.
* **base\_model\_intent** — the underlying model intent this entry maps to.
* **deprecation\_status** / **deprecation\_date** — whether the intent is deprecated and, if so, from when.
* **intent\_type** — `standard` or `custom`.
* **sort\_order** — position within the tree.
* **custom\_first\_level** / **custom\_second\_level** / **custom\_third\_level** — category, subcategory, and intent labels used to place the intent in your tree.

<Tip>
  Export your current configuration first, then edit the JSON. That gives you a valid template with your own ids and category structure to work from.
</Tip>

## What's next

* [Create and train custom intents](/knowledge-base/axon/create-custom-intents) for building intents from scratch inside Axon.
* [Navigate the intent tree](/knowledge-base/axon/intent-tree) for organizing what you import.