Deploying to a sandbox is now available | Community
Skip to main content

Deploying to a sandbox is now available

  • July 29, 2025
  • 8 replies
  • 0 views

Carl14

We are excited to announce that the EAP now allows you to deploy a version/snapshot to your sandbox. 

This means that any version you have saved can be deployed to your sandbox. You can use this to keep your sandbox configuration up to date and closely matching your production environment. 

 

How do I access it?

You will find this feature listed under the Configuration management menu item, labelled “Deployments”. You can read more about how to use this feature here.

 

What can / can’t I deploy?

Currently, deployments are supported only to sandboxes. Because deployments can make significant changes to your environment, we want to be confident that the feature is working as expected before allowing it to change your production environment. 

All your main Zendesk configurations can be deployed, including triggers, automations, custom fields, and others. There are some areas that we have blocked from deployment as they require more work from our team to ensure they function correctly. 

 

What’s next?

Over the next few months, the team is focused on improving deployment features. Improvements such as automatic dependency selection and improved error handling and messaging will be released over the coming months. 

As always, I encourage you to provide any feedback or questions as they are critical to helping us improve the product to make it useful for you. Please post in these community forums, or feel free to email me directly.

8 replies

Christopher22

This feels like a massive leap forward for Zendesk in QoL admin features. Thanks for working on this!


Carl14
  • Author
  • July 31, 2025

Thanks for the feedback @christopher22. We're pretty excited about this feature and building it out even more over the coming months.


Michael14
  • August 19, 2025

@carl14 - I have been looking to finally sync up my Sandbox with production. Is Brand a supported object to sync? Mine is grayed out.


Carl14
  • Author
  • August 20, 2025

Hi Michael. Thanks for the question. Brands are currently disabled as you have noticed. Brands need to be unique across all Zendesk instances (e.g. unique subdomains). The team are still working on how to best deal with this particular constraint. Once we have a path forward we'll allow brands to be deployed/enabled as well.


Clément13
  • September 23, 2025

Hello there @carl14 , hope you are doing well.

We are currently testing this new feature, and unfortunately it seems like all of our test deployments are failing. We thought it was related to the number of dependencies we are trying to import at the same time, but even by selecting fewer dependencies, it always fails :/ 

Have you experienced/heard about this issue already or it might be related to a “locale” issue? I can provide a HAR File in case it helps :)

Thanks a lot in advance, and have a great day!
Clément


Emily31
  • September 23, 2025
Hi Clément! We have created a ticket on your behalf. Someone from Support should be reaching out to your shortly. 

Richard83
  • September 30, 2025

Having some issues with Deployment duplicating items and not updating the list of differences between environments. 
 

For example, with fields, this is shown as needing to be added to our Sandbox environment when looking to push from Production. 


Then, when we switch the comparison, our Sandbox environments shows that the below needs to be deleted. 

 

Then when deployed, this ends up duplicating in the Sandbox environment. 

 

I'm not sure if I am doing anything wrong. From my view, after a deployment is done, if I look to deploy different changes from the same snapshot to the same Sandbox environment, the list of differences should change based on what was previously deployed. This seems to be the case with things like groups, as now it no longer shows on the left, indicating no differences between the snapshot and the environment, but things like tags and fields continue to show despite how many times they have been deployed. 


Oliver35
  • Employee
  • October 28, 2025

Hey @richard83, I believe the team has already been in touch, but just in case you missed it, we identified a small issue related to partially completed deployments which has now been fixed. Please reach out if you experience any additional issues. Thanks!