Multi store functionality is the ability to manage multiple customized shops which share common items from one back office.

Don’t confuse multi store management with multiple sites management. You DO NOT have to use multi store to implement:

  • multiple languages
  • multiple currencies
  • different design templates

You DO have to use multi store in case:

  • you want to set different prices for same products
  • you want to limit access of customers who buy from your different stores to order history of one of the stores

Multi store functionality allows:

  1. set up more than one online store
  2. theme each store in a different way according to the products which are sold
  3. share products between several stores so product doesn’t have to be maintained in different locations
  4. give products different prices depending on the store they are located in
  5. set store location
  6. create default customer group

There are 4 main scenarios of multi store migration.

Scenario 1

Multi Store → Multi Store

Both Source and Target shopping carts support multi stores.

You will have one source store URL and one target store URL. The migration is considered as a single one. The procedure is similar to a simple store migration.

On the step of Multi store configuration you will have to map source and target stores. The data is transferred to a target store. You can choose the Target store which migrated data will be assigned to.

As it is a single migration, the price depends on the quantity of items you migrate. It can be calculated previously with the help of Migration Estimator.

The option Preserve order IDs on target store in this case can not be chosen as it will disable mapping of several source stores with one target store.

Scenario 2

Several source stores → Multi store

The migration procedure is different from the previous one. You have several stores on platforms that don’t support multi store functionality, and want to move data to a multi store. This case is regarded as several separate migrations, because you have several source URLs and one target URL.

The shopping cart data from several source stores will be migrated to target store. So, eventually you will get one target store URL. You will be able to map source and target stores. The data will be transferred to corresponding categories of the chosen target stores. If you skip mapping the data will be migrated to a default store.

When migrating from different source stores to one platform with multiple stores, the service moves all the data without checking the availability of product in catalog. If you have similar data at your stores like product SKU (model, description, prices), customer e-mails or order IDs (and you want to preserve IDs on target store) the data can be duplicated on the target store. We do not take the responsibility for data selection and guarantee data transfer with no loss. So, it is recommended to check data after migration and locate it in categories appropriately.

Note! As you perform several migrations, the price is calculated separately for each data transfer. If you have two source stores which you have to migrate to one Target store, you have to pay for two migrations. Each migration price depends on the quantity of items and the type of source cart. It can be previously calculated using Migration Estimator.

The option Preserve order IDs on target store in this case can not be chosen as it will disable mapping of several Source stores with one Target store.

Scenario 3

Multi store → Several target stores

The case is rare as it is usually more convenient for merchants to manage several stores from one backend using multi store functionality, then manage several stores separately.

The migration is contrary to the previous scenario. You will have one source store and several target store URLs as a result. In this case you will also have to perform store mapping to migrate the data accurately.

All stores of multi store source cart should be mapped with appropriate target stores.

Such case is regarded as several migrations, and is charged for each store migration separately. The exact price can be calculated with Migration Estimator.

Scenario 4

Multi store → One target store

This option is similar to the previous one. Here you can choose one or several stores from multi store shopping cart and migrate them to one store on your target cart. You should also perform mapping to choose source stores you want to migrate from (you can choose to migrate data from all, several or one store on multi store shopping cart).

This case is considered as a single migration as you will have one Source and one Target store URL. The migration is charged as a single and can be estimated depending on the quantity of items you need to migrate. Use Migration Estimator to know the exact migration price.