Ecommerce redesign · PrestaShop

PrestaShop 1.6 and 1.7 migrationTo PrestaShop 9, Shopify or WooCommerce.

Is your store still on PrestaShop 1.6 or 1.7? Neither version gets fixes any more, and neither does the PHP version it needs. We audit the store, help you choose the target, then switch over after full testing on a copy.

Where your version stands

The dates that matter.

Dates and versions taken from the official PrestaShop and PHP websites. Sources are listed below the table.

  • No longer maintained

    PrestaShop 1.6

    Releases
    Last release: 1.6.1.24, May 2019.
    Supported PHP
    PHP 5.2 to 7.1.
    Status
    Official maintenance ended on 30 June 2019. The 1.6 GitHub repository is archived.
  • No longer maintained

    PrestaShop 1.7

    Releases
    Last release: 1.7.8.11, January 2024.
    Supported PHP
    PHP 5.4 to 7.4 depending on the minor version, 7.1 to 7.4 for 1.7.8.
    Status
    Security fixes for 1.7.8 stopped when PrestaShop 9.0.0 came out, in June 2025.
  • Capped at PHP 8.1

    PrestaShop 8

    Releases
    Released in October 2022. Patch releases of 8.2 still published in 2026.
    Supported PHP
    PHP 7.2 to 8.1.
    Status
    Maintained, but PHP 8.1 has had no security fixes since 31 December 2025.
  • Current version

    PrestaShop 9

    Releases
    9.0.0 released on 10 June 2025, 9.2 released in September 2026.
    Supported PHP
    PHP 8.1 to 8.4 for 9.0, 8.1 to 8.5 for 9.1 and 9.2.
    Status
    Current branch, built on Symfony 6.4.
Each PrestaShop version stops at a given PHP version. Here is which one, and how long PHP keeps fixing it.
PrestaShopHighest PHPPHP security fixes until
1.6.17.11 December 2019
1.7.0 to 1.7.47.11 December 2019
1.7.5 and 1.7.67.230 November 2020
1.7.77.36 December 2021
1.7.87.428 November 2022
8.0 to 8.28.131 December 2025
9.08.431 December 2028
9.1 and 9.28.531 December 2029

Why a PrestaShop 1.6 or 1.7 store becomes fragile

The software no longer moves. Official maintenance of PrestaShop 1.6 ended on 30 June 2019. The 1.7.8 branch received security fixes until PrestaShop 9.0.0 came out, in June 2025, and nothing since.

The server is the second problem. PrestaShop 1.6 supports PHP 7.1 at most, PrestaShop 1.7.8 PHP 7.4. PHP has published no security fixes for these versions since December 2019 and November 2022. The day your host removes them, the store has to run on a PHP version its code was not written for.

Third-party modules depend on their vendors. Before any decision, we check which ones are still updated for your version and which ones exist for the target.

Upgrade PrestaShop or change platform

Moving from PrestaShop 1.7 to a recent version is an upgrade. PrestaShop provides an official module for it, the Update Assistant, formerly 1-Click Upgrade. The core is updated, but every module, every code override and the theme must be checked, and the server must move to a compatible PHP version.

From PrestaShop 1.6, the path is longer. The official module requires two steps, to 1.7 and then to the target version. PrestaShop's documentation also states that there is no easy way to carry over a 1.6 theme: it has to be rebuilt.

Changing platform, to Shopify or WooCommerce, means rebuilding the store on other software and importing the data. The theme, the modules and the page addresses change. The audit compares both paths for your case: catalogue, modules, integrations and team habits.

What the audit looks at

The technical side: exact PrestaShop and PHP versions, module list, code overrides, theme and its changes.

The catalogue: products, combinations, images, features, custom fields, languages and currencies.

Search: indexed URLs, pages that get traffic, inbound links and Search Console data.

The flows: payment, shipping, ERP, accounting and marketplaces. You get a written recommendation, a scope and a quote.

The options

Three paths, each with its limits.

No option is right by default. Here is what each one keeps, what it forces you to redo and which store it suits.

  • Upgrade

    PrestaShop 9 or 8

    You stay on PrestaShop, with a maintained version and a PHP version that still gets fixes.

    What you keep

    • The back office your team knows.
    • The data in place: products, customers, orders.
    • Page addresses, if their format stays the same.

    To redo or check

    • The theme: a 1.6 theme must be rebuilt, a 1.7 theme checked.
    • Every module: compatible version, replacement or custom work.
    • The server: PHP 8.1 at least for PrestaShop 9.
    • From 1.6, a mandatory step through 1.7.

    A good fit if

    Your catalogue is complex, your business modules must stay and your team knows PrestaShop. Version 8 only makes sense if a required module does not exist for 9 yet, because 8 stays capped at PHP 8.1.

  • Migration

    Shopify

    A hosted platform: Shopify runs the server, the updates and the security of the software.

    What you keep

    • Imported data: products, variants, customers and orders.
    • No server or software updates to manage.

    To redo or check

    • A monthly subscription, plus any paid apps.
    • Different page addresses, to redirect one by one.
    • Many combinations, to check against Shopify's limits on options and variants.
    • Less control over the server and the checkout.

    A good fit if

    Your team wants to focus on selling rather than hosting, and your catalogue has no unusual pricing or variant logic.

  • Migration

    WooCommerce

    An open source WordPress extension: you keep control of the code, the hosting and the data.

    What you keep

    • Imported data: products, variations, customers and orders.
    • Code and hosting on your side, with no platform subscription.
    • WordPress for content: guides, blog, editorial pages.

    To redo or check

    • Hosting, updates and security, handled by you or a provider.
    • Different page addresses, to redirect one by one.
    • Extensions to choose and keep up to date.

    A good fit if

    Your store publishes a lot of content or needs custom rules. We publish our own WooCommerce extensions on WordPress.org.

During the migration

What we protect.

No migration is risk-free. Here is what we do, point by point, to protect your sales and your search traffic.

  • One 301 redirect per URL

    We list indexed URLs, the ones that get traffic and the ones with inbound links. Each gets its new address in a 301 redirect table, tested line by line on the copy.

  • Product pages, variants and images

    Descriptions, prices, combinations, stock, SKUs, features and images are carried over, then compared with the original store, on the totals and page by page on a sample.

  • Customer accounts

    Accounts, addresses and consents are carried over. Passwords are stored encrypted and do not always transfer: when they do not, we prepare a message with you that invites each customer to set a new one.

  • Order history

    Past orders, with their lines, amounts and statuses, stay available in the new back office for customer service and accounting.

  • Payment and shipping

    Each payment and shipping module is replaced by a compatible version or its equivalent on the target, set up with your contracts and tested in test mode before the switch.

  • Go-live without downtime

    The new store is built and tested on a copy, at a separate address. The switch is prepared in advance, and the last orders from the old store are carried over at the moment of the change.

Method

From audit to 301 checks.

  1. Step 1 :Store audit

    Versions, modules, theme, catalogue, URLs and flows. You get a written recommendation and a quote.

  2. Step 2 :Choice of target

    PrestaShop 9, Shopify or WooCommerce: we compare the options on your data, you decide.

  3. Step 3 :Test copy

    New store built on a copy, data imported, redirects tested. Your team signs off the acceptance tests.

  4. Step 4 :Switch-over

    Go-live at a quiet time, last orders carried over, payments and emails checked.

  5. Step 5 :301 and Search Console checks

    Redirects, 404 errors and indexing monitored for several weeks, with fixes as issues appear.

PrestaShop migration

FAQ

Is PrestaShop 1.6 obsolete?

Yes, in terms of support. Official maintenance ended on 30 June 2019, the last release is 1.6.1.24 and it supports PHP 7.1 at most, a PHP version with no security fixes since 1 December 2019. The store can still run, but the official 1.6 repository is archived.

Can PrestaShop 1.7 be upgraded to PrestaShop 8 or 9?

Yes. The official upgrade module, the Update Assistant, moves a 1.7 store to a newer version. In parallel, every module and the theme must be checked, and the server must move to a compatible PHP version: 7.2 to 8.1 for PrestaShop 8, 8.1 or later for PrestaShop 9. We do this work on a copy.

What about PrestaShop 1.6?

The upgrade takes two steps, first to 1.7, then to the target version. A 1.6 theme cannot be reused as is and has to be rebuilt. Since the theme and part of the modules must be redone anyway, a migration to Shopify or WooCommerce is worth comparing.

PrestaShop 8 or PrestaShop 9?

PrestaShop 8 does not support PHP beyond 8.1, which has had no security fixes since 31 December 2025. PrestaShop 9.1 and 9.2 accept PHP 8.1 to 8.5. We therefore recommend 9, unless a required module does not exist for it yet.

Will we lose our search rankings?

Every migration carries a risk for organic traffic, and nobody can guarantee there will be no drop. We reduce it with one 301 redirect per URL tested before the switch, carried-over tags and content, then Search Console and 404 monitoring after go-live.

Will our customers have to change their password?

It depends on the target. Passwords are stored encrypted and do not always transfer. When they do not, accounts are imported without a password and each customer gets an invitation to set a new one. We write that message with you.

How much does a PrestaShop migration cost?

The price depends on the number of products and combinations, the modules to replace, the theme and the target you choose. It is quoted after the audit, with a written scope and milestones. The schedule is set at the same time.

See also

Contact

Still on PrestaShop 1.6 or 1.7?

Send us your store address and its PrestaShop version. We reply in English with what to check first and what the audit will cover.

Or email us: contact@jeytech.app