Set up a PrestaShop webservice key for a multistore migration

PrestaShop treats resource permissions and shop associations as separate settings. A multistore migration needs both configured correctly: the key must be able to read the shops resource, and it must be associated with every active shop.

Before you create the key

In PrestaShop, open Advanced Parameters → Webservice and make sure the webservice is enabled. Create a new key for PrestaShop Importer, then keep it read-only: enable GET access for the resources the importer reads.

If your setup guide tells you to enable GET for all resources, that includes shops. If you select resources individually, explicitly enable GET for shops as well as the other migration resources.

Associate the key with every active shop

On a multistore installation, use the key’s shop association control to associate it with every active shop. This is separate from the GET permission grid.

PrestaShop Importer checks each active shop during its scan. If even one shop is inaccessible, the scan stops with a webservice read-rights warning. The job log identifies the shop name and ID and includes PrestaShop’s error. Return to the key in PrestaShop, add the missing shop association, save it, and rescan.

Why GET access to shops matters

GET access to shops lets the importer detect a multistore installation and display the shop selector.

Without this permission, the key can still run a migration in the old, unscoped mode. You will not be offered a shop choice, and the job log will contain Resource of type 'shops' is not allowed with this authentication key even though the scan otherwise succeeds. Add GET access to shops, save the key, and rescan before continuing if you need to migrate a specific shop.

Choose the shop in PrestaShop Importer

When more than one active shop is found, the guided migration shows Choose your PrestaShop shop before the scope and language steps. Select a shop from the Shop dropdown, then choose Save shop & rescan. In the advanced dashboard form, use PrestaShop shop → Import data from this shop.

Only data belonging to the selected shop is counted and migrated. The rescan updates that shop’s product, order and customer counts. Each migration covers one shop.

The tier for a shop migration is set by that selected shop’s product and order/customer counts. Any amount already paid is credited, so if you migrate a larger shop later, you pay only the difference to its tier rather than buying another migration at full price.

A single-shop installation does not show the selector and follows the same flow as before.

After the migration starts

The selected shop cannot be changed after the migration is paid or downloading. If you try, the app shows: The PrestaShop shop cannot be changed after a migration has started.

The selection is retained for repeat migrations, demo-to-full migrations and inventory sync jobs.

Quick check

Before paying for the migration, confirm that:

• every active shop appears in the selector;
• the intended shop is selected;
• the product, order and customer counts match that shop;
• no shop access error appears in the job log.

If a shop is missing, first check GET permission for shops. If the scan stops on a named shop, check that shop’s association with the webservice key.