How to update the system after a long-term interval

Installation
1

If the system has not been updated for a long time and several minor versions of the module have been missed, migration errors may pop up during the update. If this happens in your environment, we recommend using the following tutorial.

Steps to update atrocore from old versions

These are the version breakpoints regarding migration: 1.5.64, 1.6.22, 1.7.0, 1.7.14
To update you have to set those versions and do multiple steps

It is better to migrate from minor change tag to next minor change tag, for example if you are at Core 1.1 and you want to go to 1.3, update to 1.2 first then update to 1.3

Example: We have a system at 1.5.0 and we want to update to 1.10.0

These are the steps:
1 - set core version as 1.5.64 and update, after update, go to administration and click on “Rebuild Database”
2 - set core version as 1.6.22, update and rebuild database
3 - set core version as 1.7.0, update and rebuild database
4 - set core version as 1.7.14, update and rebuild database
5 - set core version as 1.8.0, update
6 - set core version as 1.9.0, update
6 - set core version as 1.10.0, update

2

A couple of useful notes from our experience doing this.

  1. If your first attempt fails, it is worth going back to a full restore of the db and app server and then walk through the steps above.
  2. In the rebuild database steps, look at the user activity in the database rather than rely on the UI reporting it is done. Some of the rebuilds can take a long time (we have 50k products and a lot of assets and some rebuilds took up to an hour. First time round we thought the rebuild was done and carried on with upgrades and found issues
  3. Use snapshots if using vm. If an error occurs you can roll back quickly. We took a snapshot after every successful upgrade