> 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/api-references/api-guides/utilities/import-service.md). # Import Service Imports external master data into Emporix. A configuration groups one or more streams; each stream extracts from a source connection, maps fields to an Emporix target type, and upserts idempotently. {% hint style="danger" %} This functionality is in preview mode - some of the features may not be fully operational yet. {% endhint %} ### Key features and benefits * Imports external master data into Emporix through configured streams * Groups one or more streams in a configuration, each mapping source fields to an Emporix target type * Performs idempotent upserts of imported records * Triggers import runs manually or on a cron schedule * Supports full and delta run modes, with an optional dry run that validates without writing * Runs imports asynchronously and streams per-stream progress over Server-Sent Events * Monitors run status, history, errors, and per-stream counters * Cancels active import jobs * Retrieves configurations, streams, schedules, and imported records --- # 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://developer.emporix.io/api-references/api-guides/utilities/import-service.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.