MultiStore Migration
MultiStore functionality is the ability to manage multiple customized shops which share common items from one back office.
You DO have to use multistore 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
MultiStore functionality allows:
- set up more than one online store
- theme each store in a different way according to the products which are sold
- share products between several stores so the product doesn’t have to be maintained in different locations
- give products different prices depending on the store they are located in
- set store location
- create default customer group
There are 3 main scenarios of MultiStore migration
Scenarios 1
Several Source Stores → MultiStore
You have several stores on platforms that don’t support multistore functionality and want to move data to a multistore. 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 the target store. So, eventually, you will get one target store URL. We will map source and target stores. The data will be transferred to corresponding categories of the chosen target stores.
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't be duplicated on the target store.
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.
Scenario 2
MultiStore → Several Target Stores
The case is rare as it is usually more convenient for merchants to manage several stores from one backend using multistore 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, we will also have to perform store mapping to migrate the data accurately.
All stores of multistore source shop should be mapped with appropriate target stores.
Such case is regarded as several migrations and is charged for each store migration separately.
Scenario 3
MultiStore → One Target Store
This option is similar to the previous one. Here you can choose one or several stores from multistore shop and migrate them to one store on your target cart. We should also perform mapping to choose source stores you want to migrate from (we can choose to migrate data from all, several or one store on multistore shop).
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 migration.
For more information Contact Technical Team