Edit History

The attached script copies the content (business data) of a shop from one installation of Prestashop to another. The products, orders, customers, etc of the new (usually freshly installed) shop will be completely replaced by those from the old shop while its configuration is maintained. Your customers can even keep their old passwords.

Prestashop updates regularly result in unstable situations. This instability is nearly always in the files or the configuration settings.In either case this script can be a solution as it leaves both behind. It is far superior to a csv export as that copies only a part of your data.

Copy_shopdata should be installed in the same directory as Prestools as it uses Prestools for authorization. It should be installed in the new shop, after which you fill in the database data of the old shop in copy_shopsdata's config file.

Copy_shopdata is meant to repair installations. You should leave the upgrade process to Prestashop.

Documentation is in the pdf file.

PS. Nearly any shop can be repaired and/or updated this way. If you are afraid to do it yourself you can hire me to do it for you.

PS-2. Some people have tried to use this tool for updating from 1.6.1 to 1.7. This is to some extent possible as the database structure is very similar. However, nowadays that shouldn't be done anymore as Prestashop's update software now can update from 1.6 to 1.7

You can download from the Prestools website

Copy Shopdata

Or directly (doesn't work when you are not logged in into the forum)

copy_shopdata-v0.30.zip

The attached script copies the content (business data) of a shop from one installation of Prestashop to another. The products, orders, customers, etc of the new (usually freshly installed) shop will be completely replaced by those from the old shop while its configuration is maintained. Your customers can even keep their old passwords.

Prestashop updates regularly result in unstable situations. This instability is nearly always in the files or the configuration settings.In either case this script can be a solution as it leaves both behind. It is far superior to a csv export as that copies only a part of your data.

Copy_shopdata should be installed in the same directory as Prestools as it uses Prestools for authorization. It should be installed in the new shop, after which you fill in the database data of the old shop in copy_shopsdata's config file.

Copy_shopdata is meant to repair installations. You should leave the upgrade process to Prestashop.

Documentation is in the pdf file.

PS. Nearly any shop can be repaired and/or updated this way. If you are afraid to do it yourself you can hire me to do it for you.

PS-2. Some people have tried to use this tool for updating from 1.6.1 to 1.7. This is to some extent possible as the database structure is very similar. However, nowadays that shouldn't be done anymore as Prestashop's update software now can update from 1.6 to 1.7

copy_shopdata-v0.29e.zip

The attached script copies the content (business data) of a shop from one installation of Prestashop to another. The products, orders, customers, etc of the new (usually freshly installed) shop will be completely replaced by those from the old shop while its configuration is maintained. Your customers can even keep their old passwords.

Prestashop updates regularly result in unstable situations. This instability is nearly always in the files or the configuration settings.In either case this script can be a solution as it leaves both behind. It is far superior to a csv export as that copies only a part of your data.

Copy_shopdata should be installed in the same directory as Prestools as it uses Prestools for authorization. It should be installed in the new shop, after which you fill in the database data of the old shop in copy_shopsdata's config file.

Copy_shopdata is meant to repair installations. You should leave the upgrade process to Prestashop.

Documentation is in the pdf file.

PS. Nearly any shop can be repaired and/or updated this way. If you are afraid to do it yourself you can hire me to do it for you.

PS-2. Some people have tried to use this tool for updating from 1.6.1 to 1.7. This is to some extent possible as the database structure is very similar. However, you should only update to 1.7.2 and use the PS updater for updating to 1.7.3. One problem is the security key (Rijndael) that is differently structured in 1.7. I don't know how to make that transition. That means that you shouldn't copy the ps_employee* tables or adapt those keys. You may copy the ps_customer* tables but you will need to ask your customers to reset their passwords. However, copying product data is possible. Yet some adaptions are needed such as setting the "state" field in ps_product to "1".

copy_shopdata-v0.29e.zip

The attached script copies the content (business data) of a shop from one installation of Prestashop to another. The products, orders, customers, etc of the new (usually freshly installed) shop will be completely replaced by those from the old shop while its configuration is maintained. Your customers can even keep their old passwords.

Prestashop updates regularly result in unstable situations. This instability is nearly always in the files or the configuration settings.In either case this script can be a solution as it leaves both behind. It is far superior to a csv export as that copies only a part of your data.

Copy_shopdata should be installed in the same directory as Prestools as it uses Prestools for authorization. It should be installed in the new shop, after which you fill in the database data of the old shop in copy_shopsdata's config file.

Copy_shopdata is meant to repair installations. You should leave the upgrade process to Prestashop.

Documentation is in the pdf file.

PS. Nearly any shop can be repaired and/or updated this way. If you are afraid to do it yourself you can hire me to do it for you.

PS-2. Some people have tried to use this tool for updating from 1.6.1 to 1.7. This is to some extent possible as the database structure is very similar. However, you should only update to 1.7.2 and use the PS updater for updating to 1.7.3. One problem is the security key (Rijndael) that is differently structured in 1.7. I don't know how to make that transition. That means that you shouldn't copy the ps_employee* tables or adapt those keys. You may copy the ps_customer* tables but you will need to ask your customers to reset their passwords. However, copying product data is possible. Yet some adaptions are needed such as setting the "state" field in ps_product to "1".

copy_shopdata-v0.29d.zip