HQ Upgrade - Importing Transactions

I am upgrading to HQ. I currently have 2 stores and will add a 3rd in a couple of weeks. Is there any way to import our old transaction data into HQ. Both stores have the same databases, more specifically, the ID field values are the same for products in both databases. I don't think the transaction info is saved when the master databases are created during HQ setup and the store database is exported. I was thinking about writing a little script to import the transaction data back into the store databases and then let HQ import it into the main database. Unless someone already has a import module already done.

Reply to
Tony McLaughlin
Loading thread data ...

I think it will import all of that stuff with the first WS401, assuming all customers are global.

We ran SO for a while before adding HQ and I am fairly certain that my earliest customers have all of their purchase history available at HQ. Journals may be a different story.

I don't know about sales history for reports, etc. Never really checked it against the oldest store data.

Tom

Reply to
Terrible Tom

It is not really the item ID that matters. If both stores have the same set of items AND the ItemLookupCodes match up, you should be able to import one of the stores into HQ, then use 101 worksheets to Syncronize the existing store databases. You don't have to export new databases.

This is only going to be possible with extremely clean and consistent item data between the stores. You should work with your reseller on this!

Glenn Adams Tiber Creek C> I am upgrading to HQ. I currently have 2 stores and will add a 3rd in a

Reply to
Glenn Adams [MVP - Retail Mgmt

A store operations database does not have the same structure as a HQ store operations database. I find it hard to beleive that HQ will allow the databases to sinc unless it is the same format.

I tried to use 2 different store databases to make export databases but the transactions did not transfer.

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

Reply to
Tony McLaughlin

Hi Tony,

Glenn is correct, but let me explain a bit more. When you implement HQ from then on you should never create any items, department, category, tender types, tax type, etc... at any stores. Now since you already have 2 stores what needs to happen is that you create an HQ that has all the fix data [configured data - items, department, categ, messages, taxes, tenders, suppluers etc...] of both stores in them. If both stores already have exactly the same data set that would be easy, but often time they do not have that. Realitically this is a job you should give to a reseller that knows all this to do for you. I suggest that you 1st create an export of your fix data [run a report of your item value list and activate all fields in the report and then export it as a csv] and import the CSV result from excel to an RMS blank database. Then do the same for the second store and import into the same database. If you do this for allyour fix data the new store database will have a combined data of both stores fix info. From HQ Admin you can import this combined store database to HQ. Once done you can create a 101 worksheet followed by a 250 worksheet [select all items] and communicate to both stores. This will ensure that both stores have HQID that matches the ID at HQ as well as adding any missing fix data to the tsore twhere it is missing. When done run a 401 worksheet and all your sales data etc... will be uploaded to HQ.

I strongly recommend that you get a professional reseller that knows what they are doing to do this job for you. If you wish us to do this for you I would be happy to quote. You could upload both Store ZIP files to FTP and we would do the job for you and give you back the synchronised HQ. Contact me if interested.

Afshin Alikhani - [ snipped-for-privacy@retailrealm.co.uk ] CEO - Retail Realm = = = = = = = = "Tony McLaughlin" wrote in message news: snipped-for-privacy@microsoft.com...

Reply to
Afshin Alikhani

Reply to
Tony McLaughlin

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.