First, define what needs to change
Moving to a newer version does not necessarily mean a new design or a new store. Establish whether you need a technical update, a data transfer to a new installation, or broader changes to functionality and appearance. Each option has a different scope.
Choose the target version based on verified compatibility and support. A full list of add-ons and custom changes matters more to this decision than the number of products alone.
Map your current setup
Record your PrestaShop version, theme, modules and their licences. Include custom changes and connections to inventory, accounting, payment and shipping systems. Also record the hosting environment and PHP version.
For every important module, ask its supplier about support for the intended version. If no compatible version exists, agree on a replacement or process change. Do not assume every add-on will work unchanged.
Agree on the data to transfer
List everything which must remain available after the move. Alongside products and categories, this includes variants, images, customers, orders, stock data, languages and content pages. Specify how custom fields will transfer.
Check the URLs of important pages too. If they will change, prepare a redirect map. Do not send every old URL to the homepage when a matching product or category exists.
Backups and a test environment
Before making changes, you need a backup of both the database and files, plus a verified recovery procedure. Trial the move on a copy first. Restrict access, real payments, outgoing emails and order transfers to dispatch in the test environment.
The official Update Assistant documentation describes the update tool. Using this tool does not replace an assessment of your theme, add-ons and custom changes. Verify the available upgrade path for your specific starting version.
Testing means more than opening the homepage
Prepare scenarios for product search, variant selection, discounts, shipping, payment and order confirmation. Check customer login and connections to other systems. Review the mobile experience and the administration.
Check the data as well: product counts and samples, order values, customer accounts and attachments. If any area falls outside the migration scope, record this before approving launch.
Launch needs a plan
Agree on the date, any maintenance window, the final transfer of changed data and the conditions for returning to the original system. Decide who approves the result and who will be available for checks after launch.
Our PrestaShop migration service follows this process. We price the work after assessing its scope, rather than treating migration as an unlimited hourly package. If you want a new starting store instead of an upgrade, compare your requirements with ShopStart.
After migration, arrange ongoing technical care so someone continues to maintain the module inventory, backups and documentation.