Quote:
Originally Posted by Ksenia
If you move data from an older version to a newer one, we do not recommend using export/import. Not all types of data can be imported ( e.g orders), there can also be some mess with IDs or customers/products/categories.
Instead, you should upgrade the store, as a result you do not need to transfer any data manually at all.
But before taking any steps, please create a dev copy and use it as a sandbox.
*If your store is of version 4.5.0-4.5.5, you can download an upgrade pack and patch both files and database.
*If your store is of version 4.1.x-4.4.x, the most optimal way is to:
- save blowfish key
- upgrade DATABASE to v.4.5.0 by means of SQL upgrade patch ( in upgrade pack).
- assign the upgraded database to fresh 4.5.0, specify the blowfish key.
- upgrade from v4.5.0 to 4.6 by means of upgrade patches.
This is a very general instruction. Should you need a more detailed one, please request help in your HelpDesk account. Our engineers can also upgrade the store for you.
-
|
This is good advice, however it leaves you with a problem. After maybe several days/weeks work you now have a development system working and tested, with any mods you have applied or tailoring to the templates; BUT the database is now out of date as any changes (e.g. new products, new customers, new orders) are on the live database.
If you have gone from 4.4.5 to 4.6.0 using the route suggested how do you upgrade the live database and connect the new 4.6.0 store without going through the whole process again (including applying any mods or template changes) ? Repeating all the steps can introduce new errors (especially if you have any user mods).