How can I migrate without losing my data?

First of all, NEVER uninstall your module before this process.

To transfer your engines to another installation or PrestaShop version, have your developer prepare the migration on a test copy. Back up the files and database before making changes.

Data and files to preserve

• All module tables: after your shop’s database prefix, their names start with pm_advancedsearch. Include the main pm_advancedsearch table, its language and shop tables, associations, SEO pages and the tables specific to each engine.
• Configuration entries whose names start with PM_as4_ and PM_AS4_, including their shop or shop group context.
• Custom files used by the filters, especially images in modules/pm_advancedsearch4/search_files/criterions/ and modules/pm_advancedsearch4/search_files/criterions_group/.
• Advanced styles and theme adaptations you want to preserve. Copying the database alone does not copy these files.

Keep in mind that in order for this copy to conform to your original version, you will need to have the same IDs for products/categories, etc.

Also check the identifiers of referenced combinations, attributes, features, brands, suppliers, languages and shops. If these identifiers change, the engine references must be adapted. Your developer must check schema and module version compatibility on the destination: copying raw tables is not a universal upgrade procedure.

If your filters use PrestaShop 9.2’s Extra Properties

The destination must use PrestaShop 9.2 or later with Advanced Search PRO 5.4.0 or later. Preserve the property definitions and their values on products, combinations, categories, brands and suppliers: copying the module’s tables alone does not copy them.

• Preserve definition and related item identifiers, together with shop and language associations.
• If a module provides these properties, check that it is present and available in the relevant shops.
• Preserve the Extra Property criterion mappings in the module’s tables.

Check the result

This inventory helps prepare the migration; it does not guarantee that a raw copy works between different versions. The following checks are essential on the test destination.

After restoring the data and applying the required upgrades on the test copy, run a complete re-indexing of the affected engines as described in this FAQ. Re-indexing does not recreate missing property definitions or recover values that were not migrated.

Check the engines, criteria, results, images, styles, positions, visibility restrictions and SEO pages in the languages and shops you use before validating the migration.