How migration settings are remembered

Once you have run a migration with WooCommerce Importer or PrestaShop Importer, the app remembers your choices for the next migration from that same connection. If you return months later and start a new migration, the app scans the source store and then automatically opens and focuses the settings form, 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;
• for a PrestaShop multistore connection, the PrestaShop shop you selected;
• 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, choosing a different shop in the advanced dashboard starts a rescan immediately. When it finishes, the setup form returns with that shop’s counts. The selected 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 copies the settings from your last migration job. Starting a separate new migration uses the settings saved for that store connection, with the two safety exceptions above.