[Feature Request] App Builder Apps Migration from Sandbox to Production Environment

Overview of Feature Request & Affected Roles

Zendesk App Builder currently does not support promoting or migrating an app project that was started in a sandbox environment into a production instance while retaining version history and ongoing maintainability.
 

This impacts Zendesk admins and developers who use sandboxes for proper testing and validation before deploying apps to production. It also indirectly affects agents and end users, as useful tools may be delayed, duplicated, or abandoned due to sandbox limitations.
 

What problem does this solve?

This would solve the problem of forced duplication and long-term dependency on sandbox environments for app maintenance.

Today, if an app is initially built and validated in a sandbox, there is no supported way to “promote” that app to production. Admins must either:

• Rebuild the app from scratch in production, or
• Keep the sandbox permanently active to maintain and update the app

This undermines the purpose of sandboxes as temporary testing environments and creates unnecessary technical debt.
 

When were you last affected? Frequency & business impact

I was recently affected when building a duplicate user cleanup app in a sandbox to safely test logic and behavior against non-production data. Once validated, there was no supported way to move this app into production while preserving it as the same project.

This issue occurs every time a custom app is responsibly tested in a sandbox first, which is standard best practice. The impact includes:

• Consuming limited sandbox environments long-term
• Blocking other testing initiatives due to sandbox scarcity
• Increasing maintenance overhead and risk of inconsistencies
• Discouraging innovation and custom tooling despite clear business value

With only two sandboxes available, one becomes effectively “locked” indefinitely with outdated data, reducing overall testing capacity.
 

Current workaround (if any)

Yes. The current workaround is to retain the sandbox indefinitely so the app can continue to be maintained, updated, and redeployed.

Alternatively, rebuilding the app manually in production is possible but:

• Error-prone
• Time-consuming
• Difficult to validate
• Results in fragmented app versions and duplicated effort

Neither option is sustainable or aligned with standard development workflows.
 

Ideal solution

The ideal solution would be a sandbox-to-production promotion workflow for App Builder projects, similar to deployment pipelines in other development platforms.

For example:

• Ability to promote an app from sandbox to production
• Preserve app identity, version history, and configuration
• Continue maintenance and upgrades from production after promotion
• Optionally support rollback or version comparison

This would:

• Allow sandboxes to remain temporary and reusable
• Encourage safer testing and better governance
• Reduce admin overhead and technical debt
• Align App Builder with real-world development best practices