When importing a manual club member list for automated discounts or sending out invitations, there's some data issues that can be created by the source of your data that should be addressed before importing. And the best place to start is to clean up the data in the database where you are sourcing the information.
Easiest place to start is to take our example import file and copy & paste just 10 rows of data in to it, then save the file as "cellarpass-club-import-052523.xls" replacing the "052523" with today's day. Then attempt an import. The less data in your first pass will confirm your file format is correct. Then you can add another 300-400 rows, do a test import and so forth. If this import is rejected, then you now there's something wrong with the data in the file itself in rows 11 - 400.
Look for Phone Number Issues
Data to look out for typically is admin (and the system) entering phone numbers in an inconsistent format such as 8554234448 or (855) 423-4448 or (855)423448 and so forth. Cleaning up your data will pay dividends as you move data around to different systems. We recommend 855-423-4448 or (855) 423-4448 formats. If you do international numbers, then you can extend the data set by including the country code such as +1 (855) 423-4448.
Look for Email Address Issues
Some systems (or people) enter more than one email address in our email field, which our import will reject it. The email address must be unique per row.
Check the Filename
As we mentioned above, be sure to NOT include more than one "period" in the filename such as "club-import-05.25.23.xls" as the server will not understand the file format and reject it. You'll typically get an error saying "wrong file format". Follow our suggestions above for proper file naming.
Look for Special Characters
Including special characters such as 'double quotes' and in some cases ampersands (&) can cause issues. You can however use an ampersand in a case like "Bill & Melinda Johnson" but you cannot use that in an address field, email address field or phone field.
Comments
0 comments
Article is closed for comments.