Hello and thank you for choosing StagingPro! We are delighted to have you on board as we take you on a quick tour to help you get familiarised, settled in and make the best use of StagingPro’s features available to you.
...
Step 4: Add GitHub accounts
IMPORTANT: Please ensure that your development team reviews and fixes the notifications visible on the deployment logs. Once all log items are reviewed and fixed, the deployments will be successful.
Step 5: Setup notifications in Slack
Step 6: Setup notifications in Teams
Step 7: Setup notifications by Email
...
Step 8: Try a test ‘Content Migration’ to a non-Production destination store
Please note that some data elements like Promotions will automatically move all other related data entities in full. Please refer to Data Dependencies, Coupon Codes/Promotions, Known Data Migration Issues and Product Fixes/Releases before attempting a test migration
Step 9: Try a test ‘Product Catalog’ migration to a non-Production destination store
IMPORTANT: You MUST perform comprehensive testing and proper validation in non-Production environments first. Only after validation and approval, should you migrate data to a live Production environment.
...
Bulk migration
When you perform a Bulk migration, StagingPro assumes the entities are not present in the destination and the StagingPro app will simply create them on the target store. If the entities already exist, it will show error notifications. There is no update action for existing entities.
Selective migration
Products
If products already exist on the destination store, it will updated during a migration. Products with multiple variation items will be deleted and recreated on the target store.
Promotions
TBC
Pages & Layouts
Page content (text) is updated if the page already exists. If it does not exist, a new page is created. With respect to widgets and widget templates, all existing widgets contained within a page will be removed and recreated again
...