Support Asset Migration Between Sandbox and Production Environments Within the Same PX Subscription

Current Behavior

• When a Gainsight PX subscription is shared between sandbox and production environments (i.e., both environments exist under the same subscription), it is currently not possible to migrate configured assets — including custom objects, user-level objects, connector configurations, segments, and engagements — from the sandbox environment to production using the xorg migration tool.
• The xorg tool fails because it attempts to create user-level objects that already exist within the shared subscription, resulting in a conflict. Attempting to manually recreate the configuration in production is also unreliable and time-consuming

Desired Behavior

• Customers should be able to promote fully tested PX configurations from a sandbox environment to production within the same subscription, without hitting object-level conflicts. Specifically:
  • The xorg migration tool (or a replacement asset migration workflow) should support same-subscription sandbox-to-production promotion
  • Assets including custom objects, user-level objects, connector configurations, segments, and engagements should all be promotable
  • The tool should handle object conflicts gracefully — either by updating existing objects in the target environment or providing a clear conflict resolution interface, rather than failing silently or throwing an error

Business Impact

• My customer manages 13 products being instrumented through PX and requires the ability to build and test configurations in a sandbox environment before moving them to production — a standard enterprise software development practice. Without this capability:
  • Customers cannot safely test new PX configurations against real data before production go-live
  • Any configuration changes must be built directly in production, introducing risk of errors in a live customer-facing environment
  • Team has already lost significant time manually attempting to recreate sandbox configurations in production, delaying automation programs, scorecard updates, and the overall PX rollout timeline

Workaround Available?

Partial — Gainsight's current guidance recommends creating separate products within the same subscription for sandbox and production environments rather than using environment flags or the xorg tool. However this workaround:

• Does not allow testing against real production data in sandbox before go-live
• Requires maintaining duplicate configurations across multiple product keys
• Is not practical for customers managing 13+ products with complex connector dependencies

Proposed Solution

One or more of the following:

1. Enhance the xorg migration tool to support same-subscription environment promotion by detecting existing objects and updating rather than failing on conflict
2. Build a dedicated Sandbox-to-Production promotion workflow in the PX UI — similar to what exists in Gainsight CS — that allows admins to select assets to promote and handles conflicts with a UI-driven resolution flow
3. Support a dual-connection sandbox configuration within a single PX subscription, where one connection points to the sandbox CS tenant and one points to production — allowing parallel testing without requiring a full migration