Loading Customers with Purchase History

Purchase history is in the transaction table - each transaction may be linked to a customer. You do not want to import this data as transactions - you might consider loading it as text into the Customer.Notes field though.

Could you explain to me why 'I don't want to import transactions' directly in order to retain my customer sales data? Putting this information into the Customer.Notes field dosn't help much for preparing customer and/or item performance reports.

Thanks,

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Importing transactions from and old system in to RMS is not an easy task. It could be done, but you need someone to write the code to read the history from your old POS and then migrate it in to RMS. If I had to do it, I'm guessing it would take me atleast 2 full days of work to write the code, test it and verify it worked. The benefits usually do not outweigh the cost. Most people are able to keep their old system around for reference if needed.

Jason,

You are correct, it is a bit of a trick. I have managed to import the information into RMS at the db level using several sql scripts to clean up the data. The only RMS tables that appear to need building are the transaction, transactionEntry and batches. At least that is true for my purposes. In my business I have several customers who want to know which items they have purchased in the past, and in some cases when and how much did they pay. Keeping the old POS system available is not an option, so it is worth the effort to implrt, although I wouldn't recommend it for everyone. Two days is correct.

Thanks

"Jas> Importing transactions from and old system in to RMS is not an easy task.