> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/tutorials/more/importing-customers-in-bulk.md).

# Importing customers in bulk

{% hint style="info" %}
Just a quick note: **Locksmith does not create a separate database of customers**. Any customers that you import here are imported as regular Shopify customers and will appear in your Shopify [Customers area](https://help.shopify.com/en/manual/customers/manage-customers). Our bulk import is simply an additional tool with a couple extra options to create/import customers.
{% endhint %}

To get started, use the "Import customers" link, found in the footer navigation on any page of the app:

<figure><img src="https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FB5l4JFrMtLa9dO6xF94z%2FImporting_customers_2.png?alt=media&amp;token=63d1de56-d510-4756-87e5-bbe67f6b263b" alt=""><figcaption></figcaption></figure>

There are two options for importing your customers: using a plain list of email addresses, or by loading in a CSV file that you create with your spreadsheet application.

## Importing using email addresses

The only thing you'll need: a list of emails to be used, one per line(or separated by a space).

You'll also see options to:

* add one or more **customer tags** to each customer that's created (useful for pre-approving wholesale accounts, for example)
* set an **account password** (which would allow your customers to sign in immediately, using that password).

If you'd like to customize which tags or what password is used *per customer*, try using a CSV instead - read on!

## Importing using a CSV

For the most flexibility, set up your customer records in your spreadsheet application (like Excel, Google Sheets), and load it into Locksmith for a bulk import:

### Supported column names

*All columns are optional, unless noted.*

* Email (required!)
* First name
* Last name
* Accepts marketing (can be "true" or "false")
* Note
* Tags (comma-delimited)
* Password
* etc...

Since this information is just forwarded to your Shopify store, you'll be using the same format that Shopify uses. For more complete information on CSV files for Shopify customers (and what other columns are available), [check out this page](https://help.shopify.com/en/manual/customers/import-export-customers).

## Results

Locksmith will give you a preview of the customers to be imported:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e27859a2c7d3a7e9ae68e67/5e27859a2876c.png)

And after you click the "Start Import" button at the bottom of the page, you'll see the results:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e27859a04286364bc9436f4/5e27859a995e5.png)

In addition to skipping any invalid e-mails, you'll notice that Locksmith will also automatically skip any emails that already have a customer account, and it'll let you know which ones it skipped.

**For questions, get ahold of us via email at <team@uselocksmith.com>**


---

# 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://www.locksmith.guide/tutorials/more/importing-customers-in-bulk.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.
