StagingPro Onboarding

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 based on the StagingPro licence plan you have selected.

Quick setup (Environments)

Step 1: Plan your environments
- Also refer to Best practice naming conventions and testing guidance in your new StagingPro environments
Step 2: Check that the StagingPro app is pre-installed
Step 3: Link additional environments to Production
To easily access all areas of your store’s backend admin Control Panel (including your Sandbox stores) you need Store Owner* access.
*See the BigCommerce article for Store Owner User Role and Permissions

Quick setup (Integrations)

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. Also please be patient when generating preview servers as it will take time to download all the packages and dependencies, before the preview server is generated
Step 5: Setup notifications in Slack
Step 6: Setup notifications in Teams
Step 7: Setup notifications by Email

Test a Migration

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
For Multi storefront migrations please refer to the following article https://stagingpro.atlassian.net/wiki/spaces/STAGINGPRO/pages/127795201

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.

For B2B migration - refer to https://stagingpro.atlassian.net/wiki/spaces/STAGINGPRO/pages/71401479?search_id=16169d9f-9fa9-4f7c-8be4-6501432acc05

Migration Types - Bulk Migration vs Selective Migration

Bulk Migration (Migration that creates records in an empty destination store)
- 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.
- When you select ‘Products’, by default, the product stock inventory count wont migrate. Use Selective Migration for Products instead.
- NOTE: New Product ids are linked to orders during Bulk Content Migration
Selective Migration (Migration that updates records in the destination store)
- 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.
  - Selective Product Migration now features the ‘Copy All Products’ button, which means you can run a selective update on all products now, as an on-demand task
  - Now by default (Product Stock count wont migrate unless you specify the checkbox value on the popup 'Migrate Product Stock inventory count to target store'
  - As it relates to product images, if you delete product images on the source store SKU and perform a Selective Product migration, the corresponding product images will not be deleted from the destination SKU. As an example,
    - lets say you have a SKU with 10 images on source store which you have performed a selective migration to destination.
    - If you remove 5 images from the source SKU and repeat the Selective Product Migration, the corresponding images are not removed from the destination store. You need to delete these images manually on the destination store
- Promotions
  - With current behaviour, promotions that exist in the source store are migrated to the destination store
- Categories
  - If categories exist in the destination store, you can use this option to update the categories on the target store
  - When migrating the category from source to destination, if the category already exists at the destination inside another parent category, then StagingPro creates a category with the same name as per the source category structure in the destination.
    - In this case you will have two categories in the destination with same name.
    - StagingPro will not delete the old category in the destination, it remains same.
- Custom Pages and Page Templates
  - You can use this to migrate Custom pages from Source store + storefront to destination.
  - You can select ‘Migrate Global Widgets’ depending on your migration preference
  - 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
  - Homepage should be a selectable option under ‘Page Templates’ tab
  - If you are using the old Page Widgets API, steps for this is covered in the article https://stagingpro.atlassian.net/wiki/spaces/STAGINGPRO/pages/103186433
  - IMPORTANT: For reliable Pages migration we highly recommend you use the new Page Widgets API. Send your store hashes to our Helpdesk Team so it is whitelisted on both BigCommerce as well as our StagingPro systems. Once whitelisting is confirmed, you can use the new Page Widgets API for improved migration accuracy.
- Themes
  - You can migrate Themes selectively from your source to destination BigCommerce store.
  - Select the Theme of your choice and use the ‘Copy Theme’ button to start the migration

Time taken for Data Migrations

Well, this is based on many factors such as the data available in your tenant, the data dependencies, BigCommerce API throttling, transfer connections speeds etc and can range from a few seconds for simple migrations to several hours for data intensive migrations

API Access (Selected Plans only)

Depending on the subscription entitlement for selected plans, it is also possible to access to our StagingPro APIs to manage data and deployments using APIs between environments.

Our StagingPro REST API documentation is available at the following URL:
https://www.apimatic.io/apidocs/stagingpro/v/1_0#/rest/step-by-step-tutorial

FAQs

For quick reference, here are some FAQs

Knowledgebase

The knowledgebase URL is → https://stagingpro.atlassian.net/wiki/spaces/SPSUPPORT/overview

Support Tickets Helpdesk

Support ticket portal URL is → https://stagingpro.atlassian.net/servicedesk/customer/portal/1
- you can track all of your tickets here as well as search for knowledge base articles
- Email (creates a ticket): helpdesk@stagingpro.com
- Using the Support Ticket portal helps with faster team assignment for investigation and resolution
IMPORTANT: For support troubleshooting, the StagingPro tech team may request access to sandbox stores only. As with Bulk Migration behaviour, items on the target sandbox store will need to be deleted before attempting a migration to ensure the migration happens correctly. Please ensure that:
- You do not store important, business critical or development essential data on a sandbox store as this is for test migrations only! Keep your configuration settings safe elsewhere.
- If there is any information we need to be aware before granting access to our tech team for troubleshooting e.g.,

i) data on staging that you’re team is actively working on and you wish to retain

ii) your development workflow processes we need to be aware of, please let us know before access is granted and our testing starts.

Support Phone Number

StagingPro Support +44 20 4547 9292