A customers CSV file for import must have a name customers-xxxxxx.csv, where the part -xxxxxx can be anything you want, or can be omitted.
Examples of correct product CSV file names:
customers.csv;
customers-13-01-01.csv;
customers-from-my-provider.csv
A customers CSV file must contain at least two fields:
login - unique identifier of a user (user email);
status - the status of a user (either E (enabled) or D (disabled)).
A sample of the simplest customers CSV file is as follows:
There are many more fields that you can include into your product CSV file. Below is a list of supported fields and their respective value types for the import of customers:
Field in CSV file | What this field describes | |
login* | Unique identifier of the user. Email is used as login. | String, |
status* | User status. Possible values are:
| Enum |
added | Service field containing the date of registration | Date |
firstLogin | Service field containing the date of first successful login | Date |
lastLogin | Service field containing the date of last successful login | Date |
referer | Referer link | Date |
language | Two-symbol code of the language (e.g. en) | String, |
membership | Membership of the user | String |
password | Password. Will be encrypted and stored as a hash. | String |
forceChangePassword | Should be Yes if user is required to change his password on next login and No otherwise. | Yes/No |
addressField | A very special service field. Has a row on each address and a column on each address part, such as zipcode. Column name is combined from part name and 'addressField' word. See example below.***
| Multicolumn, |
* Required field.
** See CSV Field Notices for more info.
*** addressField example:
Tips:
If you are going to import data into X-Cart and do not wish to update certain X-Cart fields during the import process, you should not include these fields in your CSV file for import. Simply remove the respective column(s) from the file.
Related pages: