During installation, StagingPro will create two complete environments for you, but you can decide what to do after this based on your specific needs.
The Content Migration screen allows you to move only that data which applies to what you want to test. For example, if you were changing from an Easter to a Christmas theme, the chances are pretty good that you won't need to move products, categories, and other store settings.
It is important that you be aware that the content migration screen will only move data that does not already exist in the destination. For example, if you attempt to move ten brands from source to destination, but one brand already exists, nine new brands will be created in the destination store, but the one record that already exists will fail.
In order to overwrite data, you can use the Understanding the Product Catalogue screen, which deletes and recreates data.
When performing partial migrations, it is important to know that some data depend on others. For example, while it is possible to migrate a Product, this data will not be complete unless the brands, categories, variations etc have been migrated. Therefore, StagingPro migrates associated with other data elements EVEN IF THEY ARE NOT SELECTED INDIVIDUALLY by you. Below is a list of data fields that get migrated automatically.
...
Migrating Entity
...
Other Entities Migrated
...
Products
...
Brands and Categories
...
Product Reviews
...
Brands, Categories and Products
...
Price List Records
...
Brands, Categories, Products and Price Lists
...
Price List Assignments
...
Prices Lists and Customer Groups
...
Customers
...
Customer Groups
...
Shipping Methods
...
Shipping Zones
...
Promotions
...
Brands, Categories, Products, Customer Groups, Shipping Zones
1) Choose the environment where you want to migrate FROM.
2) Choose the environment where to want to migrate TO
3) Starts migrating the selected options from the source to the destination environment.
4) Design and Content Migration contains only those “graphical” interfaces that your user see’s. The website theme, images (not product images), pages and blogs will be migrated.
5) Product Data Migration is a bit more involved than other migration options and may take a while to process depending on the number of products in your catalogue. Many different options such as brands, categories, variants etc all need to be considered when moving products. For a detailed explanation of the process you can click here.
6) As you would expect, Order Data Migration is purely data associated with orders however, due to PII (Personally Identifiable Information), it is not normally wise to use this data as is. For this reason, StagingPro gives you the option to anonymise both order and customer information. “Fake” names and addresses will be inserted instead of the actual values meaning that a true environment can still be maintained without the risk.
7) Finally is the store settings. If you have been testing different scenarios with how your store displays, sends out notifications or even how your regional settings may affect your store, you can use this option to just migrate those particular elements.Bulk Content migration assumes the destination store is empty.
Select your source environment, select your destination environment, select the entities you wish to migrate and click on the ‘Start the Migration’ button.
...
Under the ‘Order Data Migration’ section, choose ‘Anonymise Customer Data’ to scramble the source environment’s customer data before it is migrated to your destination environment for testing and data security purposes.
Entities with the black info circle icon have dependencies. Example Products when migrated brings over its dependencies, this case Brands and Categories.
Entities without the black info circle icon have no dependencies and can be migrated as is.
Schedule migration and B2B migration are Premium plan features