function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

Keeping sandboxes refreshed without losing ongoing work

Is there any good way of refreshing a sandbox from production without totally losing anything in that sandbox that hasn't yet been pushed to production?  Something like a merge rather than a total ovewrite?


We have a sandbox that has a long-running project going on.  There is also a second sandbox used for more short-term changes.  The latter sandbox has its changes deployed to production once a month or so.  We like to keep our sandboxes refreshed from production pretty frequently, so we would like to refresh the first sandbox with the long-running project after production is updated.  However, if we do that, we'll lose all the changes for the project that aren't ready to go to production yet.


Does anyone have a good process for this?  Do you just not refresh sandboxes until all your changes are deployed?  What about longer term (3-6 month) projects? 


I generally wait to push all my required changes to production and later on do a refresh.


You can deploy from short term sandbox to long term sandbox and then to prodcution or from short term sandbox to production and then to long term sandbox. In this way all 2 instances are in sync with production and you still retain your development changes in long term sandbox.


Unfortunately, there is no easy way to perfom a merge kind of operation when you refresh a sandbox.