Why migrate your store now
PrestaShop 1.7 has not received a single security fix since PrestaShop 9 was released in June 2025: its last patch, 1.7.8.11, dates from January 2024. It does not run beyond PHP 7.4, which itself has had no fixes since the end of 2022, and PrestaShop 1.6 is even older. Sooner or later your host will require a newer PHP version: the store will then stop working, or become an easy target for hackers, with your customers’ data at stake.
The target is now PrestaShop 9.2, released on 30 September 2026, built on a technical foundation (Symfony 6.4 LTS) maintained until November 2027. PrestaShop 8.2 is still an option, but it only receives security fixes, until PrestaShop 10 comes out, and it does not run beyond PHP 8.1, which is no longer maintained. Migrating is also an opportunity to review your e-commerce strategy: PrestaShop 9’s technology brings better handling of images, of the checkout and of connections with your software.
Planning ahead costs less than repairing: a prepared migration takes one to two weeks, whereas a store taken down by a change forced by your host is a problem to fix in a hurry, with sales blocked. My goal: a switchover your customers do not notice, and a store ready to become faster and more secure, where an old installation is often slow.
Upgrade or migration: what is the difference?
- Upgrade (from 1.7 or 8): the existing store moves to the newer version, keeping its structure. The official tool, Update Assistant, does not skip major versions: a 1.7 store first moves to 8.2, then to 9, with its database adapted at each step.
- Migration (from 1.6): PrestaShop is installed in a new environment, then the data is transferred into it. A manual migration, table by table, is not reliable on a real store: I use tested transfer scripts, migrate a sample first, then check that every piece of migrated data has been carried over correctly.
- Either way, the process is the same: copy, migrate, check, then switch over.
Which tools should you use to migrate PrestaShop?
There are three families of solutions, and none of them gets a migration done on its own:
- Update Assistant (formerly 1-Click Upgrade, technical name autoupgrade), PrestaShop’s free official tool: it upgrades the core and the database, makes a backup and lets you roll back, but moves one major version at a time and fixes neither the look of the store nor incompatible modules.
- Data transfer modules sold on the market (MigrationPro, MigraPro…): they copy the catalogue, customers and orders from a 1.6 installation to a fresh PrestaShop. Useful from 1.6, they carry over neither the design nor custom code.
- Custom scripts and checks: what I add around these tools to handle special cases (overrides, added fields, feeds), then check the migrated data item by item.
The right solution depends on the current version and the state of the store: it is decided during the audit, never at random.
Migrating from PrestaShop 1.6 to 1.7: is 1.7 still worth it?
No: in 2026, moving from PrestaShop 1.6 to 1.7 means migrating to a branch that is already at the end of its life. 1.7 no longer receives security fixes and does not run beyond PHP 7.4: everything would have to be done again within months. A 1.6 store therefore migrates straight to PrestaShop 8 or 9, in one go.
- The direct jump is possible: a migration installs a brand-new store and then transfers the data into it, so nothing forces you to go through 1.7. The official tool, on the other hand, requires two steps (1.6 to 1.7, then 1.7 to 8 or 9): there, 1.7 is only a technical stage, never a destination.
- What does not carry over: a 1.6 theme is compatible neither with 1.7 nor with later versions, which rely on a different theme system. Some 1.6 modules and most overrides also have to be replaced or rewritten, whether the target is 1.7 or 9.
- When to stay on 1.7 for a while: if the store depends on an essential module that only exists for 1.7, until a replacement is found. This is rare, and the compatibility audit flags it before the quote.
The fixed-price migration from 1.6, detailed below, targets the latest version directly, at no extra cost compared with a 1.7 target.
What is transferred during a migration
Here is what I can transfer from your current store to the new version of PrestaShop:
- the catalogue: categories, products, combinations, images, prices, stock, features;
- customers and their address books, with their passwords: they log in as before;
- order history, invoices and credit slips;
- newsletter subscribers, with their consent;
- content pages (terms and conditions, legal notice, privacy policy);
- carriers, zones, taxes and currencies;
- files attached to products (manuals, data sheets), languages and the stores of a multistore installation.
Page addresses (URLs) are kept or redirected one by one: your domain name does not change, and Google finds every product again.
Migrating to PrestaShop 9: what I check before starting
A migration succeeds or fails on a few critical points, which the compatibility audit reviews before the final quote.
- The server: I record the exact configuration of the store and of your hosting. PrestaShop 9 requires PHP 8.1 at minimum, but PHP 8.1 has had no fixes since 31 December 2025 and PHP 8.2 reaches end of life on 31 December 2026: I aim for PHP 8.3 or 8.4. If your current hosting plan does not meet the requirements, I recommend a suitable host. Outgoing e-mail must use TLS: SSL encryption is no longer accepted.
- Modules: I draw up a complete inventory of the installed modules. PrestaShop 9 has changed its foundation (Symfony 4.4 to 6.4), removed the old product page from the back office along with more than twenty hooks, and dropped deprecated services and classes. A module written for 1.7 may therefore crash. For each one, I look for a compatible version from its developer (often on PrestaShop Addons), an equivalent, or estimate the code fix.
- The theme, meaning the pages your customers see: since 9.1, the default theme is called Hummingbird. The old Classic theme can still be used, but a marketplace theme or a custom design must be checked screen by screen, especially the cart and the checkout.
- Custom development: override files, those changes to the core that PrestaShop advises against, and the developments written for you are identified one by one. A common example: a shipping module modified years ago by a former provider, whose original code has been lost. Putting a clean solution in place, with no risk for the rest of the store, is then part of the quote.
Business-critical modules are handled first: payment methods (PayPal, Stripe, PrestaShop Checkout, your bank), delivery and shipping, invoicing.
Feeds, sales channels and connections
An online store rarely lives on its own. Before the switchover, I list everything that will need to be connected, so that nothing stops when the new store goes live:
- product feeds sent to Google Shopping, price comparison sites or marketplaces, and your other sales channels;
- data exchanges with an ERP, a point-of-sale system or a logistics warehouse (stock, orders, shipments);
- marketing apps: newsletter, customer reviews, automated abandoned-cart reminders;
- audience measurement: Matomo or Analytics, Search Console, advertising pixels.
Every feed is tested on the copy. Each of your sales channels then has to be reconnected, which is included in the fixed price; a custom integration with your ERP is quoted separately. Thanks to PrestaShop 9’s new Admin API, connecting an ERP or an app to the store is also more standard than with 1.7: the integration of your channels and feeds becomes more reliable.
How I test before the switchover
Everything happens in a secure test environment, a copy of the store (also called a staging environment), password-protected and closed to Google. Meanwhile, the live store keeps selling. I run through scenarios written in advance, which I can share with you:
- a complete order, like a real customer: cart, address, delivery, payment, confirmation e-mail;
- the back office: orders, products, categories, discounts, invoices, your team’s permissions;
- every module kept, with its settings, tested from the user’s point of view;
- page URLs and redirects, so that search rankings do not move;
- the loading time of key pages, on mobile and desktop, and the conversion rate to compare afterwards.
You can also explore the copy yourself: this is the stage where your opinion matters most.
At switchover time, the operation is short: the store closes for a few minutes, long enough to carry over the latest orders and put the migration live. A full backup (database and files) is made just before, and a second backup remains available: if a blocking bug appears, rolling back takes a few minutes.
Upgrade from PrestaShop 1.7 to 8 or 9: from €1,190 excl. VAT
For a 1.7 store with up to 15 third-party modules, the fixed price includes:
- a compatibility audit of your modules and theme;
- the work on a copy of the store, without touching the live site;
- replacement of incompatible modules, by their latest version or by an equivalent when one exists;
- a move to a maintained PHP version (on PrestaShop 9, as 8.2 remains limited to PHP 8.1);
- complete tests, from checkout to payment;
- a 30-day warranty after the switchover.
The compatibility audit, included, is also used to confirm this budget before starting: you approve the quote, then I begin.
Migration from 1.6: from €1,990 excl. VAT
Whether you are looking to upgrade PrestaShop 1.6 to 1.7 or to 8, this package takes you straight to the latest, maintained version.
For up to 2,000 products: a brand-new store on the latest version, with products and their combinations and images, customers and orders carried over, 301 redirects from the original URLs, and 1 hour of back-office training.
Budget: what makes the cost vary
The total cost of a migration depends less on the number of products than on three factors, to be assessed before setting your budget:
- the number of third-party modules and their condition: a maintained module is replaced in minutes, an abandoned one needs a replacement solution;
- the theme: standard, bought on the marketplace, or custom, or even a new design to create;
- specific development: overrides, custom modules, connections to an ERP or business software.
The total price in euros, excl. VAT, is set after a free pre-diagnosis, and the quote details each item: you know in advance what is included and what is not, and not a single euro is added without your approval.
Preparing your migration: the right questions to ask
No need for a full specification: the essentials come down to a few simple items, which are enough to draw up an accurate plan and quote. My blog also offers a step-by-step guide to getting ready.
- access: back office, hosting, domain name;
- the list of modules you actually use, and those that are no longer needed;
- the features to keep at all costs, and those you would like to improve;
- the periods to avoid for the switchover: sales, holidays, traffic peaks.
Each phase of the work is explained to you: you always know where your project stands, and what action is expected from you.
Pitfalls to avoid
- Running the migration directly on the live store: at the first error, the site is down, and the lost orders are very real.
- Forgetting a module that seems minor: an invoice or VAT carried over incorrectly blocks the accounting.
- Changing URLs without redirects: traffic from Google drops within days, and SEO takes months to recover.
- Overlooking hosting capacity: PrestaShop 9 needs adequate resources, both in memory and in database version.
- Doing it all yourself on a complex store: a migration can seem complex, and often is. A developer’s expertise costs less than a week of lost sales.
- Not checking the data after the migration: a price, a stock level or an address carried over incorrectly is discovered when a customer complains.
Agency or freelance developer?
A web agency spreads the work across a team: a project manager and several developers. With me, you speak directly to the person doing the migration: a single point of contact, from the 30-minute call to the warranty, with my experience of PrestaShop stores since version 1.6. To choose well, look at who will actually do the work. For a small business, working with a freelance PrestaShop expert is often simpler, faster and cheaper, with no loss of method: every operation is documented, tested and reversible.
Should you switch platforms while you are at it?
The question comes up often: should you leave PrestaShop for Shopify, a hosted solution paid by monthly subscription, whose ecosystem relies on apps that are often paid? For a small business already selling on PrestaShop, staying is almost always the most economical choice. The advantage is clear: you keep your catalogue, your customers, your URLs and ownership of your store, with no commission on sales. PrestaShop is open source, backed by a large community and a vast ecosystem of modules, and you stay in control: you choose your host, your modules and your provider. Switching platforms amounts to a complete redesign, to be decided for reasons other than outdated software. Conversely, migrating to PrestaShop from another solution follows the same method: data transfer, 301 redirects and tests on a copy.
After the migration: keeping your store secure
A store that is secure at switchover has to stay that way. The PrestaShop community regularly releases fixes: following the project’s news, applying security patches and testing modules with each new release is the role of the maintenance contract, which also provides support and quick help when a problem arises. Starting from a recent base also makes every later upgrade shorter and cheaper.
Your customers and search rankings preserved
Your customers keep their account and password, and the order history is intact; your team keeps managing products and orders as before. From 1.7, your page URLs stay identical; from 1.6, each old URL is redirected to the new one so that search engines lose nothing and your SEO strategy stays intact. In the following weeks, I monitor errors in Search Console and the conversion rate during the warranty month.
What is not included
Licences for new versions of paid modules, and the rewrite of an incompatible theme or custom development, or of an abandoned module with no equivalent, are quoted separately if the compatibility audit reveals any. Once the work is done, Store maintenance keeps your store secure. You can also go back to the PrestaShop developer page, or read about what is new in my article on PrestaShop 9 (in French) and the step-by-step guide in Upgrading PrestaShop 1.7 to 8 or 9.


