This article is a guide to understand the stakes and succeed in migrating to PrestaShop. (It is not a guide to know if you should migrate or not). A migration is more complicated than a website creation, because you have to redo the website and migrate the data from the old website.
Replatforming is a strategy for changing platforms. This strategy is common to all sites: ecommerce, blog, comparator. The current trend is towards micro-services, a new way of dividing up features. It allows for better scalability, a simpler interconnection and easier maintenance. It is a major technical change that has impacts on all professions: logistics, marketing, customer relations, content writing and of course IT.
The other major challenge is the change of back office interface, you will have to anticipate this point and plan a training time for your teams.
The change of CMS is a sub-type of replatforming because here we only modify the CMS. Nevertheless it is a delicate operation that deserves your full attention: sometimes, the new CMS does not have the same server requirements as the old one. It is advisable to change your hosting solution so that it corresponds better to your new CMS. When you change your CMS, the way your data is stored differs, so you need to convert it to the new structure. This is an important and complex part of the migration process.
The change of version is undoubtedly the simplest migration. However, you have to be careful about the version difference. By convention, versions are noted with 3 digits (for versions of PrestaShop prior to 8 remove the 1.: 1.7.2.1 becomes 7.2.1).
The first number represents major versions, moving from one major version to another is usually quite complicated. For example, the theme has to be redone when migrating from 1.6 to 1.7 but the data structure is similar, meaning that the data migration will be much easier than a CMS migration.
The second number represents the minor versions, they bring less changes than the major versions and it is therefore quite simple to migrate to a minor version.
The third number corresponds to a bug fix , these are generally very precise modifications that aim to correct a problem. It is therefore important to make these migrations to ensure the security of your store. Migrations are very often transparent. The structure of the code or the database hardly changes.
As you have noticed, we often use the conditional tense when talking about migration. Even if you use the same CMS, the customizations of your site are a significant factor and can represent a source of difficulty in any migration. The more your site has been customized, the more complicated the migration will be.
All migrations have the same process, once the specifications and the mock-up are done. This migration scheme is important to understand because it will allow you to understand the stakes of each step.
This is usually the first step of the migration on the technical side. If the data was to be migrated before the development of the code, there would be a problem because the specific data would not be taken into account. That's why we start the process by migrating the developments: the structure of the code of each ecommerce solution is radically different, thus, everything needs to be redone.
Establishing the specifications is therefore essential to know what developments you will undertake for the new site. To do this, you can go back to the initial specifications and delete the features that are no longer useful and add new ones. Similarly, if you want to update the theme of your site, you will need to rebuild a mock-up. This will allow you to better project yourself and limit the risks of unpleasant surprises.
This stage of development is the longest and most expensive, so you need to think carefully about the features and the theme you want before you start.
This step consists in modifying the structure and format of the data of your old CMS so that it corresponds to that of PrestaShop. This step is now well mastered by agencies, and there are modules or APIs that allow you to do the migration very easily. However, there will always be the problem of specific developments: the more specific developments you have and the more important they are, the more complicated the data migration will be.
To address this challenge, you can do partial data migrations, for example:
If you have an ERP, it will be even easier to do partial data migrations because your ERP will keep the order history.
The data migration is the real particularity of a migration, it is the complex part, because it is necessary to take back the history and sometimes to clean it. It is a process that requires a lot of rigor during the acceptance test phase.
This is a very important step and unlike the first two, you must participate in it regardless of your role. Of course the developers and the agency will perform some tests, but don't let the agency perform the tests alone. You know your site better and therefore you are in the best position to verify that the migrated data is good and consistent with the existing. This is a key phase because it will launch the last step of the production. Don't hesitate to start training your teams at this stage, it will help you to anticipate possible difficulties.
This is the last step, the production launch, the switch from one CMS to another.
Here is the procedure:
Putting the old site and the new one in maintenance
Learn more about how to migrate your ecommerce to PrestaShop with our specialists, no matter what your .current CMS is.
Merci pour votre inscription !
By submitting this form, I agree to the data entered being used by PrestaShop S.A for sending newsletters and promotional offers. You can unsubscribe at any time by using the link in the emails sent to you. Learn more about managing your data and rights .