> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/extensibility-and-integrations/integrations/import-tool.md).

# Import Tool

Use the Import Tool to keep Emporix aligned with source-system data through scheduled or on-demand imports.

Use the Import Tool when you need to load or refresh large volumes of records from an external system so Emporix stays aligned with that source. Typical cases include synchronizing master or operational data from Celonis or another backend, and repeating that load on a schedule or on demand.

The tool reads records from a connected source, maps them to Emporix entities, then creates and updates those records. You can run a full import of the current source set, or a delta import that brings only what changed. After a run you review outcomes, failures, and imported records so you can correct mapping or source issues before the next load.

You open the Import Tool from the Management Dashboard. There you store source credentials, define import jobs and streams, map fields, run or schedule imports, and monitor health. Setup, mapping, and run procedures are in the Import Tool guides.

{% hint style="info" %}
To learn more about the Import Tool, see the [Import Tool guides](https://developer.emporix.io/import-tool/).
{% 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://developer.emporix.io/user-guides/extensibility-and-integrations/integrations/import-tool.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.