How to migrate my Advanced Pack data to a new PrestaShop installation?

Copying the module’s data requires the referenced identifiers to be STRICTLY identical in both databases: packs, products, combinations, attributes and customization fields. Store identifiers must also match. If you transfer cart and order data, their identifiers must be preserved as well. If these identifiers have changed, a simple copy will not work: migration with identifier mapping is required.

The module’s tables complement PrestaShop’s native data; copying them alone does not recreate the catalog or its associations. Have the person managing your databases prepare the migration, using a complete backup and a test copy.

Data to include in the migration plan

• Tables named with the store’s actual prefix followed by pm_advancedpack: for example, ps_pm_advancedpack and tables starting with ps_pm_advancedpack_ when the prefix is ps_.
• Configuration entries whose names start with PM_AP5, in ps_configuration if your prefix is ps_. Preserve their store or store-group scope and ensure it matches the target store.
• The native data referenced by those tables: pack and component products, combinations, attributes, customizations and store associations. In particular, check the AP5-Pack attribute group and the AP5-Bundle feature used by the module, plus carts and orders if their history is transferred.

Adapt table names to each installation’s prefix. Also check the source and target module and PrestaShop versions: copying tables alone is not a universal version upgrade procedure.

Check the migrated store

After installing or upgrading the module according to the migration plan, use the test copy to check pack contents, combinations, prices, taxes, stock, store associations and a representative order. If you use postponed updates, retrieve the target store’s CRON URL from its configuration and check its scheduled task.

Restoration of all packs and settings can only be confirmed after these checks. Do not overwrite an existing store’s data without establishing the mappings and validating the migration.