Plugin Deployments Do Not Scale Beyond Two Environments

Our organization currently operates Moveworks across two environments (Sandbox and Production). In the near future, we plan to adopt a more standard enterprise deployment model with three environments: Sandbox, Test, and Production.

As we prepare for this transition, we have identified a significant operational challenge: Export/Import does not support overwriting existing assets during plugin promotion. 

Because existing assets cannot be updated in place, changes made and validated in Sandbox cannot simply be promoted to higher environments. Instead, every release requires a manual review of the assets contained within a plugin to determine what has changed and what must be migrated.

For example, we currently have to manually inspect modules such as:

• Conversational Processes
• HTTP Actions
• Script Actions
• Compound Actions
• Data Types

and determine which assets have been modified and require updating.

Once identified, the updates must be applied manually in the target environment. Depending on the asset type, this may involve copying scripts, copying YAML definitions, recreating HTTP Action configurations, or manually updating Data Type schemas and resolver settings. 

The root cause of this operational burden is that there is no supported way to overwrite existing assets through Export/Import. As a result, we cannot reliably promote a tested plugin from Sandbox to Production as a single deployable unit. 

While we are currently managing this process across two environments, it is already time-consuming and error-prone. Expanding to three environments (Sandbox → Test → Production) will significantly increase the complexity of release management and environment synchronization. In its current form, we believe this approach will become very difficult to sustain at scale.

This limitation introduces several risks:

• Manual deployment errors
• Missed updates
• Environment drift
• Configuration inconsistencies
• Increased release effort
• Higher production risk

To address this, we would strongly like to request:

• Support for overwrite updates during Plugin Import
• A true promotion mechanism between Sandbox, Test, and Production
• Environment comparison (diff) capabilities
• Dependency-aware deployment validation
• Packaging and deployment of related assets as a single unit

Even the ability to overwrite existing assets during Import would significantly reduce operational effort and deployment risk.

For organizations managing multiple Moveworks environments, this is not simply a convenience feature. It is a critical capability for maintaining a reliable and scalable release process. We strongly encourage Moveworks to prioritize this enhancement.

Thank you for your consideration.