> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/system/ergonode-transfer/exports/creating-a-new-export.md).
# Creating a new export
This is one of the most commonly used options to export data from Ergonode to outside systems. It creates a zip file with CSV files in it.
To create a new export, click ***New export*** above the list of [Exports](https://usermanual.ergonode.com/system/ergonode-transfer/exports). Fill in all fields necessary and click ***Create*** to save or ***Create & Edit*** to save and open this export. These buttons show up once you start filling in the form. Neither of them runs the export: see [Running / Exporting data](https://usermanual.ergonode.com/system/ergonode-transfer/exports/running-exporting-data).
| Field | Description |
| ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Export name | It can be anything as long as it's unique |
| Include in the export | Here you may choose what kind of data you wish to export, you may choose some you may choose all of them: ***Attributes***, ***Attribute groups***, ***Automations***, ***Categories***, ***Category trees***, ***Category attributes***, ***Completeness sets***, ***Options***, ***Products***, ***Templates***, ***Section***, ***Media***, ***Media attributes***, ***Media folders***, ***Roles***, ***Workflows*** and ***Units*** |
| Languages | Choose the language of exported data. It will NOT auto translate data for you. |
| Delimiter | Choose a symbol to mark the end of a column in a file: semicolon (;) or comma (,) |
| Export type | Can be ***full*** or ***incremental***. Option ***incremental*** works only for products: once you edit or add new products, only those changes will appear in the export |
| Segment | Choose the [segment](https://usermanual.ergonode.com/products/segments) you wish to export or leave blank to export all products |
| Behavior of [variables](https://usermanual.ergonode.com/product-design/attributes/attribute-variables) | Choose if you wish to ***replace variables with translations*** or ***keep variables as attribute codes*** |
| Maintain media file names | Choose to keep the original file name after export. This doesn't change the name in the file's URL and can cause duplicates if media files in different folders have the same name. Leave it off to give every media file a unique name (UID) |
{% hint style="info" %}
Once selected in the configuration, a segment cannot be changed. If you need to select a different segment, create a new export with the appropriate configuration.
{% endhint %}
---
# 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://usermanual.ergonode.com/system/ergonode-transfer/exports/creating-a-new-export.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.
