Forums/Community/Product Feedback

PlannedDoneNot planned

Replicating your config on your sandbox

Sandrine Moreau
suggested this on March 24, 2010 12:16

It would be great to be able to replicate your environment in your sandbox. There is an export facility in the prod box, but there is no Import facility. Having a sandbox that doesn't mirror your prod box is pretty much useless, and having to redo all the config manually on the sandbox is extremely time consuming!!!

This is the first thing that any customer with a sandbox will be asking for.... and I'm probably not the first one!



User photo
Chris K

Agreed, I would love to be able to port over my widgets and triggers into the sandbox.

April 23, 2010 07:31
User photo
Graham Robson
Coherence Design

Also in the other direction, promote from Sandbox to Production - this would be a logical deployment pattern. Develop & test in the Sandbox, deploy into Production.

April 23, 2010 10:29
User photo
Conrad Selle
Project CS Beta Testers

I'd like to understand if there is any ability for us to develop pre-production staging config, as well as add content to Forums, People, etc, that would then allow us to migrate and deploy into production when ready.  With the new Forums in our Sandbox, even an API would be an acceptable workaround so that when they go live in production, we can quickly populate content, etc.

May 05, 2010 11:03
User photo
Christopher Louie

I vote for the ability to promote from Sandbox to Production. I've stopped using Sandbox simply because of the added effort and duplication errors migrating configs to production.



May 25, 2010 12:58
User photo
Karen Anderson

I agree. I'm posting several topics into forums and it's not going to be much fun to repeat the process in the live environment.

June 23, 2010 13:18
User photo
Geoff Flamank
Project C Beta Testers

I strongly support the need for functionality that would allow selective migration of Forum articles from Sandbox to Production. Cutting and pasting isn't very efficient. Or am I missing something in my interpretation of this functionality?

- Geoff

June 30, 2010 12:05
User photo
Eric Friedman

Would be great as the complexity of mirroring is difficult.

July 02, 2010 15:37
User photo
Kyle Berger

Perhaps when you run the operation to import changes from your sandbox, there can be a selection prompt asking what and how you want it imported.  Imagine seeing a checkbox for Forums, People, Views, Macros, etc.  That way you can pick and choose what you want and what you don't to avoid problems.  Also, a drop-down next to each item that lets you select only new entries, mirror it exactly, etc.  That way you have as much control as almost anyone would possibly need.

August 16, 2010 17:38
User photo
Cheves, Dean E
Twitter Integration Beta

Assuming identity of an Agent or User has been one of the most useful features for us when developing content and fields. Assuming and exporting the identity of the Sandbox or the Main Site would be equally useful. We need a Sandbox promotion or export to live feature.

September 10, 2010 11:44
User photo
Fergus Hammond

I've got the same request. We always have staging environments at work and we'd very much like one for Zendesk too. I'm sure that Zendesk itself has a staging environment for it's own teams!

The sandbox feature is useless to us without a way of copying our current production environment. Sure, we could manually recreate our business rules but it's too much work.

December 09, 2010 16:15
User photo
Graham Robson
Coherence Design

I'm pleased to advise that Coherence Design - ( have now developed a capability to export and import all configuration elements (triggers, automation, targets, custom fields, widgets, macro, and views). This will serve as the basis for a commercial web service and widget UI to enable staging promotion to a production environment and many other scenarios, including version control.

This will be launched shortly, but please contact me ( if you want to get involved at a beta project level.

December 09, 2010 22:39
User photo
Peter Becker

As there is is no releasing process for contents (e.g. an articles is written but not reviewed and needs to be released by a reviewer) a sandbox with all contents and the possibility to stage the sandbox changes would be very helpful.

January 07, 2011 05:25
User photo
Andrew J
BizStudio NZ

Michael has opened a feature request for deploying from Sandbox to Production... may pay to make some of these comments here...

I think both would be valuable.


February 28, 2011 14:57
User photo
Maya Shoval

My +1.

November 20, 2011 23:51
User photo
John Rupp

It would be extremely valuable to be able to copy over all of our triggers and then also be able to one click to enable the new trigger that has been tested to save time going to and from testing. 

December 05, 2011 08:57
User photo
Yolandé Nelson


January 17, 2012 19:21
User photo
Mike Bergeron


February 07, 2012 10:48
User photo
Steve Perras


June 05, 2012 14:02
User photo
Pedro Rodrigues


July 12, 2012 05:47
User photo
Eli Blankers

Where is the ZenDesk staff on this one?  I cannot believe I didn't realize this need before seeing this request. Absolutely agree.  Sandbox isn't very helpful at the moment, but it would be priceless with a few updates.

July 12, 2012 11:20
User photo
Eli Blankers

Can I assume ZenDesk is working on this?  Over two years ago, and there has been NO reply by a staff member.

July 20, 2012 14:04
User photo
Jake Holman
Product Manager

Hey guys,

While I'd love to also see this feature (and perhaps even the ability to specify exactly what to sync back down to the parent) it's unfortunately not going to happen in the near future.

At the moment sandboxes are just another Zendesk account which is tied to your own account. We move a few things over such as settings and users, but we do that at the point of the account's creation. We have no mechanism to then sync anything after this point.

This project would essentially involve us completely changing sandboxes, and is thus a substantial engineering effort. Unfortunately there's likely no room between everything else on the roadmap for this year.

When we revisit this area, we'll certainly keep everyone in the loop about any plans and beta.

July 26, 2012 12:33
User photo
Graham Robson
Coherence Design

In case anyone missed this in the thread trail, Coherence Design have a full commercial extension capability called Configuration Manager that allows you to extract builds of custom fields, triggers, views, macros, reports, automations, groups, and widgets. These can then be deployed to another Zendesk, typically used between prime and sandbox instances.

To be clear this isn't syncing, which is a substantial undertaking, rather it's a set of tools that admins can use to enable portability of configurations.

If your interested in exploring, contact


July 26, 2012 12:53
User photo
Jeff Bennett

Okay this was killed about 10 months ago but really should be revisited.  We are in the midst of transitioning all of our support channels to Zendesk and our understanding of the Sandbox was we could test before deployment.   I spent lots of time developing triggers and automations when agents started entering phone conversations as tickets and then before transitioning our next channel e-mail I created a Sandbox.  Then we started getting a flood of notification e-mails that we had previously customized, we also noticed not all groups were carried over.  This meant lots of time recreating work that had already been done.

I understand not being able to dynamically add content from the other account without a redesign, but at creation couldn't the old account be basically cloned in terms of triggers etc. This would at least allow testing new things, and then later if a redesign is added to the roadmap have it able to go the other way as well.  Think it is about time for an update on this one.

May 02, 2013 13:20
User photo
Quelyn Gretsky

++++++++1 to this one

July 29, 2013 17:27
User photo
Lawrence O'Connor


August 27, 2013 03:21
User photo
Nick L

We're working on updating our triggers and such and not having this feature makes that pretty aggravating. I'm not holding my breath, but this would be really nice to have.

September 05, 2013 17:23
User photo
Christian Göingberg

I agree that it would REALLY be helpful to be able to export triggers etc. from production to Sandbox. As it is today, it would take me a week or so just to set up the environment in Sandbox, and then I still don´t have any tickets to play with.. 

November 09, 2013 15:00
User photo
Allen Hancock

To have a choice:   Clone current settings into a new Sandbox, or Create an Empty Sandbox would be just fantastic.


December 20, 2013 19:16
User photo


Have a look on our ZenDesk migration tool : :)

January 09, 2014 19:20
User photo
Cedric Dana

I find the sandbox completely useless! How can I test things if I can not mimic my production Zendesk?!?!?!?!

February 18, 2014 07:43
User photo
Matthew Mah

Hey Vincent, I see you've removed your github solution. I was excited to look at it. Any chance it's going back up?


February 19, 2014 14:26
User photo

@Matthew Send me an email at blanchon dot vincent at gmail ;)

The project can't stay on github for this moment, sorry for that

February 20, 2014 18:38
User photo
Matthew Mah

Hello Vincent,

I did send you an email. Can you please confirm reception?

Thank you!

February 24, 2014 08:00
User photo
Robert O' Kirwan

Hi Matthew, Vincent


Were you guys able to connect? We would love to trial this as well. 





February 26, 2014 22:40
User photo
Graham Robson
Coherence Design

If your in the market for a commercially supported capability to manage Zendesk configurations between Zendesk, then our CloudSET Configuration Manager is an option for you - see

Develop & test on on your sandbox and deploy to your production environment or share common configuration patterns between Zendesk's

A flexible capability that enables the extraction and injection of any or of the following Zendesk configuration components:
  • Custom Fields
  • Triggers
  • Automations
  • Macros
  • Reports
  • Views
  • Widgets
  • Groups
Arbitrary configuration of components can be made and shared across Zendesk as either repeatable patters, development-to-production promotion, or back-ups. This includes a Group, Organization, and User data re-mapping tool, since rules can contain references to specific operational data ID's.

To support this facility a shared access to your Zendesk is established. This can be bidirectional or in only one direction.The principle of operation is to extract a configuration set of components from a source Zendesk, and then from the target request an injection from the source.

Sharing Access
The CloudSET Framework account management facilities enable the setting up of shared access to transportable configuration data sets extracted and stored on CloudSET. Typically shared access is set-up with the Zendesk Sandbox available to the Zendesk Plus Plan and above. However, shared access to extracted configuration data sets, can be granted to any other Zendesk.

This achieved by registering other Zendesk accounts, verified by supplying the target Zendesk's API token access credentials. The Configuration Manager license includes the sandbox, but a separate license is needed for other Zendesk accounts. Discounts are available for Hub & Spokes architectures.

Fine granular control is available to name and define multiple set's of configuration components, down to individual rules. The configuration tool has a tab per configuration type, with handy select all or individual tick selections.

Naming and adding a description will help manage the configurations and support easy identification for injection pulls on shared configuration data access Zendesk's. Extracted configuration data sets can be deleted at any time from the source Zendesk.

From a target Zendesk, which has shared configuration data access to the source Zendesk, the Configuration Manager will section list all the configurations data sets shared by the registered source's.

Deploying a configuration data set will open up the Configuration Manager tool, the same common interface as the extraction usage, listing all the components that form the configuration data set. Automatic ID re-mapping, and dependency ordering will minimize re-mapping. However, if configuration set's make reference to rule elements that are not contained in the extraction set's or contain Organization or User reference (which is operational data), then a remapping facility is provided for each reference element. This is implemented as a drop-down selectable list for ease of set-up.

An option exist to overwrite existing configuration components, the default being to not overwrite. The exception being custom fields, since important background associations with their tags could be adversely effected.

An un-deploy function is also provided to remove a deployment due to untended use.   
February 27, 2014 00:47
User photo
Matthew Mah

Robert, I am awaiting Vincent's return from holiday sometime next week.

February 27, 2014 05:14