> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/reference/import.md).

# Import

Struct PIM's Import lets you bring data into your PIM in bulk, without touching each product, variant, or global list one by one.

If you're sitting on hundreds or thousands of rows of product data in a spreadsheet, import is what turns that into live data in PIM, instead of typing it in field by field.

In a nutshell, it's the module that maps columns from an Excel spreadsheet, or data from an installed app importer, onto data fields in the PIM, so you can create or update products, variants, variant groups, categories, or global lists all at once.

***

### What you can do with Import

* **Bring data into your PIM** from spreadsheets or installed app importers.
* **Use the build-in importers**, "General Excel import" or "List property import", to map spreadsheet columns to data fields on products, variants, variant groups, categories or global lists.
* **Generate a template file** matching the fields you want to import, so you can always know what to upload.
* **Track your import history**, including the total number of imports, when the last one ran, and how many external app importers are installed.
* **Review recent imports** and their status at a glance.

***

### Import walkthrough

#### Import layout

The main Import page shows your build-in importers, "General Excel import" and "List property import", alongside your import statistics and a list of recent imports.

#### Start an import

1. Select a build-in importer, "General Excel import" or "List property import"
2. Select or drag and drop the file to import under "Select file"

{% hint style="info" %}
If you're unsure what to upload, click "Generate a template" to get a template file matching the fields you want to import.
{% endhint %}

***

### Related tutorials 

* [**How to import products**](/tutorials/guides/how-to-use-import/how-to-import-products.md) - Skip the manual entry and create or update products in bulk.
* [**How to import list data using List property import**](/tutorials/guides/how-to-use-import/how-to-import-list-data-using-list-property-import.md) - Add, update, or remove list rows using matching keys and import actions.
* [**How to import list data using General Excel import**](/tutorials/guides/how-to-use-import/how-to-import-list-data-using-general-excel-import.md) - Map spreadsheet columns onto a list attribute with the general-purpose importer.
* [**How to import categories**](/tutorials/guides/how-to-use-import/how-to-import-categories.md) - Build or restructure your category tree from a spreadsheet.
* [**How to import media**](/tutorials/guides/how-to-use-import/how-to-import-with-media.md) - Bring images and files along with your data in one import.
* [**How to import images from url**](/tutorials/guides/how-to-use-import/how-to-import-with-images-from-url.md) - Pull product images straight from a URL during import.
* [**How to use File templates**](/tutorials/guides/how-to-use-import/how-to-use-file-templates.md) - Save your column mapping once and reuse them every time.
* [**How to import for classification**](/tutorials/guides/how-to-use-import/how-to-use-import-for-classification.md) - Sort products into categories or product structures in bulk.


---

# 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://docs.struct.com/reference/import.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.