Automatic SEO meta tags: titles, descriptions and keywords for your whole catalog
Templates per page type and per language for the meta titles, descriptions and keywords of products, categories,...
The module runs on the new shop; the old one only receives the export kit, with nothing to install or activate.
Download the kit, copy it to the old shop and run it over SSH or from a cron job. Nothing is installed or activated there: the script reads the database in a consistent snapshot without stopping sales, and asks for no license.
The package is encrypted with AES-256-GCM using your password, split into parts and accompanied by an authenticated manifest. Each part carries its SHA-256 hash: a missing or modified file is refused before import.
The audit report, on screen, as a PDF and as a CSV, describes the old shop: versions, modules, overrides, non-native tables, e-mail templates, theme and volumes. It states what will be carried, what will not, the modules to replace and the targetโs requirements.
Before the first import, see group by group the rows to insert, replace, renumber or skip, with examples, the settings that will change, the volume and the estimated duration. Choose the shop and language maps and a strategy per group.
The import runs in batches, in the browser or through the scheduled task, with pause, resume and replay of failed rows. Identifiers, link_rewrite addresses, invoice numbers and bcrypt passwords are kept; conflicts are settled by replacing, renumbering or skipping.
A safety backup comes before the first import. Verification compares rows, totals to the cent, stock, images, URLs and HTTP pages; rollback deletes what the import created and puts back what it replaced. A control subset and a differential second pass complete the switch.
Moving to a recent PrestaShop version, changing host or taking over a clientโs shop means finding the products, customers, orders, invoices, URLs and content in the new installation. Re-entering everything is slow and loses the history: invoice numbers, indexed addresses, customer passwords. The in-place update does not always fit either: a theme or modules written for an older version may not follow, and the operation is hard to undo.
PrestaShop Migration moves that data into a new installation, with checks at every stage. The module is installed on the new shop. An export kit, run from the command line on the old shop, writes an encrypted package. You read an audit report, see a preview of what will be written, import in resumable batches, compare both shops, and can roll the import back.
The kit downloaded from the module holds a script and its libraries. Copy it to the old shopโs server, ideally outside the web folder, then run php export.php over SSH or from a cron job that calls PHP. Nothing is installed or activated on that shop, and the script asks for no license.
The package is encrypted with AES-256-GCM and a password chosen by the merchant, at least 12 characters and never stored. It is split into parts of adjustable size. Each part carries its SHA-256 hash and an authenticated manifest: an incomplete package, a modified one or a wrong password is refused before anything is imported. The data stays between the two shops; the โCatalog onlyโ option produces a package with no personal data.
Once the package is received and unlocked, the audit report is available on screen, as a PDF and as a CSV. It describes the old shop (PrestaShop, PHP and database versions, installed modules, class and controller overrides, non-native tables, custom e-mail templates, theme, multistore, volumes) and states what will be migrated, what will not and why, the modules to replace before opening, and the requirements of the target version. It also checks that the new shop is not older than the old one.
The preview is read group by group: rows to insert, replace, renumber or reuse as duplicates, rows left out or failed, with examples and the settings that will change. It gives a volume and an estimated duration. Nothing is written to the shopโs tables during this analysis. You choose the shop and language maps, then a strategy per group: replace, renumber or skip an identifier that is already taken; reuse, copy or skip a natural duplicate.
Imported records keep their identifiers and link_rewrite: product, category, CMS page, brand and supplier addresses, as well as invoice, delivery slip, credit slip and return numbers, stay the same. Customer passwords stored with bcrypt are carried as they are: the customer signs in with the existing password. Legacy password formats, which the new shop cannot verify, are counted in the preview and the report; the customer uses โForgot your password?โ.
The import runs in resumable batches, in the browser or through the scheduled task. You can pause it, resume after an interruption and replay failed rows from their log, which exports to CSV. Original images are placed at the new shopโs paths and thumbnails are regenerated in its themeโs formats.
Before the first import, the module saves a safety backup of the tables it will change; it can be downloaded and restored. After the import, the verification compares both shops: rows per table, order totals excluding and including tax to the cent, stock quantities, presence and hash of images, URL count, HTTP status of key pages and the back-office order page. The final report comes as a PDF and a CSV.
Rollback deletes what the import created, puts back the records it replaced and the files it moved, and keeps the records a newer order needs. A control subset validates the mapping on a small volume before the full transfer. A differential second pass then carries the orders, customers and products created or changed on the old shop since the first export. The redirect plan downloads as CSV, Apache rules and Nginx rules.
The module is made for shops moving to a recent version while keeping their history, for shops changing host or domain, and for agencies taking over a clientโs shop. It is designed for live shop catalogs and for hosts that offer SSH access or a cron job that calls PHP.
Prepare the new shop, check what came across and stay in control until it opens.
See how we compare to the most common alternatives on the market.
| Feature | WePresta | Addons |
|---|---|---|
| payments Transparent pricing | check_circle | cancel |
| update Lifetime updates included | check_circle | cancel |
| support_agent Direct developer support | check_circle | cancel |
| verified PS 1.7, 8 & 9 compatible | check_circle | help_outline |
| code Standardized clean code | check_circle | cancel |
| storefront Multi-store ready | check_circle | help_outline |
| money_off No hidden renewal fees | check_circle | cancel |
Find answers to frequently asked questions about this module
5-minute installation · Full documentation included
Templates per page type and per language for the meta titles, descriptions and keywords of products, categories,...
Full page cache: stored pages are sent before PrestaShop builds them, with no database query from the module,...
Really blocks third-party scripts, iframes and pixels before consent, then loads them by accepted category...
check_circle
check_circle