Migrating customers to new store

**adam71o** · 06-10-2005, 07:01 AM

I am planning on updating my store. Does oscmax v1.7 have any way to export ALL customer info, so that I can update the new store with that customer info?

There is a contrib. (in the osc contrib. section) that exports customer info, but it doesn't decrypt the customers' passwords, so its no good. I might as well have the customer go in and create a whole new account. The idea is that the customer will be able to go to the new store (same old url) and log right in.

Any suggestions on exporting ALL customer info, including passwords?

**michael_s** · 06-10-2005, 01:32 PM

The passwords cannot be decrypted. They use a one way MD5 method.

You should just be able to copy the md5 hash along with all the other customer info. There is no need to have them decrypted, since md5 creates the same hash for a given password, no matter what server it is on...

**adam71o** · 06-10-2005, 02:04 PM

Ok, well then on to my new question (springing from the fact that I'm an osc idiot) - is there a way to add the customers to the new database without doing them manually >> create_account.php over and over and over and over and over again, then emailing the customers and saying "we've updated our store, please go to our site, click "password forgotten" and reset your password" ????

**michael_s** · 06-10-2005, 03:02 PM

Yep,

Just do an sql dump of the data from the original database table and then execute the sql batch file generated from the dump on the new database.

This is done in a mysql front end like phpmyadmin or sqlyog.

**adam71o** · 06-13-2005, 08:32 AM

SQL dump = ?
admin>>tools>>backup?

Would taking the SQL dump from one version of oscmax to another not totally screw things up?

For example, lets say I have an oscmax v1.7 store, and I "backup" the sql db. I then want to add those customers to my new oscmax v1.8 store (or next version, whatever the version number may be). In the process of adding those customers to the new stores database, would I not be adding all sorts of other unnecessary stuff needed by the v1.7 store, but NOT needed by the v1.8 store? -----if so, wouldn't this extra stuff that I'm adding to the new database (of the new v1.8 store) totally frag the new store?

**michael_s** · 06-13-2005, 08:48 AM

SQL dump = google it.

No, do not use the osC backup feature for this. Use a tool like phpmyadmin or sqlyog.

I did not realize you were changing versions. I thought you were just moving the data to another shop. This adds another layer to the above info.

When changing versions, you always want to compare data strucuture between the 2 dbs using a tool like mysqldiff. Then using the output of mysqldiff, upgrade a copy of your original db to the new structure. Then do an sql dump/export of the data from the original db, as its structure will now match the new db.

Most likely, if you are running a stock osCMax v1.7, you will be able to use an included mysql batch file in the new version to update the structure of your db to match the new version...

**adam71o** · 06-13-2005, 11:50 AM

Thank you SO much for your help. You are a great help, and credit to the osc community.

**hayesb2** · 06-17-2005, 10:16 AM

This seems very complicated to go from 1.7 to 2.0
Are there any plans to provide a simple upgrade installation script?
If so, any ETA when to expect this?
I'd really like to upgrade my 1.7 store, but doubt I have the "know how" to convert my existing DB manually via the steps outlined above.
Thanks.

**michael_s** · 06-17-2005, 12:07 PM

hayesb2, re read my post above:

Most likely, if you are running a stock osCMax v1.7, you will be able to use an included mysql batch file in the new version to update the structure of your db to match the new version...

That means that an upgrade script will be included in the final stable release. If the procedure seems to complex at present, wait until osCMax 2.0 Stable comes out.