Prepare your source data
File format
Each data type is imported from its own CSV file. The column headers for each file are listed in the Schema Reference, along with a downloadable header file per data type. Dates and timestamps should be formatted as ISO-8601 (Z/UTC).
For null datapoints, simply leave the cell blank.
Identifying customers
Customer records are identified by their email address and phone number — both must be unique within your file.
Files that reference customers (customer assignments and notes) accept several identifiers. Each row must include at least one of:
- Endear customer ID — the customer's unique identifier in Endear
- Customer email address
- Customer phone number
- External customer ID — the customer's identifier in an external system, alongside the External customer integration ID identifying that system
If you plan to link purchases to customers, you must upload the customers via an Integration Import instead.
Identifying staff members
Files that reference staff members (customer assignments) accept several identifiers. Each row must include at least one of:
- Endear user ID — the staff member's unique identifier in Endear
- Endear user email address
- Endear user phone number
- Endear user username
- External user ID — alongside the External user integration ID identifying that system
Staff members uploaded via a CRM Import become users that can log in to and access Endear. Staff members from your POS system — used to attribute purchases — should be uploaded via an Integration Import. The two can be linked to each other in Endear.