> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tokensupply.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Import data

> Move your existing catalog and keys into TokenSupply by uploading a file and mapping its columns.

Moving from another platform? The **Import Data** tab in **Settings** brings your existing data across so you do not have to re-enter it by hand. You upload a file, confirm how its columns line up, review what will land, and import.

## What you can import

* **Products**: your catalog. A Shopify product export or the TokenSupply template is recognised automatically, and its columns are mapped for you. Other exports work too, including ones from marketplaces like G2A, Kinguin, Eneba, and Driffle, but you match the columns yourself.
* **Inventory**: your keys or codes, uploaded as a CSV file with the key value and the SKU of the product it belongs to.

<Warning>
  Import your products first. Each key is matched to a product by its SKU, so a key whose product does not exist yet has nowhere to go and is skipped. Bring the catalog across, then load the keys.
</Warning>

## The upload-and-map flow

<Steps>
  <Step title="Choose a file">
    Go to **Settings** and open **Import Data**. In the **Products** or **Inventory** card, choose a CSV file or drop it in. If you do not have an export handy, select **Download a template** to see the expected columns.
  </Step>

  <Step title="Match the columns">
    For products, TokenSupply reads the file and lines its columns up with the fields it needs. It shows an example value from each column so you can confirm you picked the right one. **Name** and **SKU** must be mapped before you can continue. Inventory files skip this step.
  </Step>

  <Step title="Review what will land">
    A preview shows exactly which rows are ready and which are skipped, and why (for example, rows missing a name or SKU). Nothing is imported until you have seen this.
  </Step>

  <Step title="Import">
    Run the import. When it finishes, a summary tells you how many records were brought across and lists any rows that could not be imported, so you can fix them in the file and import again.
  </Step>
</Steps>

<Tip>
  Re-importing is safe. Rows are matched by SKU, so importing a corrected file again does not create duplicates of the products that already landed.
</Tip>

<Note>
  Column names vary by source. If you are unsure, open **Settings** > **Import Data**: it recognises a Shopify export or the TokenSupply template on sight and walks you through mapping anything else.
</Note>

<CardGroup cols={2}>
  <Card title="Store and store page" icon="store" href="/guides/settings/store-and-store-page">
    Set up your store's basics before you sell.
  </Card>

  <Card title="Quickstart" icon="bolt" href="/guides/quickstart">
    Go from a new store to a delivered order.
  </Card>
</CardGroup>