> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-netsuite/netsuite-deployment/prerequisite-syncs/historical-customers.md).

# Historical Customers

Retailers that have been using NetSuite and Shopify prior to implementing HotWax Commerce already have a large database of customers in NetSuite. HotWax has a historical customer sync job that imports all customers from NetSuite along with their Shopify and NetSuite Internal IDs and saves them in HotWax. Now when a returning customer places an order on Shopify, HotWax will be able to link it to the existing customer based on their Shopify ID and then push their order to NetSuite using their existing NetSuite internal ID.

**SuiteScript to generate a CSV of historical customers**

```
HC_SC_GenerateProductCSV
```

**SuiteScript to upload the historical customer CSV to an FTP location**

```
HC_SC_UploadProductCSV
```

**SFTP location**

```
/home/{sftp-username}/netsuite/historicalshopifycustomer/csv
```

**Job in HotWax to import the list of historical customers**

```
Import Historical Shopify Customer
FTP Config: IMP_HIS_SHOP_CUST
```


---

# 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://docs.hotwax.co/documents/learn-netsuite/netsuite-deployment/prerequisite-syncs/historical-customers.md?ask=<question>&goal=<endgoal>
```

`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.
