Entity Mapping

Overview

Entity mapping is a critical step that tells MigraPro how to translate references between your source and target stores. Four entity types require explicit mapping:

Shop Mapping

If both stores use multistore, map each source shop to a target shop. Products, categories, and other entities will be assigned to the correct target shop based on this mapping.

Language Mapping

Map each source language to a target language. This determines how translated content (product names, descriptions, category names, etc.) is assigned in the target store.

Extra Language Mappings

If your target store has languages that don't exist in the source, you can configure fallback mappings — specifying which source language should provide content for unmatched target languages.

Currency Mapping

Map source currencies to target currencies. The module handles schema differences between PrestaShop versions (in 1.7.6+, currency name and symbol moved from the main currency table to a separate language table).

Order State Mapping

Map source order statuses to their target equivalents. This ensures imported orders retain their correct status labels and workflow positions.

How Mappings Work

During migration, every entity reference is translated through the mapping tables. For example, when importing a product:

1. The source shop ID is translated to the target shop ID
2. The source language IDs for translations are mapped to target language IDs
3. All category, manufacturer, and supplier references are resolved via the entity mapping table

The mapping data is stored in dedicated database tables (himigration_shop_map, himigration_lang_map, himigration_currency_map, himigration_status_map).