> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/zarzadzanie-aplikacja/eksport-import-aplikacji.md).
# Application export/import
{% hint style="info" %}
The availability of the application ownership functionality depends on the license and may not be available in all deployments.
{% endhint %}
Application export and import functions make it possible to transfer ready-made business solutions between different environments, e.g. from development to test or production.
## Application export
Exporting an application in Eximee Designer is used to save it as a file containing all artifacts that make up the application - forms, processes, composite components, scripts, dictionaries, content, and other related elements.
Export is available after going to the module **Applications** and selecting an application from the list.\
The button **Export artifact**  is located in the bar in the upper-right corner of the screen and is available from every application component tab.
After clicking the button **Export artifact** a dialog window will open, whose appearance and content will differ depending on whether this is the first or a subsequent application export.
After the export is performed, the system will generate a file with the .artifact extension and allow it to be saved locally.
Exported application **no** contains no ownership information.
### First release
In the first export window, you need to add a version description and review which artifacts, and in which version, will be included in the application. Clicking the button **Release** will open a system dialog allowing the artifact to be saved to disk (with the option to add a comment to the version being created).
### Subsequent export
In the subsequent export window, we will receive information about the previous export (date and description), and the change list will show differences compared to the previous export, i.e. those artifacts that were added, changed, or removed. If there have been no changes since the previous export, a message indicating that there is no data to display will appear in place of the change list.
### Export history
The button **Export history** , located in the bar in the upper-right corner of the screen, allows you to display a dialog window with the history of all application exports along with the date, description, and information about the user who performed the export.
## Application import
Application import allows you to load a previously exported application file into Eximee Designer.
{% stepper %}
{% step %}
#### Importing an exported application — step 1
In the application list, click the button in the upper-right corner **Import application**:
Figure 4. "Applications" tab with the import option
{% endstep %}
{% step %}
#### Importing an exported application — step 2
In the opened dialog window, place the exported artifact (a file with the .artifact extension), and then click **Import**:
Figure 5. Application artifact import window
{% endstep %}
{% endstepper %}
After the import is completed, the system displays a message confirming success. If the artifact was uploaded to the repository for the first time, a message confirming its correct import will appear. If the repository already contains an artifact with the same name, the system will inform you that the selected version of the artifact already exists, but the import will still complete successfully.
{% hint style="info" %}
The import window is used to load into the repository any artifact previously downloaded from Eximee Designer – it does not have to be an application; it can be, for example, a form, process, or script.
Remember that the version of the artifact to be imported should be higher than the version of the same artifact already in the environment repository (more about versioning in: [Versioning](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/wersjonowanie.md)).
{% endhint %}
### Ownership verification rules during import
The application import process and its artifacts are subject to the following ownership checks:
1. **Application update:**\
When importing a version higher than the one currently in the environment, the user **must** must belong to the group of owners of the current application.
2. **New application:**\
If the application does not exist in the environment, anyone can perform the import, but the application will be imported **without an assigned owner**.
3. **Artifact import:**\
When importing an application with artifacts (forms, data models, and other objects) that are in a higher version than currently in the environment, the importing user **must** must have ownership permissions for those specific artifacts within the application.
[Artifact Manager](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/zarzadzanie-aplikacja/menedzer-artefaktow.md) as the only one, can import all applications and their artifacts without restrictions.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/zarzadzanie-aplikacja/eksport-import-aplikacji.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.