How migration settings are remembered

See which migration choices Store Importer remembers for each connected store, which two settings reset, and what happens after a rescan.

Published September 14, 2026

Also available in: Deutsch · Español · Français · Nederlands

Once you have run a migration for a connected store, Store Importer remembers your choices for the next migration from that same connection. If you return months later and start a new migration, the settings form is pre-filled with the choices you saved last time.

What is remembered

The app remembers what you chose to migrate and the related settings, including:

  • products, categories, customers, orders, coupons, manufacturers, pages, posts and publications;
  • language and translation languages;
  • your PrestaShop shop;
  • order prefix, order notes, selected order statuses and their financial and fulfillment mappings;
  • product, page and post redirects;
  • product reviews, description images, metafields and product metadata;
  • weight unit and date filters;
  • answers from the guided migration about scope and description style.

These settings belong to the store connection. A different connected store has its own saved settings.

What always resets

Two settings are deliberately not reused:

  • Overwrite existing products starts off for every new migration. Turn it on only when you intend to replace matching products.
  • A product-category filter set by support applies only to that migration and its follow-up jobs. It does not carry into a later, unrelated migration.

What happens after a rescan

Your selected order statuses and their financial and fulfillment mappings survive a rescan. You do not need to select or map them again.

For PrestaShop multistore connections, saving a different shop starts a rescan so the counts match that shop. The saved shop and the other migration settings are still available the next time you start a migration from that connection.

Repeat last migration

Repeat last migration still copies the settings from the specific migration job you repeat. Starting a separate new migration uses the settings saved for that store connection, with the two safety exceptions above.