StagingPro FAQs, Known Issues, Roadmap, and Release Notes

This page combines four related references: the most-asked StagingPro questions, the known BigCommerce platform limitations that constrain what StagingPro can migrate, the roadmap of upcoming features, and recent release notes. If you are debugging a migration that did not behave as expected, the known issues section is the first place to check.

​

Frequently asked questions

​

Setup

Q. How do I set up StagingPro on Production and Staging stores? Install StagingPro on Production from the BigCommerce App Marketplace. The app then becomes available on each Sandbox you intend to link. From a whitelisted Sandbox, enter the Production store hash and click Save; approve the connection request from Production. See setup and onboarding for the full flow. Q. What is a staging environment? A near replica of your production storefront for software testing. Code builds and updates require staging environments to ensure quality under production-like conditions before deployment to live. Production is the live customer-facing store. Staging is a sandbox configured to mirror Production. Q. Why is StagingPro taking a long time to create an environment? Migration speed is bounded by the source store size and the BigCommerce plan tier. Enterprise has higher API quotas and migrates faster than Pro or Plus. Anonymising data adds processing time. Image-heavy catalogues add upload time. Think about what you actually need before triggering a full Production-to-Sandbox copy. Q. How long does the first-time link from sandbox to production take? The connection request and approval is instant; allow up to 5 minutes for StagingPro to provision the migration platform and create base branches if Git is connected. Q. How do I link Sandbox environments to Production? Contact Helpdesk to ensure your Production and Sandbox environments are linked within your assigned StagingPro tenant. See setup and onboarding Step 3. Q. Can I rename Production? No. Production is a reserved name used internally. All other environment names are user defined. Q. Where does support go if onboarding hits a snag? Open a ticket at https://helpdesk.vortexiq.ai/portal/en/home or email helpdesk@stagingpro.com (which auto-creates a ticket). Q. The Slack webhook stopped working after a workspace upgrade. Slack occasionally invalidates webhooks during workspace migrations. Recreate the Incoming Webhook in api.slack.com and paste the new URL into StagingPro Settings. Q. Teams webhook URL is rejected on Send Test Message. Confirm the URL is the Workflow URL (modern), not an older Incoming Webhook connector URL. Microsoft is deprecating the older connectors; StagingPro expects the Workflow URL format. Q. Can I add multiple Slack channels? Yes. Add Channel can be repeated to add multiple Slack workspaces or channels. Same for Teams. Q. The B2B Connected button is green but B2B entities are not appearing on Bulk Content Migration. Confirm both the source and destination environments show Connected. B2B migration requires both ends connected, otherwise the entities are hidden from the migration grid.

---

​

Migration mechanics

Q. How do I migrate specific products? Use Selective Content Migration, Products tab. See selective product migration for the field-level mechanics. Q. How do I prevent confidential customer data being migrated to test environments? Tick Anonymise Customer Data in the Order Data Migration section before running the migration. This scrambles PII (Personally Identifiable Information) before it reaches the destination. Q. Can I pause or cancel a data migration? Yes, it is possible to pause/resume and cancel data migration. Q. If the migration fails halfway, do I lose my progress? No. Checkpoint-based resumability means the migration resumes from the last checkpoint when retried. Already-migrated entities are not re-processed. Q. Will third-party app extensions and scripts migrate to the new environment? No. Third-party apps and scripts must be reinstalled and reconfigured on each environment. Q. Why are my product orders all showing Pending in the destination? By design. Migrated orders are set to Pending status to prevent accidental fulfilment from the destination store. New increment IDs are assigned by BigCommerce; reference orders by source-SKU rather than ID. Q. Are reviews migrated? Yes, reviews are migrated as a distinct component step. Title, text, status, rating, name, email, and original review date are preserved. Average rating is recalculated automatically on the destination. Q. What happens to product image filenames with spaces or & characters? They will not migrate. Rename the source image files first, then re-run the migration. Q. Are products without channel assignments migrated? Yes, they are migrated and assigned to default channel in the destination store. Q. Are Shared Modifier Options or Shared Variant Options supported? Yes.. Q. Are app-specific metafields fully functional after migration? Metafield values migrate, but the creating app may need to be installed on the destination store with matching client ID for the metafields to function as expected. Q. Can I selectively migrate just the product images without other fields? No. Selective product migration is all-or-nothing for the product record’s components. To preserve specific fields, use the BigCommerce native import-export tools alongside StagingPro. Q. What happens when I migrate a selective product that already exists on the destination? The product will get updated in the destination. Q. Why does my page not have its embedded images after a selective migration? WebDAV credentials are missing on either the source or destination. Configure them under Settings, WebDAV on both stores and re-run. Q. Can I selectively migrate a single coupon code? Yes. Promotions including coupon codes appear under the Promotions tab. SKU-based references mean the underlying SKUs and category names must exist on the destination for the coupon to function correctly. Q. The migration shows In Progress for hours. What is happening? Bulk migrations of large catalogues with images, locales, and complex rules can run for several hours. Check the per-entity detail view, the platform updates progress per entity. If genuinely stuck (no progress over an hour), open a support ticket with the Request ID. Q. My promotion migrated but the discount is not applying on the destination. Most likely cause: the SKUs or category names on the destination do not match the source. Coupon codes match by SKU and Name, not by ID. Verify the destination has the matching SKUs and identical category names. Q. Can I migrate just B2B Companies without their dependencies? No. Companies pull in Customer Groups and Price Lists automatically because those define the trading relationship. The dependency cannot be turned off. Q. How long does a B2B migration take? Comparable to standard product migrations of similar size. Expect tens of minutes to a couple of hours depending on company count and quote/invoice history. Q. Why was my Gift Certificate migration empty? Gift Certificates must be enabled in the source store before migration. Open BigCommerce, Marketing, Gift Certificates, ensure Enable Gift Certificates is ticked, then re-run the migration. Q. Can I include Orders in a Production-to-Sandbox migration? Yes, but always tick Anonymise Customer Data in the Order Data Migration section to scramble PII. Migrated orders go to Pending status to prevent accidental fulfilment.

---

​

Theme Deployments

Q. Do I need a GitHub account before installing? Only if you intend to use code deployment. Data migration works without Git connected. You can register for a free GitHub account when you are ready. Q. Can I get only my own deployments notified to me? Not currently. Notifications fire to all configured channels for every event of the enabled types. Use channel-side filtering (Slack or Teams) if per-developer routing matters. Q. Can I create a GitHub account from inside StagingPro? No. You need an existing GitHub account. Sign up free at https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github. Q. Why does my preview URL take 5 minutes to come up? The preview server has to provision a temporary instance and install the theme. Larger themes take longer; under-2-minute previews happen for small themes. Q. Why does deploy take 15 to 20 minutes after approval? StagingPro packages the theme bundle and uploads it to BigCommerce, which then installs it to the target channel. The bundle size is the bottleneck. Small themes deploy in 5 to 10 minutes. Q. We have a CI/CD pipeline running custom build actions. How does StagingPro fit? Run your CI/CD before merging into the StagingPro environment branch. As long as the merge commit lands on the StagingPro branch, it will appear on Code Deployment. Pre-merge gate via Jenkins or similar is fully compatible. Q. After installing StagingPro I see autogenerated branches like Productione347c1. Are they correct? Yes. These per-channel branches are required for commit tracking. Do not delete or rename them. Q. Will StagingPro auto-export the theme from BigCommerce to GitHub on first connect? Yes, provided GitHub is connected and at least one team member has been added on Settings. The theme downloads into the connected branch automatically. Q. We use a typical develop branch where developers push first. How does that map? Set up the StagingPro environment branches to match: Production, Staging, UAT. Treat your developer branches as personal branches. Code flows: developer branch -> Staging -> UAT -> Production via merges. The reverse flow also works as long as no conflicts. Q. After approval, can the deployment be cancelled? You can Reject a deployment that is still Awaiting Approval. Once Approved & Deployed, use Rollback to revert. Q. What if I get an “invitation not received” message during GitHub connection? Confirm you used the GitHub Apps integration path rather than manual invite. GitHub Apps is OAuth-based, organisation-level, with automatic token rotation and granular permissions, set up in one click. The GitHub App flow handles authorisation directly without the email-invite hop that fails. See GitHub and Bitbucket. Q. Can I create a GitHub account from inside StagingPro? No. Sign up free at https://docs.github.com/en/get-started first, then link in StagingPro.

---

​

Rollback and history

Q. I approved a GitHub commit by mistake. How do I undo? Open History and Rollback, Code Deployment tab. Click Rollback on the deployment row. The previous theme version redeploys (15 to 20 minutes for the bundle to land). See history and rollback. Q. Are store data/system IDs migrated as-is? No. BigCommerce assigns new increment/system IDs in the destination. Always reference products by SKU rather than ID, since SKUs are preserved.

---

​

Multi-storefront and channels

Q. How does multi-storefront migration work? Bulk and Selective migration both work with multi-storefront setups. You can move data within one store or across different stores, based on the source store(s) chosen before migration. The dropdown will show all available storefronts for the selected source and destination stores. Q. I migrated a product with locale and metafields, but the product data is not displaying correctly on the destination storefront page. Why? To successfully migrate locale and metafield data, the destination storefront must have the same language configured as the source storefront. If the languages don’t match, locale-specific content and related metafield information may not migrate correctly.

---

​

Notifications and team

Q. Can I limit notifications to events that affect me? Not currently per-user. Notifications fire to all configured channels for every event of the enabled types. Filter at the Slack or Teams side if needed. Q. Can I restrict an external agency from changing Production? Yes. Use BigCommerce user permissions plus GitHub Change Permission to give the agency Staging and UAT access only, retaining Production for your team.

---

---

​

Known issues and platform constraints

​

Products

• Channel Assignment Required, products without a channel assignment are excluded from migration. Ensure every product has at least one channel before migrating.
• Shared Modifier and Variant Options are not yet supported. BigCommerce is working on the relevant APIs (no confirmed ETA). Regular modifier and variant options migrate fine.
• Customs Information is not part of the standard Product API and does not migrate.
• High Variant Count Products (very high counts) may return 500 errors and require BigCommerce engineering intervention.

​

Orders

• Order IDs are incremental in BigCommerce; migrated orders get new numbers.
• Destination orders cannot be deleted, so repeat migrations grow the order count.
• Orders migrate with statuses as-is. Recommended: disable customer order notifications in BigCommerce Marketing, Transaction Emails before migrating.
• Multi-shipment orders, BigCommerce API allows only one shipment per order; additional shipments are not migrated. Payment method becomes “Manual”.

​

Pages and categories

• Blog-type pages cannot be migrated via the BigCommerce API; create manually in the control panel.
• URL conflicts, pages and categories sharing the same URL can show “The URL is duplicate” errors. Ensure unique URL values.

​

Themes and images

• Themes apply only to the default store channel.
• Product image filenames must not contain spaces or & characters.

​

Other limitations

​

BigCommerce API rate limits

BigCommerce applies quota-based rate limits refreshed every 30 seconds: StagingPro automatically handles rate limiting with circuit-breaker logic and exponential backoff so migrations pause and resume without data loss.

​

Roadmap

Items planned, subject to change based on customer feedback and BigCommerce API availability.

​

Data migration enhancements

​

Recent release notes

A condensed timeline of fixes and features.

​

Support

Open a ticket at https://helpdesk.vortexiq.ai/portal/en/home, email helpdesk@stagingpro.com, or call StagingPro Support at +44 20 4547 9292. For escalations gather:

• Source store hash and destination store hash.
• Request ID of the migration in question.
• Started at and Completed at timestamps.
• Error messages from the per-entity detail view.
• Screenshots if applicable.

For a feature request, submit through the helpdesk and the product team will weight it in the priority queue.

---

To view our Onboarding steps, please access the following article → StagingPro Onboarding